[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]
Re: [XaraXtreme-dev] Re: configure.in:305: error: possibly undefined macro: AM_GNU_GETTEXT
- From: Vasil Dimov <vd@xxxxxxxxxxx>
- Date: Tue, 6 Jun 2006 15:45:18 +0300
- Subject: Re: [XaraXtreme-dev] Re: configure.in:305: error: possibly undefined macro: AM_GNU_GETTEXT
On Tue, Jun 06, 2006 at 12:25:48PM +0100, Alex Bligh wrote:
[...]
>
> >There is still the more complicated issue with the file strings.h.
> >The problem is that FreeBSD's /usr/include/string.h does
> >#include <strings.h> which includes strings.h located in wxOil/
> >subdirectory instead of the system one (located in /usr/include) thus
> >resulting in a complete mess.
>
> On gcc we could fix this with -iquote wxOil instead of -I wxOil,
> but that is not (I think) portable (e.g. I don't know if icc
> supports it).
>
> In the old days we could fix this with -I-, but that is deprecated.
>
> We should expect system headers to be able to include other system
> headers successfully (which means they should go first on a -I
> line),
I have tried even adding -I/usr/include in front of all -I flags but
that does not help either :-/
> and I don't think there is any longer a non-deprecated
> portable way to search for '#include "foo.h"' but not
> '#include <foo.h>' - obviously this would be attractive.
>
> So all said and done, I reckon we should probably rename strings.h to
> camstring.h or similar as you suggest. I'm happy to do a rename. It's
> actually only used in 32 places and at least 11 of them (probably many
> more) are incorrect as it is in the pch.
>
Renaming seems the straightforward solution to me. It would be nice to
have this done.
--
Vasil Dimov
gro.DSBeerF@dv
Testing can show the presence of bugs, but not their absence.
-- Edsger W. Dijkstra