Subject: Re: current isn't building and I think it's
To: YAMAMOTO Takashi <>
From: Perry E. Metzger <>
List: current-users
Date: 12/26/2005 21:02:31
YAMAMOTO Takashi <> writes:
>> The firefox port is broken on -current because of an error in 'configure'
>> (see below).  I suspect the problem is related, but I'm not sure.
>> I tried adding the 'S' to the linflags in /usr/pkg/share/mk/, but
>> it didn't help.  (I see that /usr/share/mk/ already has the 'S'.)
>> Any thoughts?
>> configure:5213: checking for pthread_create in -lpthread
>> cc -o dummy dummy.c -O2 -I/usr/pkg/include -I/usr/include -I/usr/X11R6/include -DGLX_GLXEXT_LEGACY -I/usr/pkg/include/freetype2 -pip
>> e -ansi -Wall -I/usr/pkg/include -I/usr/include -I/usr/X11R6/include -DGLX_GLXEXT_LEGACY -I/usr/pkg/include/freetype2 -lpthread -Wl,
>> -R/usr/pkg/lib/firefox -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/lib -Wl,-R/usr/lib -L/usr/X11R6/lib -Wl,-R/usr/X11R6/lib -lm -lintl
> as __inline was converted to inline even for public headers,
> pre-C99 sources, including -ansi, are now broken.

The sources aren't broken. An old *compiler* is broken. "-ansi" tells
gcc to act like an ISO C90 compiler.

However, there should be no need to compile anything with -ansi though
-- it does not break programs to build them without turning off
C99. Is there a reason configure for firefox is insisting on -ansi???

If this is a widespread problem I can revert it very easily but I'm
not sure why one would compile with -ansi except in specialized cases,
such as if one wanted to catch things that would break older