Re: Compiling FreeBSD with non-standard flags.

On Thu, Jul 29, 2004 at 02:32:59AM +0000, Alexander Kabaev wrote:
> Hello all,
> 
> > % make buildworld
> > .....
> > ===> libexec/atrun
> > cc -O2 -fomit-frame-pointer -pipe  -DATJOB_DIR=\"/var/at/jobs/\"  -DLFILE=\"/var/at/jobs/.lockfile\"  -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\"/var/at/spool\"  -DVERSION=\"2.9\" -DDAEMON_UID=1 -DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun  -c /usr/src/libexec/atrun/atrun.c
> > cc -O2 -fomit-frame-pointer -pipe  -DATJOB_DIR=\"/var/at/jobs/\"  -DLFILE=\"/var/at/jobs/.lockfile\"  -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\"/var/at/spool\"  -DVERSION=\"2.9\" -DDAEMON_UID=1 -DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun  -c /usr/src/libexec/atrun/gloadavg.c
> > cc -O2 -fomit-frame-pointer -pipe  -DATJOB_DIR=\"/var/at/jobs/\"  -DLFILE=\"/var/at/jobs/.lockfile\"  -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\"/var/at/spool\"  -DVERSION=\"2.9\" -DDAEMON_UID=1 -DDAEMON_GID=1  -DDEFAULT_BATCH_QUEUE=\'E\'  -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun   -o atrun atrun.o gloadavg.o
> > /usr/obj/usr/src/i386/usr/lib/libc.so: undefined reference to `pthread_mutex_destroy_int'
> > /usr/obj/usr/src/i386/usr/lib/libc.so: undefined reference to `pthread_cond_destroy_exp'
> > ..........
> > 
> 
> There were a number of reports of buildworld breakage due to people using
> non-default flags like -Os, -O2 and even -fomit-frame-pointer. While desire
> to squeeze the very last drop of performance out of their systems is 
> understandable goal, you should understand, that you are on your own while
> you are doing that, especially right after a major GCC version upgrade.
> 
> I will try to fix this particular breakage when other, more pressing issues
> have been addressed.

I was just reporting a bug... not ranting ;)
btw: -O2 is officially supported, isnt it? and tinderboxes also compiles with
-O2

anyway - thnx for great work in upgrading gcc!

roman