On Wed, 2012-06-06 at 15:43 -0400, Jeremy Huntwork wrote:
> On 6/6/12 3:24 PM, Matt Burgess wrote:
> > Surely if we can't find/link against host libs at this point, that flag
> > is at best superfluous and at worst a potential danger as it may mask us
> > being able to link against host libs when w
On 6/6/12 3:24 PM, Matt Burgess wrote:
> Surely if we can't find/link against host libs at this point, that flag
> is at best superfluous and at worst a potential danger as it may mask us
> being able to link against host libs when we shouldn't be able to?
Yep - agreed on all points. Superfluous.
On Wed, 2012-06-06 at 14:57 -0400, Jeremy Huntwork wrote:
> If the user has been following the instructions correctly, it will be
> impossible to link against host libs at this point.
So, why then do you think
> We have the switch --disable-perl-regexp which is fine
Surely if we can't find/l
We have the switch --disable-perl-regexp which is fine, but the
explanation is no longer correct. It says:
This ensures that the grep program does not get linked against a Perl
Compatible Regular Expression (PCRE) library that may be present on the
host but will not be available once we enter t
