[Tfug] Compiling with GCC 4.1.0

[Felix Tilley]

Including

#include <unistd.h>

seems to help.  I have no idea why.

The most frequent warning and error message is something like

implicit redefinition of built in function exit.

Sorry for the delay.  I was out of town for a few days.

Felix Tilley


>
> Message: 2
> Date: Sun, 22 Jul 2007 22:42:17 -0700
> From: Brian Murphy <murphy+tfug at email.arizona.edu>
> Subject: Re: [Tfug] Compiling with GCC 4.1.0
> To: tfug at tfug.org
> Message-ID: <20070722224217.opwe80k040wkc0co at www.email.arizona.edu>
> Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
>
> Newer gcc releases follow the standards closer than older versions.
>
> That said, it's impossible to say if this is your problem since you
> choose not to include specifics in your post.
>
> Brian
>
> Quoting Felix Tilley <fetilley at earthlink.net>:
>> I have had a lot of problems compiling programs with
>> GCC 4.1.0.  I suspect the C header files have been
>> reorganized under GCC 4+.
>>
>> I am trying to compile C programs from the late 1990s
>> and early 2000s.
>>
>> I think the #include statements have to be increased.
>>
>> This is not stuff I have written myself.  This stuff I downloaded
>> from universities.
>> n
>> Felix
>>