On Wednesday, August 16 at 05:16 PM, quoth Tim Prince:
>> Does anyone have any idea what might be going wrong? I looked
>> through di_bootagent.c and didn't see anything that looked
>> particularly complicated, so I have no idea why the compiler would
>> *segfault*. And yet... I know LAM supports these compilers, so I
>> thought I'd ask if this is something others have come across
>> before.
>Did you examine the contents of your unistd.h, after pre-processing, at
>the point indicated? Does this step work for you with gcc, and does it
>use the same pre-processed source?
I haven’t compared, but that’s a good idea, I’ll do that. Yes, it
compiles perfectly with gcc.
>You haven't given a clue on the identity of your linux distro, so it
>is double important to show what actually is in the source code at
>the failure point.
Ah, sorry: it’s RedHat Enterprise Linux 3, with all the current
security patches.
~Kyle
--
Once again the conservative sandwich-heavy portfolio pays off for the
hungry investor!
-- Zoidberg
- application/pgp-signature attachment: stored
|
