| Summary: | ULONG_MAX defined as hex on freebsd, ULONG_MAX defined as int on GNU, breaks autoconf | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Sean Jensen-Grey <seanj> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 1.0-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Sean Jensen-Grey
2001-11-13 20:30:01 UTC
On Tue, Nov 13, 2001 at 12:23:28PM -0800, Sean Jensen-Grey wrote:
> Now my question is. Is this actually a bug?
This is a bug in either boa configure script or autoconf, I guess.
It's reading a C header file, so it should be expected to understand
anything which C can.
I'll close the PR, unless you feel strongly otherwise?
David.
State Changed From-To: open->closed Submitter is going to take it up with the boa guys. damn logic, you have a point. I'll check with the boa guys and see if they manually added that check or if it is an autoconf thing. go ahead and close the PR. Sean. On Tue, 13 Nov 2001, David Malone wrote: > On Tue, Nov 13, 2001 at 12:23:28PM -0800, Sean Jensen-Grey wrote: > > Now my question is. Is this actually a bug? > > This is a bug in either boa configure script or autoconf, I guess. > It's reading a C header file, so it should be expected to understand > anything which C can. > > I'll close the PR, unless you feel strongly otherwise? > > David. > |