Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal

I can confirm now that ONE of these core dumps ("conftest signal 12") 
messages is being generated when I (re)compile the apache2 port. I still 
don't know which other port generates the other identical message in my 
system log file.

Is there any chance that the maintainer of the apache2 port can look into 
this? Thanks in advance!!

Zoltan

> Dan Nelson said:
>> In the last episode (Nov 06), Zoltan Frombach said:
>>> I've recently migrated to FreeBSD 5.3. I just upgraded my system to
>>> the brand new 5.3-RELEASE version, and first of all, I have to tell
>>> you that it works really great!! I love it! Thank you guys for the
>>> great work!!
>>>
>>> But I run into a somewhat weird problem. After the successful
>>> migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I
>>> recompile all installed ports with 'portupgrade -af', I get this in
>>> my system log file:
>>>
>>> Nov  6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal
>>> 12  (core dumped)
>>> Nov  6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal
>>> 12  (core dumped)
>>>
>>> But portupgrade proceeds and seemingly re-compiles all installed
>>> ports anyway (at least this is what I believe). When I look for the
>>> .core file(s), I can't find any on my hard drive anywhere! If the
>>> core was really dumped, then where did the .core files go? And how
>>> can I find out which port(s) are causing these problems? What is this
>>> signal 12 with conftest means anyway? I couldn't find anything about
>>> it by Googling...
>>
>> #define SIGSYS 12 /* non-existent system call invoked */
>>
>> This is an unusual error to be getting, but it's possible that one of
>> the ports you tried to install tried to check for a syscall that either
>
> It's apache, i get these too.