Subject: Re: pkgsrc and OS X
To: pkgsrc-user MailingList <pkgsrc-users@NetBSD.org>
From: Philipp Riegger <philipp@riegger.name>
List: pkgsrc-users
Date: 10/18/2006 23:59:07
On Oct 18, 2006, at 10:54 PM, Christian Biere wrote:
>>>> The issues with gprolog are obviously not specific pkgsrc
>>>> but original bugs in the software.
>>>
>>> I had a look at darwinports and they just used gcc-3. What is the
>>> "normal" gcc-version used in netbsd? 3 or 4?
>>
>> Ok, i tried gcc-3 and it just built. So, does pkgsrc use gcc3 or
>> gcc4? An easy workaround for OS X might be to check if /usr/bin/
>> gcc-3.3 exists, tell configureto use it if it exists and die with an
>> error message if not.
>
> pkgsrc will use whatever C compiler you have installed. Of course,
> it only
> knows about GCC and maybe whatever native compiler exists for a
> given platform.
> If a program doesn't build with GCC 4 that simply means it's
> broken. Since GCC
> gets more strict with each release - which is good - lots of
> programs will not
> build with GCC 4 until someone fixes them. The bugs might also show
> up in
> platform-specific parts of the code, so pkgsrc might build it
> successfully on
> one platform but not another.
Ok. I would be interested if the problem only occurs on OS X with gcc
4 or also on NetBSD with gcc 4. Does anybody know? Is this package
broken for gcc 4 on OS X or in general?
> So GCC 3.x might be the better choice for you for the time being
> unless you
> can fix the bugs yourself. You should certainly report these bugs
> to the
> original authors.
I will have a look at it, but i think i don't like the gnu bug report
system. Maybe i find out some more.
Philipp