Passing options to a 'make install clean'

Sean rsh.lists at
Fri Dec 31 22:04:41 PST 2004

Michael C. Shultz wrote:
>>Well I thought I would just let both of you know as I write this I
>>have started the rebuild of my system with "WITH_LIB32=yes" in the
>>make.conf. I will let you know how it goes.
>>I guess if you don't here from me for a while, then it did not go
>>well! 8-)
> I'd like to hear how it goes, either way if you don't mind. I've
> a feeling many people will be getting AMD64s and so I wish
> to stay up as much as possible on what it takes to support them.
> -Mike

Hi Mike,

Well here is what I did and what resulted.

-Added the "WITH_LIB32=yes" to make.conf.
-While I was at it I moved over to the new scheduler.
-Did the standard builds and installs of world and kernel.
-Started Openoffice build, command line below

-error during build of gcc, results below
. -I.././..//gcc-3.2.3/gcc/config -I.././..//gcc-3.2.3/gcc/../include 
ors.c -o errors.o
In file included from config.h:26,
                  from ../../gcc-3.2.3/gcc/errors.c:25:
../../gcc-3.2.3/gcc/config/i386/freebsd.h:143:1: warning: 
In file included from config.h:25,
                  from ../../gcc-3.2.3/gcc/errors.c:25:
../../gcc-3.2.3/gcc/config/i386/x86-64.h:76:1: warning: this is the 
location of the previous def
stage1/xgcc -Bstage1/ -B/usr/local/x86_64-portbld-freebsd6.0/bin/ 
-DIN_GCC    -g -O2 -W -Wall -W
write-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional 
-pedantic -Wno-long-long  -
  genflags.o rtl.o read-rtl.o bitmap.o ggc-none.o gensupport.o 
print-rtl.o errors.o ../libiberty/
./genflags .././..//gcc-3.2.3/gcc/config/i386/ > tmp-flags.h
Segmentation fault (core dumped)
gmake[2]: *** [s-flags] Error 139
gmake[2]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc'
gmake[1]: *** [stage2_build] Error 2
gmake[1]: Leaving directory `/usr/ports/lang/gcc32/work/build/gcc'
gmake: *** [bootstrap] Error 2
*** Error code 2

Stop in /usr/ports/lang/gcc32.
*** Error code 1

Stop in /usr/ports/editors/openoffice-1.1.

So basically the builds and installs made no difference to the gcc problem.
Some other system information, if it helps.
tardis# uname -a
FreeBSD 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Dec 
31 23:02:45 EST 2004 
sean at  amd64
tardis# gcc -v
Using built-in specs.
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 3.4.2 [FreeBSD] 20040728

One thing I see in the openoffice lines is a reference to 
Wasn't that the original name for the amd64 platform, before it was 
called amd64?
Perhaps a problem?

If you have something else you would like me to try, or looking for some 
more information on configurations, just ask, I do not mind.


More information about the freebsd-questions mailing list