I unfortunately have nothing new to add here. I know that the PGI compilers
had problems with some versions, but I was under the impression that their
most recent patch levels had fixed most of the problems.
I have not personally tested 7.1.2 with the most recent PGI, however.
On 8/17/06 12:39 AM, "Kyle Wheeler" <kbwheel_at_[hidden]> wrote:
> 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
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
|
