From: Marc Olzheim <zlo@zlo.nu>
To: Stanislav Brabec <utx@penguin.cz>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Commit 2e0fa4918d643ce6ec0299cd31cfe1c346e4bce3 breaks libtool's do_configure [PATCH]
Date: Thu, 30 Jul 2009 13:49:22 +0200 [thread overview]
Message-ID: <20090730114922.GA29793@zlo.nu> (raw)
In-Reply-To: <1248952464.21030.110.camel@hammer.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On Thu, Jul 30, 2009 at 01:14:24PM +0200, Stanislav Brabec wrote:
> > I'm not sure how you tested this, but there are quotes missing, so that
> > the "-E" argument to "grep" is passed to "export" instead. I guess some
> > shells have a "-E" flag to "export", so it is silently ignored, but mine
> > don't.
>
> I tried both versions - quoted and unquoted - before the commit. Both
> worked for me, that is why I committed the shorter one.
>
> Well, adding quotes is safe. Can you check your configure output and
> host shell version?
>
> My configure output:
>
> checking for a sed that does not truncate output... (cached) /bin/sed
> checking for grep that handles long lines and -e... (cached) /bin/sed
> checking for egrep... (cached) /bin/grep -E
> checking for fgrep... (cached) /bin/grep -F
>
> It indicates, that it worked correctly.
>
> My native shell is:
>
> /OE/openembedded/build> sh --version
> GNU bash, version 4.0.24(1)-release (x86_64-suse-linux-gnu)
Hmm, what I got was:
(task 365) ERROR: function do_configure failed
(task 365) ERROR: log data follows
(/home/marcolz/src/iphion-new-oe3/embbuild/tmp/work/i686-oe-linux/libtool-cross-2.2.6a-r0/temp/log.do_configure.22690)
| export: 929: -E: bad variable name
(task 365) NOTE: Task failed:
/home/marcolz/src/iphion-new-oe3/embbuild/tmp/work/i686-oe-linux/libtool-cross-2.2.6a-r0/temp/log.do_configure.22690
(task 365) ERROR: TaskFailed event exception, aborting
(task 365) ERROR: Build of
/home/marcolz/src/iphion-new-oe3/embbuild/openembedded.iphion/recipes/libtool/libtool-cross_2.2.6a.bb
do_configure failed
My local bash version is:
GNU bash, version 3.2.39(1)-release (i486-pc-linux-gnu)
Copyright (C) 2007 Free Software Foundation, Inc.
Marc
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
next prev parent reply other threads:[~2009-07-30 12:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:39 How to convert OE hardware platform from ARM into X86 刘芳华
2009-06-04 19:38 ` GNUtoo
2009-06-05 2:12 ` 刘芳华
2009-06-05 12:37 ` GNUtoo
2009-06-05 12:53 ` GNUtoo
2009-06-10 6:48 ` OE Build :error configure failed to discover size of unix socket path 刘芳华
2009-06-10 11:34 ` Lin_Lynn
2009-06-10 12:00 ` Stanislav Brabec
2009-07-30 10:57 ` Commit 2e0fa4918d643ce6ec0299cd31cfe1c346e4bce3 breaks libtool's do_configure [PATCH] Marc Olzheim
2009-07-30 11:14 ` Stanislav Brabec
2009-07-30 11:49 ` Marc Olzheim [this message]
2009-07-30 12:14 ` Stanislav Brabec
2009-07-30 12:50 ` Marc Olzheim
2009-07-30 13:22 ` Leon Woestenberg
2009-07-30 14:48 ` Marc Olzheim
2009-07-30 14:57 ` Philip Balister
2009-07-30 15:12 ` Marc Olzheim
2009-07-30 15:01 ` Graeme Gregory
2009-07-30 16:39 ` Koen Kooi
2009-08-01 5:32 ` Mike Westerhof
2009-08-02 1:32 ` Mike Westerhof
2009-08-02 3:56 ` Mike Westerhof
2009-08-02 9:21 ` Koen Kooi
2009-08-03 8:26 ` Marc Olzheim
2009-08-02 8:49 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090730114922.GA29793@zlo.nu \
--to=zlo@zlo.nu \
--cc=openembedded-devel@lists.openembedded.org \
--cc=utx@penguin.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.