[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
#define warnings when using various autotools projects
From: |
aaragon |
Subject: |
#define warnings when using various autotools projects |
Date: |
Mon, 12 May 2008 17:07:02 -0700 (PDT) |
Hi everyone,
A project of mine uses two autotools projects, each of which creates a
config.h file where there are a bunch of #define statements. Well, when I
compile I see several warning messages telling me that some of those
variables are re-defined. What is the cleanest way to fix this? I could just
rename those #define statements to something else in any of the config.h
files but I don't think that is the way to do this. Besides, those files are
generated from a config.h.in that had been generated by autoheader.
Any suggestions? Thank you all,
aa
--
View this message in context:
http://www.nabble.com/-define-warnings-when-using-various-autotools-projects-tp17198634p17198634.html
Sent from the Gnu - Autoconf - General mailing list archive at Nabble.com.
- #define warnings when using various autotools projects,
aaragon <=
- Re: #define warnings when using various autotools projects, John Calcote, 2008/05/13
- Re: #define warnings when using various autotools projects, Bob Friesenhahn, 2008/05/13
- Re: #define warnings when using various autotools projects, Bruce Korb, 2008/05/13
- Re: #define warnings when using various autotools projects, Ed Hartnett, 2008/05/13
- Re: #define warnings when using various autotools projects, Ralf Wildenhues, 2008/05/18
- Re: #define warnings when using various autotools projects, aaragon, 2008/05/18