[PATCH] 'yes' within the path sets wrong config variables
Benjamin Esquivel
benjamin.esquivel@linux.intel.com
Thu Mar 5 18:55:00 GMT 2015
On Wed, 2015-03-04 at 10:04 -0600, Benjamin Esquivel wrote:
> On Wed, 2015-03-04 at 01:00 -0500, Mike Frysinger wrote:
> > On 04 Mar 2015 03:58, Joseph Myers wrote:
> > > On Tue, 3 Mar 2015, Benjamin Esquivel wrote:
> > > > It seems that the 'AC_EGREP_CPP(yes...' example is quite popular
> > > > but being such a short word to grep it is likely to produce
> > > > false-positive matches with the path it is configured into.
> > >
> > > What's your objection to the AC_PREPROC_IFELSE / #error approach suggested
> > > in <https://sourceware.org/ml/libc-alpha/2014-08/msg00414.html>?
> >
>
> I don't have an objection to either approaches. Semantically, it looks
> to me that AC_CHECK_DEFINE is a better option. I'll give it a try.
>
> > that would be an improvement over the status quo, but i think AC_CHECK_DEFINE is
> > even better
>
Now, the thing is that I have been unsuccessful at doing the reconfigure
required to get the 'configure' files out of the modified 'configure.ac'
files.
So far I've tried autoreconf, and make configure at the glibc root dir
and got errors.
Any input on how to reconf is appreciated.
>
> > -mike
>
>
More information about the Libc-alpha
mailing list