From: Chris Conroy <Chris.Conroy@hillcrestlabs.com>
To: OE-Dev <openembedded-devel@lists.openembedded.org>
Subject: libtool failing to define echo?
Date: Wed, 09 Dec 2009 19:04:52 -0500 [thread overview]
Message-ID: <1260403492.2106.17.camel@conroy-linux> (raw)
I've got an issue building cairomm-1.8.2 (which is newer than the latest
version in OE proper).
Basically libtool is not defining $echo and this is causing compile
errors. I can work around the issue by inserting an echo=echo before the
failure, but this seems like either a cairomm bug or a libtool bug. I'm
just not sure how to go about properly patching it since I don't fully
'get' libtool. If anyone can offer some insight as to the proper fix, it
would be greatly appreciated.
I'm using libtool 1.5.24 at the moment. I seem to recall running into
issues with a newer version, but if the correct thing to do is to
upgrade libtool, let me know.
> # Darwin sucks
> eval std_shrext=\"$shrext_cmds\"
Here is my bogus workaround define
> echo=echo
>
> disable_libs=no
>
> # Parse our command line options once, thoroughly.
> while test "$#" -gt 0
> do
> arg="$1"
> shift
>
> case $arg in
And here is where it fails without the bogus workaround
> -*=*) optarg=`$echo "X$arg" | $Xsed -e 's/[-_a-zA-Z0-9]*=//'` ;;
> *) optarg= ;;
> esac
reply other threads:[~2009-12-10 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1260403492.2106.17.camel@conroy-linux \
--to=chris.conroy@hillcrestlabs.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox