i686-pc-linux-musl-g++ not in /usr/lib/distcc

[Adel Ahmed]

I am trying to setup distcc and cross compiling to compile i686 packages on my x86_64 laptop(both laptops have USE=-*)
while compiling mesa on the client I see these errors:

[eccerr0r]

probably a bug/oversight, too many combinations, might want to b.g.o it. But first, does it work if you put in that link manually?

someday i should set up a musl system to see what benefits it gets...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[Adel Ahmed]

putting in the link manually did not work

[eccerr0r]

Well, that's still necessary (and it should be handled by portage/ebuild), then the other thing is why isn't i686-pc-linux-musl-g++ in the path of distccd ... where is the normal binary installed and is it in distccd's path?

(clang was a weird problem in the past for me... had one machine kept running old versions of clang and couldn't get it to run newer versions at all...)
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[Adel Ahmed]

the binary is not installed, I'm not sure why, i tried running crossdev again with the stage 4 option but it's not there:

[eccerr0r]

Is there a g++ somewhere? How is g++ being invoked normally/locally?
Can you symlink i686-pc-linux-musl-g++ to that binary?
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[pingtoo]

Adel Ahmed,

You are trying cross compile with distcc. You may want to review Gentoo wiki: Distcc/Cross-Compiling-Compiling

So, does your distcc helper have same crossdev target installed? does your distcc helper updated so it know how to invoke your crossdev target compiler?

[Adel Ahmed]

I tried to create the symlink pointing to my executable under /usr/bin/g++
still getting the error though:

[pingtoo]

So may be the file got accidentally deleted.

So let examine if any thing is missing from portage point of view first.

first use the known exist gcc by

[eccerr0r]

Not sure where you made the symlinks but you should symlink i686-pc-linux-musl-g++ to g++ in the directory that g++ stands in, and then link i686-pc-linux-musl-g++ to distcc / distccd in the distcc shadow directories... Running i686-pc-linux-musl-g++ should not give you a No Such File or Directory error...

Also your path, when running locally, should point to the shadow directories first and then have i686-pc-linux-musl-g++ later in the path. distcc will do the path f**kery to find the correct g++ binary despite having the same name. For helper boxes the path should NOT include the distcc shadow directories.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[Adel Ahmed]

[Adel Ahmed]

I symlinked symlink i686-pc-linux-musl-g++ to g++ in the directory that g++ stands in, and i686-pc-linux-musl-g++ to distcc / distccd in the distcc shadow directories
I no longer get the no file or directory error and the compilation fails with a new error:

[eccerr0r]

Looks like you jumbled two command outputs? One is from emerge, one is manual?

Does your g++ work separately?

Here's a test C++ program you can use if you don't have one handy...

[Adel Ahmed]

yes i have sorry about that, one is from emerge on the client, the other is from the distcc helper.
the compiler works on the helper(64 bit) machine:

[pingtoo]

[pingtoo]

[Adel Ahmed]

helper:

[Adel Ahmed]

I'm trying to set gcc 14 as the version to use but I keep getting 13, what am I doing wrong here:

[pingtoo]

Adel Ahmed,

thanks for the output.

May I suggest let's review the current condition. What work? what not? And what is the objective? Because all the outputs and posts I am lost track of what is going on.

For example it is unclear to me if your builder and helper are the both 64 bits multi-lib setup or something else.

So far I do remember is that you want to build 32bits packages and you are using distcc and crossdev.

[eccerr0r]

pingtoo: we know that portage "did the wrong thing" and thus this is worthy of a bugs.gentoo.org report.

I'm just wondering how much of the system is there and whether it actually could support distcc with musl so a dev could fix this and an emerge of a new version would fix this automatically.

Adel Ahmed: yes the -m32 is a good idea for testing for now though again this should be fixed in portage for gcc. In any case on the machine that's requesting help, try adding "-m32" in the CFLAGS of your make.conf to see if your amd64 box would then give you a 32-bit object file instead of giving you a useless 64-bit object file for your 32-bit machine... however this should be automatic.

The other idea is instead of the i686-pc-linux-musl-g++ symlink to g++, you should add a wrapper script that does something like

[Adel Ahmed]

I have removed all the crossdev targets, recreated the linux-musl one, recreated the symlinks:

[pingtoo]

Adel Ahmed,

I am afraid I am not able be much of help. I don't have much information I need to work on. However I tried on my test container, all thing exist at expected location.

Notice a few thing, not sure if that is your desire.

• Set -s4, not sure about this effect. I usually don't specify stage
  
• Always use latest ebuild, is that disirable? distcc requre major version be same and best to have minor version be same also
  
• How you invoke emerge? for crossdev build usually it is emerge-i686-pc-linux-musl
  
• You last ran crossdev still not produce i686-pc-linux-musl-g++, did you somehow USE=-cxx or something will disalbe g++ build?
  
• You symbolic link /usr/bin/g++ to /usr/bin/i686-pc-linux-musl-g++, this is wrong, this will produce 64bits code
  
• Your crossdev repository is at /var/db/repos/brave-overlay. I suspect your next sync might wipe it out.
  
• emerge-i686-pc-linux-musl --info

I ran