[Top][All Lists]

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

Re: Problems with old GCC and #include_next

From: Reuben Thomas
Subject: Re: Problems with old GCC and #include_next
Date: Sun, 21 Sep 2008 13:14:36 +0100 (BST)
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)

On Sat, 20 Sep 2008, Eric Blake wrote:

According to Reuben Thomas on 9/20/2008 4:22 PM:
gnulib checks that the compiler supports #include_next before actually
stuffing #include_next into the generated .h files.

I think I might be confused here. I am running gnulib on my computer,
and distributing the files it builds. Should I not be doing this?

When both a .in.h and .h file exist, only distribute the .in.h file (the
gnulib automake snippets already do this for you, with no extra effort
needed on your part).

Indeed, and since I'm not making any extra effort, I'm assuming it's doing the right thing.

I've checked the source tarball from which I was building, and there's no #include_next in any .h file. That suggests something is going wrong with the configuration check, or somehow two different cpps are getting involved. Checking...

http://rrt.sc3d.org/ | secret, n.  what all know but none speaks

reply via email to

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