From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] cacaoh: patches to get do_install do its work
Date: Thu, 28 Oct 2010 15:59:44 +0200 [thread overview]
Message-ID: <20101028135944.GL3311@excalibur.local> (raw)
In-Reply-To: <lyy69l5nvj.fsf@ensc-virt.intern.sigma-chemnitz.de>
Hello.
On Tue, 2010-10-26 at 11:01, Enrico Scholz wrote:
> Khem Raj <raj.khem@gmail.com> writes:
>
> >>>>> - install -m 0755 src/cacaoh/.libs/cacaoh ${STAGING_BINDIR}/cacaoh-cldc-${PV}
> >>>>> + install -m 0755 src/cacaoh/cacaoh ${STAGING_BINDIR}/cacaoh-cldc-${PV}
> >>
> >> * libtool creates sometimes a wrapper script for executables (e.g. when
> >> they are linked against local libraries) and places the real executable
> >> in .libs/. Manually installing one of them is error prone and it might
> >> break with other linker flags or libtool versions.
> >
> > the binary in .libs do not exist so the link is final in this case.
>
> Really? The author of the original recipe had an environment where the
> executable was in .libs/. Are you really sure that such an environment
> does not exist anymore? Or will the recipe now silently fail by installing
> the shell wrapper sometimes?
For me it did silently fail. :)
The openjdk-6 build failed due to missing header files like
exceptions.c:44:45: error: native/include/java_lang_String.h: No such file or directory
> > but in any case If you can come up with a patch to install it using
> > libtool that would be nice.
>
> Sorry; providing a patch means testing it (regardless whether it is
> trivial). Here, I am not sure whether 'libtool' or the platform
> prefixed '<arch>-libtool' is required and how to express
> '<arch>-libtool' in oe.
>
> I gave my comment to a patch which fixed a broken recipe by replacing it
> with another broken recipe. So I expect that the author of this patch
> fixes and tests his work.
>
> For completeness; install command should be
>
> | libtool --mode=install install -m 0755 src/cacaoh/cacaoh ${STAGING_BINDIR}/cacaoh-cldc-${PV}
Thanks. I implemented this and the build works fine again. Thanks for letting us
know. Will push it in when I have network connectivity again.
regards
Stefan Schmidt
next prev parent reply other threads:[~2010-10-28 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 8:11 [PATCH] cacaoh: patches to get do_install do its work Jaap de Jong
2010-10-24 13:19 ` Enrico Scholz
2010-10-24 18:36 ` Khem Raj
2010-10-25 10:53 ` Enrico Scholz
2010-10-25 17:49 ` Khem Raj
2010-10-26 9:01 ` Enrico Scholz
2010-10-28 13:59 ` Stefan Schmidt [this message]
2010-10-28 6:24 ` Stefan Schmidt
2010-10-28 6:36 ` Khem Raj
2010-10-28 7:44 ` Stefan Schmidt
2010-10-28 14:02 ` Jaap de Jong
2010-10-28 16:23 ` Stefan Schmidt
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=20101028135944.GL3311@excalibur.local \
--to=stefan@datenfreihafen.org \
--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