From: Peter Seebach <peter.seebach@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] pseudo_1.6.2.bb/pseudo_git.bb: Pseudo 1.6.3
Date: Thu, 22 Jan 2015 16:05:00 -0600 [thread overview]
Message-ID: <20150122160500.68efde12@e6410-2> (raw)
In-Reply-To: <CAJTo0LYPQenCD2eMaSzPbaaUrky_Ta4cpnjFpN55D+BS5YzRJw@mail.gmail.com>
On Thu, 22 Jan 2015 11:26:55 +0000
"Burton, Ross" <ross.burton@intel.com> wrote:
> This fails to build on *some* machines in the AB pool.
>
> http://errors.yoctoproject.org/Errors/Search/Details/7899/1/10/a6ea28e3460217496856d2d79667c4bfbd867df9
> :
>
> DEBUG: Executing shell function do_compile
> NOTE: Building/installing only 64-bit libpseudo.so for nativesdk-pseudo.
> NOTE: If you need to run 32-bit executables, ensure that NO32LIBS is set to
> 0.
> /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-mips/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-pseudo/1.6.3-r0/pseudo-1.6.3/configure:
> line 72: cd: /opt/poky/1.7/sysroots/i686-pokysdk-linux/usr: No such file or
> directory
> ERROR: Prefix is current directory. That doesn't work.
D'oh.
Okay, so what's happening here is, I added a configure test to try to detect
cases where --prefix=foo was the current directory. Which, of course, does
$(cd $prefix; pwd).
And that won't work if the prefix directory doesn't exist at the time of
compilation.
I'll get a fix for that in shortly. Sorry!
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2015-01-22 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 21:21 [PATCH 0/1] pseudo 1.6.3 Peter Seebach
2015-01-20 21:21 ` [PATCH 1/1] pseudo_1.6.2.bb/pseudo_git.bb: Pseudo 1.6.3 Peter Seebach
2015-01-20 21:48 ` Saul Wold
2015-01-20 22:26 ` Peter Seebach
2015-01-22 11:26 ` Burton, Ross
2015-01-22 22:05 ` Peter Seebach [this message]
2015-01-22 23:04 ` Peter Seebach
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=20150122160500.68efde12@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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