[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon, 5 Feb 2007 07:48:20 +0900
On Sun, Feb 04, 2007 at 11:45:25AM -0800, Ben Pfaff wrote:
Jason Stover <address@hidden> writes:
> The latest checkout of gnulib puts a a couple of restricted
> qualifiers in declarations in string.h. This breaks the OBSD
> build with gcc 3.3.5.
> restrict is part of c99, right?
> So gcc 3.3.5 is breaking because it doesn't know about
> Shouldn't a portability library not bother with what seems like a kind
> of optimization that restrict is for? I mean, isn't that a decision
> best left to the compiler?
The configure script is supposed to detect whether the compiler
supports the "restrict" keyword. If it doesn't, it should add
to config.h, so that any use of restrict is dropped by the
Can you check whether your config.h defines restrict this way?
If it doesn't, then we should figure out why. If it does, then
the most likely problem is that the source file or files that
trigger the error are forgetting to #include <config.h> at the
top. Every PSPP source file should #include <config.h> as the
first thing it does.
But it seems that the offending file in this case is gl/memmem.c
I think this ought to have
at its head. So perhaps this problem should be discussed on the
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.
Description: Digital signature
- restrict, Jason Stover, 2007/02/04
- Re: restrict, Ben Pfaff, 2007/02/04
- Re: restrict,
John Darrington <=