Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 13, 2010, at 3:55 AM, Michael Haubenwallner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><br>On 12/11/2010 09:46 PM, Perry Smith wrote:<br><blockquote type="cite">I'm trying to do the "make install" of the prefix installer and I died with this:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">make[4]: Entering directory `/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix5.3.0.0/libcpp'<br></blockquote><blockquote type="cite">/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix5.3.0.0/./prev-gcc/xgcc -B/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix5.3.0.0/./prev-gcc/ -B/gsa/ausgsa/home/p/e/pedzan/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/powerpc-ibm-aix5.3.0.0/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/buildroot<br></blockquote>/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<br><blockquote type="cite">xgcc: Internal error: Killed (program cc1)<br></blockquote><br>Interesting - this works since ages on the AIX 5.3 boxes here...<br></div></blockquote><div><br></div>Yes. As a curiosity, I pulled down 4.2.4 and compiled it on my own sandbox and it did fine.</div><div><br><blockquote type="cite"><div><br>And there isn't anything in prefix-launcher-trunk over prefix-launcher-2.1.0<br>that should have any influence for AIX 5.3, only AIX 6.1:<br><a href="http://prefix-launcher.svn.sourceforge.net/viewvc/prefix-launcher/prefix-launcher/trunk/ChangeLog?view=log">http://prefix-launcher.svn.sourceforge.net/viewvc/prefix-launcher/prefix-launcher/trunk/ChangeLog?view=log</a><br><br><blockquote type="cite">Please submit a full bug report.<br></blockquote><blockquote type="cite">See <URL:http://gcc.gnu.org/bugs.html> for instructions.<br></blockquote><blockquote type="cite">make[4]: *** [charset.o] Error 1<br></blockquote><br>Are you able to compile 'charset.o' with '-save-temps' compiler flag?<br></div></blockquote><div><br></div><div>Its been a long weekend with many misadventures. I did not know about the INTERACTIVE method and I copied and pasted the compile command (above) 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. So, I wasn't using *exactly* the right environment.</div><br><blockquote type="cite"><div>Some hints for prefix-launcher:<br> $ gmake config gcc_BUILDMODE=INTERACTIVE<br> $ gmake gcc SHELL=/bin/bash<br>Instead of running src_compile() from gcc/gcc.build, you get a bash-prompt where<br>you can run (parts of) src_compile manyally. However, this isn't Ctrl-C save.<br><br><blockquote type="cite">make[4]: Leaving directory `/gsa/ausgsa-h2/01/pedzan/src/prefix-launcher-2.1.0/buildroot/gcc/p51.powerpc-ibm-aix5.3.0.0/libcpp'<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">So far, I've not found a similar bug report.<br></blockquote><blockquote type="cite">I'm trying it a second time but I assume its not going to work.<br></blockquote><blockquote type="cite">This is on stage 2 which is a bit odd.<br></blockquote><br>Does it work to build vanilla gcc-4.2.4 out-of-the-box?<br></div></blockquote><div><br></div>Yes.</div><div><br></div><div>Probably I'm going to start over again but here are some clues.</div><div><br></div><div>First, my build scripts for gcc always do:</div><div><br></div><div>ulimit -S -d unlimited</div><div><br></div><div>I can't remember why I've added that over the years. But build script that worked did this:</div><div><br></div><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">ulimit -S -d unlimited</font></div><div><font class="Apple-style-span" color="#000000">export CONFIG_SHELL=/usr/local/bin/bash</font></div><div><font class="Apple-style-span" color="#000000">( ../../src/gcc-4.2.4/configure -v \</font></div><div><font class="Apple-style-span" color="#000000"> --disable-nls \</font></div><div><font class="Apple-style-span" color="#000000"> --enable-threads=aix \</font></div><div><font class="Apple-style-span" color="#000000"> --with-libiconv-prefix=/usr \</font></div><div><font class="Apple-style-span" color="#000000"> --enable-languages=c,c++ && echo "configure returned $?" ) > C-OUT 2>&1</font></div><div>( gmake bootstrap && echo "gmake returned $?" ) > M-OUT 2>&1 &</div></blockquote><div><div><br></div></div><div>which is almost what your scripts did. That script worked.</div><div><br></div><div>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:</div><div><br></div><div>1) I *forgot* to do the CONFIG_SHELL (and I'm paying the price for that. I plan to open a defect on ksh. I've discovered that not only does it make tons of temps but the temps are wide open... a glaring security hole. But, that will take a battle plus a year to get out the door and they will likely fix it for new releases.)</div><div>2) I did the ulimit change above</div><div>3) I moved my source and destination directories to much short paths (trying to avoid the arg list too long problem).</div><div>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.</div><div><br></div><div>So far, it is still going but I'm not 100% done with gcc yet but I'm past all the previous failure points.</div><div><br></div><div>I plan to start over again. I want to redo it with CONFIG_SHELL set, ulimit set, and the newer gcc (at the new location) and see how that goes.</div><div><br></div><div>Can we set CONFIG_SHELL inside the top level Makefile? I'm going to just add it to my .bash_profile too.</div><div><br></div><div>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.</div><div><br></div><div>Thanks!!! I'm still plugging. (I haven't read your other email yet).</div><div><br></div><div>Perry</div><div><br></div></div></body></html> |
|
