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
On Thu, Feb 07, 2002 at 05:53:49PM +0100, Akim Demaille wrote:
>
> | Can anyone explain what this code in autoupdate does? :-
> |
> |
> | my $macros = new Autom4te::XFile ("$autoconf"
> |. " --trace AU_DEFUN:'AU:\$f:\$1'"
> |. " --trace define:'AC:\$f:\$1'"
> |
Tim Van Holder wrote:
>
> 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 \" \
> > >/de
> "Matt" == Matt Schalit <[EMAIL PROTECTED]> writes:
Matt> It's my conclusion that grep -e is the correct syntax.
Matt> Too bad I can't get anyone at libtool to care, but as I mentioned
Matt> I'm not running Linux.
`grep -e' is correct.
Or you can use something like this:
grep '[-]lc'
Hi,
Is there a simple way of determining the version number of the compiler used to
compile an application? I have written a benchmark, which for consistency of
results should ideally always be compiled with the same compiler (gcc) and
version (2.95.3). Is there a way to check this, and if
> From: "Dr. David Kirkby" <[EMAIL PROTECTED]>
> Date: Fri, 08 Feb 2002 19:28:57 +
> Is there a simple way of determining the version number of the
> compiler used to compile an application? I have written a benchmark,
> which for consistency of results should ideally always be compiled
> wit
