From: Mike Crowe <mac@mcrowe.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: mac@mcrowe.com, openembedded-core@lists.openembedded.org
Subject: Re: libtool-cross patch thread : follow up on do_install...
Date: Mon, 26 Mar 2012 11:48:26 +0100 [thread overview]
Message-ID: <20120326104826.GA28912@mcrowe.com> (raw)
In-Reply-To: <CAMKF1sqwv=WyUAKzoSc3mGJFzWQvPG3ax=eatLAqT2dfjan6XA@mail.gmail.com>
On Sun, Mar 25, 2012 at 10:07:17AM -0700, Khem Raj wrote:
> On Sun, Mar 25, 2012 at 8:51 AM, Mike Williamson
> <michael.williamson@criticallink.com> wrote:
> > Hi,
> >
> > I was investigating a build issue using a local recipe inheriting autotools
> > employing libtool (a compile of unixodbc, needed by the new php recipe)
> > and ran into an issue that appears to be solved by modifying the
> > do_install() method of libtool-cross according to comments made
> > in this patch thread:
> >
> > http://patches.openembedded.org/patch/15065/
> >
> > Basically, replace the do_install with "oe_runmake DESTDIR=${D} install"
> > suggested by Khem Raj. Mike Crowe seemed to think that it cleaned
> > up issues he was having, but the thread seems to die at that point.
> >
> > The current recipe for libtool-cross does not reflect the modification
> > mentioned, so I am wondering if this is not appropriate?
> > Am I doing more harm than good?
>
> Mike Crowe did not report back so if he saw no issues we should have this patch
> in with required alteration.
I did have some success but I ended up with various other problems
that I never got to the bottom of. I kept hoping I'd be able to
investigate further and solve the remaining problems but that has
turned out not to be the case. :(
I did find that I had to add back the parts from Richard's original
patch that installed stuff in ${bindir_crossscripts}.
But after that it seems that my variables are a mixture of full paths
and relative paths which causes problems when I run make install
whether I use ${MAKE} or oe_runmake and whether I specify DESTDIR or
not.
For example, during do_configure_prepend I have the following:
STAGING_DATADIR=/home/mac/src/oe/build/tmp-eglibc/sysroots/panther/home/mac/src/oe/build/tmp-eglibc/sysroots/panther/usr/share
STAGING_DIR=/home/mac/src/oe/build/tmp-eglibc/sysroots
datadir=/home/mac/src/oe/build/tmp-eglibc/sysroots/panther/usr/share
target_datadir=/usr/share
libdir=/lib
datadir makes its way into libtool's Makefile so I end up
with the /home/mac/... directories in my image. :(
I tried various things to fix the problem (mainly not making datadir
absolute) but I never got anything that completely worked from
clean. I think some of the remaining problems were due to me using
meta-micro's no /usr though.
I hope this is useful and I'm sorry it's not more so.
Thanks.
Mike.
prev parent reply other threads:[~2012-03-26 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 15:51 libtool-cross patch thread : follow up on do_install Mike Williamson
2012-03-25 17:07 ` Khem Raj
2012-03-26 10:48 ` Mike Crowe [this message]
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=20120326104826.GA28912@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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