[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gnu-libiconv] Attempting to compile configure libiconv with onl

From: Randall S. Becker
Subject: Re: [bug-gnu-libiconv] Attempting to compile configure libiconv with only c99
Date: Sun, 10 Jan 2016 12:28:46 -0500

> Daiki Ueno writes:
> > "Randall S. Becker" <address@hidden> writes:
> > This may or may not be a defect, but I need some help. I am trying to
> > build libiconv (1.14) on an HPE NonStop server that has c89 and c99;
> > neither of which support the GCC extension #include_next, and porting
> > GCC is not an option. This seems to be more an issue in libcharset and
> > srclib that are on the tarball. There does not seem to be an option
> > documented (or support for) in configure to use standard mechanisms
> > for resolving #include loops. Does a recipe exist for building on this
> > type of system? I need to change config.sub to support the platform
> > regardless, so options there are available - if that helps. The bug
> > seems to be that libiconv will only build on systems supporting the
> extension, is that the case now?
> According to the documentation of the 'include_next' module in Gnulib
> by libiconv), #include_next is only used when the compiler supports it,
> otherwise #include is used.  See:
> http://git.savannah.gnu.org/cgit/gnulib.git/tree/m4/include_next.m4
> If it doesn't work on your system, I would suggest to report it to bug-
> address@hidden, with the logs (including config.log) and the changes you
> made in config.sub.

The situation is that our c99 compiler properly reports that #include_next
is not a known preprocessor directive, but that does not translate into a
non-zero completion code - changing that behaviour is not likely not going
to be a viable option. The test done by configure is insufficient to detect
this. The team is trying to MacGyver a more definitive error detect that
tries to detect the failure to process a header with a definition that will
trigger an actual compiler error. I suspect that this issue may turn out not
to be platform-specific.

-- Brief whoami: NonStop&UNIX developer since approximately
-- In my real life, I talk too much.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]