On 12/13/2010 03:32 PM, Perry Smith wrote:
>>> make: Entering directory `/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix188.8.131.52/libcpp'
>>> /gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix184.108.40.206/./prev-gcc/xgcc -B/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix220.127.116.11/./prev-gcc/ -B/gsa/ausgsa/home/p/e/pedzan/prefix-launcher-2.1.0/powerpc-ibm-aix18.104.22.168/powerpc-ibm-aix22.214.171.124/bin/ -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp -I. -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp/../include -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp/include -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -pedantic -Wno-long-long -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp -I. -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp/../include -I/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildro
>> /gcc/gcc-4.2.4/libcpp/include -c -o charset.o -MT charset.o -MMD -MP -MF .deps/charset.Po /gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/gcc-4.2.4/libcpp/charset.c
>>> xgcc: Internal error: Killed (program cc1)
>> Interesting - this works since ages on the AIX 5.3 boxes here...
> Yes. As a curiosity, I pulled down 4.2.4 and compiled it on my own sandbox and it did fine.
>> Are you able to compile 'charset.o' with '-save-temps' compiler flag?
> Its been a long weekend with many misadventures.
This is how it works, unfortunately
> I did not know about the INTERACTIVE method and I copied and pasted the compile command (above)
The INTERACTIVE feature is an internal detail and for debugging purpose only.
However, there is some doc in prefix-launcher-*/BUILDING.
> and added -save-temps and it compiled fine. So I then just did "make" in that directory -- which worked.
> Moved up and did "make" again and that eventually failed with arg list too long.
"arg list too long" rings the "ncargs defaults to 4" bell:
$ lsattr -E -l sys0 -a ncargs
We do have it set to 40 here, but on some AIX6.1 I've seen this set to 256:
$ chdev -l sys0 -a ncargs=40
> So, I wasn't using *exactly* the right environment.
This might be the reason: Inside prefix-launcher the environment is a little
larger than outside, which may trigger the arg list too long problem.
Thing is that both the commandline argument /plus/ the environment variables
are counted in here for 'ncargs'.
There is another thing: You could 'source' the installed environment-file of prefix-launcher:
$ . /prefix/for/launcher/chost/bin/prefix-launcher-env.sh
Then you should have a similar environment than within the builds,
except for a package's local build-variables set within pkg/pkg.build.
> First, my build scripts for gcc always do:
> ulimit -S -d unlimited
> I can't remember why I've added that over the years. But build script that worked did this:
Seems like you've hit the arg list too long error before.
> As I mentioned, the "make" above ended with arg list too long.
> I hit that again doing some other path. So, I restarted your process with these changes:
> 1) I *forgot* to do the CONFIG_SHELL (and I'm paying the price for that.
> I plan to open a defect on ksh.
Good to know you have resources to do so.
> 4) Used a different gcc. Before I was using my newly built gcc 4.5.0 and this last trip I'm using 4.3.1.
It should work with any Ansi-C compiler that is able to bootstrap gcc-4.2.4.
For what it's worth, on AIX 6.1 I've recently used gcc-4.2.0 from the
"AIX Toolbox for Linux Applications".
> Can we set CONFIG_SHELL inside the top level Makefile? I'm going to just add it to my .bash_profile too.
It isn't that easy. The only thing I could do is to set
CONFIG_SHELL = $(SHELL)
as I cannot have an idea where to find some bash in that Makefile.
Additionally, bash isn't a technical requirement for prefix-launcher on any platform.
> One other suggestion, I assumed that the install of the prefix-launcher was going to be a half minute adventure
> and the big adventure was going to come while using it.
> My suggestion is mention that installing it will take a long time.
> Also, give some help (like you just did) about doing things piecemeal if things go wrong.
You're welcome to draft up something you'd like to read (in the MediaWiki),
and I'll be happy to review and add it.
Gentoo on a different level