autoconf
[Top][All Lists]
Advanced

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

Re: Difficulty with configure in libtool-1.4.2


From: Tim Van Holder
Subject: Re: Difficulty with configure in libtool-1.4.2
Date: 08 Feb 2002 13:06:06 +0100

On Fri, 2002-02-08 at 08:51, Matt Schalit wrote:
> 
> I'm not experienced with enough platforms to tell why
> line 5148 in libtool-1.4.2 configure doesn't call grep -e:
> 
>       if { (eval echo configure:5149: \"$archive_cmds 2\>\&1 \| grep \" -lc 
> \" \
> >/dev/null 2\>\&1\") 1>&5; (eval $archive_cmds 2\>\&1 \| grep \" -lc \" 
> >\>/dev/n
> ull 2\>\&1) 2>&5; }
> 
> 
> 
> Doesn't grep -e exist on your computers?  On my unix box,
> which is UnixWare 7.1.1, grep -e is required to protect grep 
> from interpreting the -lc as another switch.  (grep returns 
> a 2 for syntax error every time with this configure line)

I'll leave that for someone else to answer; I'm guessing its some
sort of portability issue.

> Please advise.  I can't get any response from the bug-libtool
> list so far, and I'm not sure the best way to fix all six configures
> that are in that distro.  Thanks.
> Matthew

The proper place will likely be libtool.m4 (provided the problem is in
a libtool-related configure test); any changes to that file will
propagate to all configure scripts after running the bootstrap script
in the top of the libtool tree.





reply via email to

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