On Wed, 2003-06-18 at 04:29, Tom Lane wrote:
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > configure: WARNING: sys/select.h: present but cannot be compiled
> > configure: WARNING: sys/select.h: check for missing prerequisite headers?
> > [many similar]
>
> <> do these headers assume
> <> do these headers assume as a
> prerequisite on your system?
I don't know - I'll check
> Not sure why it'd have just now broken, though. Take a look at the most
> recent commits to the configure stuff if you need clues.
I haven't tried a build for a few weeks...
Chris
---
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> configure: WARNING: sys/select.h: present but cannot be compiled
> configure: WARNING: sys/select.h: check for missing prerequisite headers?
> [many similar]
<> do these headers assume as a
prerequisite on your system?
Not sure why it'd hav
configure: WARNING: sys/select.h: present but cannot be compiled
configure: WARNING: sys/select.h: check for missing prerequisite headers?
configure: WARNING: sys/select.h: proceeding with the preprocessor's result
checking for sys/select.h... yes
checking sys/sem.h usability... no
checking sys/sem
