From tony at stclaire.com Wed Feb 1 02:26:10 2012 From: tony at stclaire.com (tony at stclaire.com) Date: Tue, 31 Jan 2012 21:26:10 -0500 Subject: [Aboriginal] cpp in the native environment Message-ID: <51387.1328063170@stclaire.com> Never mind, I think a looped wrapper using "-x c" for non-c files may suffice. ------------------------- Message sent via Atmail Open - http://atmail.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob at landley.net Wed Feb 1 04:00:14 2012 From: rob at landley.net (Rob Landley) Date: Tue, 31 Jan 2012 22:00:14 -0600 Subject: [Aboriginal] cpp in the native environment In-Reply-To: <201201311307.q0VD7dk04341@ns1.ceenet.com> References: <201201311307.q0VD7dk04341@ns1.ceenet.com> Message-ID: <4F28B8CE.70309@landley.net> On 01/31/2012 05:58 AM, tony at stclaire.com wrote: > Hello Rob, > > Any chance to include the full cpp preprocessor in aboriginal. The > problem with cc -E is it will not process includes. Although cpp is not > used by much in linux it has proven handy as a non-c code preprocessor. It processed includes for me? I can apply ccwrap to cpp if there's a reason to, I just haven't bothered yet because the shell wrapper was trivial to do and Worked For Me. What's the test case? > Any chance it will make it in 1.1.1 ? I'm uploading 1.1.1 now. It can go in next release if needed... Rob 1328068814.0 From rob at landley.net Wed Feb 1 04:08:02 2012 From: rob at landley.net (Rob Landley) Date: Tue, 31 Jan 2012 22:08:02 -0600 Subject: [Aboriginal] cpp in the native environment In-Reply-To: <51387.1328063170@stclaire.com> References: <51387.1328063170@stclaire.com> Message-ID: <4F28BAA2.7000103@landley.net> On 01/31/2012 08:26 PM, tony at stclaire.com wrote: > > Never mind, I think a looped wrapper using "-x c" for non-c files may > suffice. I'd appreciate a test case so I know if what I'm implementing works. Right now I haven't got anything that actually uses cpp... Rob 1328069282.0 From tony at stclaire.com Wed Feb 1 18:18:28 2012 From: tony at stclaire.com (Tony Tonchev) Date: Wed, 01 Feb 2012 13:18:28 -0500 Subject: [Aboriginal] cpp in the native environment In-Reply-To: <4F28BAA2.7000103@landley.net> References: <51387.1328063170@stclaire.com> <4F28BAA2.7000103@landley.net> Message-ID: <4F2981F4.8070303@stclaire.com> The existing wrapper does in fact work fine and handles the includes as you mentioned. In my case, I needed to call the wrapper as "cpp -P -w -x c -o file.out file.in" which is synonymous in both the aboriginal cpp wrapper as well as the original cpp binary. Originally, my script was running cpp -P -w file.in file.out, which is incompatible with the wrapper although a valid cpp syntax.. The cpp binary does not care about a source type, while cc does. The above resolves that issue and any other anomalies that caused my confusion. Moving on ;-) On 1/31/2012 11:08 PM, Rob Landley wrote: > On 01/31/2012 08:26 PM, tony at stclaire.com wrote: > >> >> Never mind, I think a looped wrapper using "-x c" for non-c files may >> suffice. >> > I'd appreciate a test case so I know if what I'm implementing works. > Right now I haven't got anything that actually uses cpp... > > Rob > -- Tony Tonchev St. Claire, inc. 248-553-2474 1328120308.0 From rob at landley.net Sat Feb 4 20:24:06 2012 From: rob at landley.net (Rob Landley) Date: Sat, 04 Feb 2012 14:24:06 -0600 Subject: [Aboriginal] Possible regression in Aboriginal 1.1.1 (vs 1.1.0) In-Reply-To: <4F2D9303.3000704@landley.net> References: <4F2D8645.7050903@gmail.com> <4F2D88C8.80709@gmail.com> <4F2D9303.3000704@landley.net> Message-ID: <4F2D93E6.9090403@landley.net> I should remember to send this stuff to the list... On 02/04/2012 02:20 PM, Rob Landley wrote: > On 02/04/2012 01:36 PM, Piotr Karbowski wrote: >>> Sadly I am unable to even understand the error so I have no idea where I >>> can look. >> >> After some research I found that libgcrypt-config fail with fgrep: no >> such file. After linking /bin/fgrep to /bin/busybox it does work. > > I was about to say that the most likely cause of regressions is the > switch from busybox defconfig (almost 350 commands) to a specified > config (about 125 commands). There could easily be a few that people > actually use which I didn't include. > > I just added FEATURE_GREP_FGREP_ALIAS=y to baseconfig-busybox, it'll be > in the next release (which might be at the end of the month, I've got > some catching up to do with the new uClibc release and such...) > > Thanks, > > Rob 1328387046.0 From blink at bojary.koba.pl Mon Feb 13 10:50:32 2012 From: blink at bojary.koba.pl (Paul Onyschuk) Date: Mon, 13 Feb 2012 11:50:32 +0100 Subject: [Aboriginal] cpp in the native environment In-Reply-To: <4F28BAA2.7000103@landley.net> References: <51387.1328063170@stclaire.com> <4F28BAA2.7000103@landley.net> Message-ID: <20120213115032.5c193a11.blink@bojary.koba.pl> On Tue, 31 Jan 2012 22:08:02 -0600 Rob Landley wrote: > > I'd appreciate a test case so I know if what I'm implementing works. > Right now I haven't got anything that actually uses cpp... > Apologies for delay, but I was in the wilderness for 2 weeks. I found that some configure scripts of Xorg parts are calling cpp directly (usage is pretty much the same): libX11, libXext, libXt, xorg-server, xf86-video-sis. You can check configure script around line 13000 of libX11 version 1.3.5 [1]. I'm not good at reading configure scripts, but I managed to isolate relevant parts. I'm attaching 2 small shell scripts: cpp-undef.sh and cpp-whitespace.sh. With 'gcc -E "$@"' wrapper it ends up with error "rawcc: no input files". Hope this case scenarios will help. I patched temporarily configure scripts, but I guess I'll hit direct cpp usage later with other packages. [1] http://mi.mirror.garr.it/mirrors/x.org/individual/lib/libX11-1.3.5.tar.gz -------------- next part -------------- A non-text attachment was scrubbed... Name: cpp-undef.sh Type: application/x-sh Size: 475 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cpp-whitespace.sh Type: application/x-sh Size: 425 bytes Desc: not available URL: From rob at landley.net Fri Feb 17 11:54:10 2012 From: rob at landley.net (Rob Landley) Date: Fri, 17 Feb 2012 05:54:10 -0600 Subject: [Aboriginal] cpp in the native environment In-Reply-To: <20120213115032.5c193a11.blink@bojary.koba.pl> References: <51387.1328063170@stclaire.com> <4F28BAA2.7000103@landley.net> <20120213115032.5c193a11.blink@bojary.koba.pl> Message-ID: <4F3E3FE2.1090802@landley.net> On 02/13/2012 04:50 AM, Paul Onyschuk wrote: > On Tue, 31 Jan 2012 22:08:02 -0600 > Rob Landley wrote: > >> >> I'd appreciate a test case so I know if what I'm implementing works. >> Right now I haven't got anything that actually uses cpp... >> > > Apologies for delay, but I was in the wilderness for 2 weeks. Between day job and toybox eating my spare time, I'm at least as distracted. :) > I found that some configure scripts of Xorg parts are calling cpp > directly (usage is pretty much the same): libX11, libXext, libXt, > xorg-server, xf86-video-sis. You can check configure script around > line 13000 of libX11 version 1.3.5 [1]. > > I'm not good at reading configure scripts, but I managed to isolate > relevant parts. I'm attaching 2 small shell scripts: cpp-undef.sh and > cpp-whitespace.sh. > > With 'gcc -E "$@"' wrapper it ends up with error "rawcc: no input > files". Hope this case scenarios will help. > > I patched temporarily configure scripts, but I guess I'll hit direct > cpp usage later with other packages. I'll just add cpp support to ccwrap and see if that helps. I've got a 3 day weekend coming up, should be able to catch up on this sort of thing then... Rob 1329479650.0 From clyde.oxman at gmail.com Sun Feb 19 14:58:02 2012 From: clyde.oxman at gmail.com (Clyde Oxman) Date: Sun, 19 Feb 2012 16:58:02 +0200 Subject: [Aboriginal] Distcc not distributing Message-ID: <4F410DFA.4000606@gmail.com> Hi All, I'm trying to set up some build control images, and have unfortunately found that with the latest aboriginal hg tip, distcc is not working. The dev-environment.sh script seems to setup distcc correctly, launching the daemon on the host and creating the distcc_links directory, but in the emulated target environment, I constantly get 'Warning: failed to distribute, running locally instead". Looking at the distccd.log file, I find that it seems that distccd on the host is continually failing to run gcc with 'exit code 110'. Has anyone run into this? I would really like to take full advantage of the awesome aboriginal framework to speed up these builds. Clyde -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob at landley.net Sun Feb 19 23:42:36 2012 From: rob at landley.net (Rob Landley) Date: Sun, 19 Feb 2012 17:42:36 -0600 Subject: [Aboriginal] Distcc not distributing In-Reply-To: <4F410DFA.4000606@gmail.com> References: <4F410DFA.4000606@gmail.com> Message-ID: <4F4188EC.7060502@landley.net> On 02/19/2012 08:58 AM, Clyde Oxman wrote: > Hi All, > > I'm trying to set up some build control images, and have unfortunately > found that with the latest aboriginal hg tip, distcc is not working. Sigh. Distcc is crotchety, and it has the nasty tendency to fail _silently_, and I have no control over its' decisions when to distribute and when not to. (Sometimes it thinks it's "faster" to just compile it locally, which is pretty much never the case in this setup...) I really need to write a new one... > The dev-environment.sh script seems to setup distcc correctly, launching > the daemon on the host and creating the distcc_links directory, but in > the emulated target environment, I constantly get 'Warning: failed to > distribute, running locally instead". > > Looking at the distccd.log file, I find that it seems that distccd on > the host is continually failing to run gcc with 'exit code 110'. > > Has anyone run into this? Oh. Is it related to: http://landley.net/hg/aboriginal/rev/1041 I fixed host-tools but may need to similarly fix the distcc setup script... Rob 1329694956.0 From rob at landley.net Sun Feb 19 23:46:52 2012 From: rob at landley.net (Rob Landley) Date: Sun, 19 Feb 2012 17:46:52 -0600 Subject: [Aboriginal] Distcc not distributing In-Reply-To: <4F410DFA.4000606@gmail.com> References: <4F410DFA.4000606@gmail.com> Message-ID: <4F4189EC.6020400@landley.net> On 02/19/2012 08:58 AM, Clyde Oxman wrote: > Hi All, > > I'm trying to set up some build control images, and have unfortunately > found that with the latest aboriginal hg tip, distcc is not working. > > The dev-environment.sh script seems to setup distcc correctly, launching > the daemon on the host and creating the distcc_links directory, but in > the emulated target environment, I constantly get 'Warning: failed to > distribute, running locally instead". > > Looking at the distccd.log file, I find that it seems that distccd on > the host is continually failing to run gcc with 'exit code 110'. > > Has anyone run into this? No, that can't be it. That fix was for the host toolchain, and distcc is using a cross compiler built for the target. Can you run binaries out of the distcc_links directory? Also, if you strip the & off the end and stick an "echo" before this line in dev-environment.sh: PATH="$(pwd)/distcc_links" "$(which distccd)" --no-detach --daemon \ --listen 127.0.0.1 -a 127.0.0.1 -p $PORT --jobs $CPUS \ --log-stderr --verbose 2>distccd.log & Does the PATH and such look right? Thanks, Rob 1329695212.0 From clyde.oxman at gmail.com Mon Feb 20 08:07:12 2012 From: clyde.oxman at gmail.com (Clyde Oxman) Date: Mon, 20 Feb 2012 10:07:12 +0200 Subject: [Aboriginal] Distcc not distributing In-Reply-To: <4F4189EC.6020400@landley.net> References: <4F410DFA.4000606@gmail.com> <4F4189EC.6020400@landley.net> Message-ID: <4F41FF30.8090708@gmail.com> Hi Rob, I checked that I can run the bins from distcc_links (at least gcc), by simply doing: PATH=/path/to/distcc_links gcc --version This reports rawcc 4.2.1 as expected. echo-ing the distccd execution line from dev-environment.sh shows the following, which looks correct to me! PATH=/path/to/aboriginal/tip/build/system-image-mipsel/distcc_links /path/to/aboriginal/tip/build/system-image-mipsel/../host/distccd --no-detach --daemon --listen 127.0.0.1 -a 127.0.0.1 -p 25602 --jobs 1 --log-stderr --verbose BTW: off-topic, the zlib version in the various build-control images in your hg repo is no longer available from the zlib site. I've bumped the version, if you want the (trivial) patches. > ------------------------------------------------------------------------ > > Rob Landley > February 20, 2012 1:46 AM > > > > No, that can't be it. That fix was for the host toolchain, and distcc > is using a cross compiler built for the target. > > Can you run binaries out of the distcc_links directory? Also, if you > strip the & off the end and stick an "echo" before this line in > dev-environment.sh: > > PATH="$(pwd)/distcc_links" "$(which distccd)" --no-detach --daemon \ > --listen 127.0.0.1 -a 127.0.0.1 -p $PORT --jobs $CPUS \ > --log-stderr --verbose 2>distccd.log & > > Does the PATH and such look right? > > Thanks, > > Rob > ------------------------------------------------------------------------ > > Clyde Oxman > February 19, 2012 4:58 PM > > > Hi All, > > I'm trying to set up some build control images, and have unfortunately > found that with the latest aboriginal hg tip, distcc is not working. > > The dev-environment.sh script seems to setup distcc correctly, > launching the daemon on the host and creating the distcc_links > directory, but in the emulated target environment, I constantly get > 'Warning: failed to distribute, running locally instead". > > Looking at the distccd.log file, I find that it seems that distccd on > the host is continually failing to run gcc with 'exit code 110'. > > Has anyone run into this? > > I would really like to take full advantage of the awesome aboriginal > framework to speed up these builds. > > Clyde > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: compose-unknown-contact.jpg Type: image/jpeg Size: 1421 bytes Desc: not available URL: