This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Rename unwind.h to unwind-gcc.h


On 04/16/2014 05:56 PM, Ian Lance Taylor wrote:

I'm still not clear on what the real problem is.

It seems to me that when using GCC, if you #include <unwind.h>, you
will get the GCC version, since it will come from the installed
GCC include directory, which is searched ahead of /usr/include.  That
seems OK.

The original e-mail suggested that there was a problem building
libgcc, but I don't see why that would be.  Is that the real problem?
If so we need more details.

The root of the problem is a hack in libgcc/config/t-vxworks put in to resolve a name clash for "regs.h", but this clash was in the other direction, e.g. the vxworks version is needed in preference to the gcc version.

Now with vxworks7, we have a name clash in the other direction and a catch-22 trying to fix it.

I'm working now to try to remove this first hack, then the unwind.h problem should resolve itself.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]