(1) distcc[326] (dcc_trace_version) distcc 2.18.3 x86_64-pc-linux-gnu; built Aug 26 2008 11:29:50
You're using distcc 2.18.3; the latest version of distcc is 3.0. (2) exec on 10.0.0.1: ... Is 10.0.0.1 your server? (3) exec on 10.0.0.1: x86_64-pc-linux-gnu-gcc -O2 -pipe -ffast-math -march=core2 -c -o cmatrix.o cmatrix.c Your compilation command is "x86_64-pc-linux-gnu-gcc ..." but you didn't mention that command name at all in the output of ls -la in your first email. (4) distcc[326] (dcc_set_path) setting PATH=/usr/local/sbin:/sbin:/usr/sbin:/usr/lib64/portage/bin:/usr/local/bin:/bin:/usr/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.1:/usr/qt/3/bin Your PATH is /usr/local/sbin:/sbin:/usr/sbin:/usr/lib64/portage/bin:/usr/local/bin:/bin:/usr/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.1:/usr/qt/3/bin. Also, I'm wondering about /usr/x86_64-pc-linux-gnu/gcc-bin/4.3.1 in your PATH... do you need that? On Wed, Aug 27, 2008 at 3:12 PM, Daniel Beecham <[EMAIL PROTECTED]> wrote: > Fergus Henderson wrote: > >> On Wed, Aug 27, 2008 at 10:53 AM, Daniel Beecham <[EMAIL PROTECTED]> >> wrote: >> >> >> >>> Fergus Henderson wrote: >>> >>> >>> >>>> On Tue, Aug 26, 2008 at 3:05 PM, Daniel Beecham <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>> >>>> >>>> >>>> >>>>> Hi there everyone. >>>>> First post here, so to introduce me, I'm Daniel. :-) >>>>> >>>>> I have three computers, a Gentoo hardened server, a Gentoo desktop and >>>>> a >>>>> Gentoo laptop. All run core2duo, but i don't want to give the server >>>>> anything unstable, like the gcc 4.3. >>>>> >>>>> Well, anyway, i've compiled gcc 4.3 (called via /usr/bin/gcc-4.3.1), >>>>> and >>>>> i >>>>> want everything compiled by the server (for the laptop/desktop) via >>>>> distcc >>>>> to be of that version. Searching, i've found ( >>>>> http://lists.samba.org/archive/distcc/2006q4/003468.html) a previous >>>>> mail >>>>> by this mailing list where Patrick shows his way of doing it. Here's >>>>> how >>>>> it >>>>> looks for me (thank you, Patrick): >>>>> >>>>> sh-3.2# cd /usr/lib/distcc/bin/ >>>>> sh-3.2# ls -la >>>>> total 16 >>>>> drwxr-xr-x 3 root root 4096 Aug 26 20:05 . >>>>> drwxr-xr-x 3 root root 4096 Aug 26 13:04 .. >>>>> drwxr-xr-x 2 root root 4096 Aug 26 15:30 .backup >>>>> -rw-r--r-- 1 distcc 240 0 Aug 26 15:13 .keep_sys-devel_distcc-0 >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:28 c++ -> wrapper >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:28 cc -> wrapper >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:28 g++ -> wrapper >>>>> lrwxrwxrwx 1 root root 15 Aug 26 15:30 g++-4.3.1 -> /usr/bin/distcc >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:28 gcc -> wrapper >>>>> lrwxrwxrwx 1 root root 15 Aug 26 15:29 gcc-4.3.1 -> /usr/bin/distcc >>>>> -rwxr-xr-x 1 root root 60 Aug 26 15:27 wrapper >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:30 x86_64-pc-linux-gnu-c++ -> >>>>> wrapper >>>>> lrwxrwxrwx 1 root root 7 Aug 26 15:30 x86_64-pc-linux-gnu-g++ -> >>>>> wrapper >>>>> sh-3.2# cat wrapper >>>>> #!/bin/bash >>>>> exec /usr/lib/distcc/bin/g${0:$[-2]}-4.3.1 "$@" >>>>> >>>>> But, trying to compile, it tells me the gcc 4.3-only flag -march=core2 >>>>> is >>>>> a >>>>> bad value. (as if it's using gcc 3.4.6. Am i doing something wrong? >>>>> >>>>> >>>>> >>>>> >>>> Did you add /usr/lib/distcc/bin to the start of your PATH? >>>> What's the compilation command? >>>> Which distcc version are you using? >>>> For debugging, try adding "set -x" (after the #! line) to your bash >>>> wrapper >>>> script, and set DISTCC_VERBOSE=1. >>>> >>>> >>>> >>>> >>>> >>> Hmm, PATH on the client machine has /usr/lib/distcc/bin at first, >>> >>> >> >> >> Good. >> >> >> >> >>> as well as the server /etc/profile, >>> >>> >> >> >> That shouldn't be necessary, and might be harmful. >> >> >> >> >>> however, distcc echoes >>> something along the lines with "distcc 2.18.3 trace: compiler name is >>> x86_64-pc-linux-gnu-gcc, setting PATH="/usr/local/sbin:/usr....". That >>> must >>> be the problem. >>> >>> >> >> >> distcc removes its own directory from the PATH, before searching for the >> compiler, to ensure that you don't end up having distcc recursively invoke >> itself. >> >> If that is what's causing the problem, it might work better if you put the >> symlinks to "wrapper" in a different directory than the symlinks to >> distcc. >> >> Otherwise, please attach the full output from a distcc command with >> DISTCC_VERBOSE=1. >> >> > > http://rafb.net/p/SSUt3b52.html > There you go. :-) > -- Fergus Henderson <[EMAIL PROTECTED]>
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc