From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] pseudo 1.4.2: linkat() and bitrot cleanup
Date: Fri, 14 Dec 2012 20:10:56 -0600 [thread overview]
Message-ID: <cover.1355536994.git.peter.seebach@windriver.com> (raw)
The major change here is the addition of linkat(), and the change of link()
to be written in terms of it (for consistency with othe *at() calls).
I checked this out on Darwin (which hasn't got *at() functions) and picked
off a couple little bits of bitrot.
The other change is that the WR build system turns out to have reasons to,
in some cases, actually use a lib64 directory for things like the host
sqlite3 library. So I cleaned up the computation of the sqlite library
path; of course, this then broke oe-core on 64-bit hosts, but I'd anticipated
that, and pseudo's configure can take an explicit full path to libsqlite3.a
if it's not in a directory with the same name as $(LIB). Did that to the
various 32-bit and 64-bit forms. Note that on 64-bit hosts, this means
that 32-bit libpseudo (if it's being built) is being configured with the
explicit path to our 64-bit libsqlite3.a; that's okay, because we only
build libpseudo for the 32-bit case. Confirmed that, with NO32LIBS = 0,
I get both 32-bit and 64-bit libpseudo.
I did have build failures in perl-native when I was first testing this,
but updating oe-core made them go away, so it was probably just my tree
being pretty old before I started on the pull request.
The tarball is already on yoctoproject.org (thanks, pidge!) and I have
verified that the build still succeeds.
The following changes since commit ad79360c1d992830d4f0e06a3bbf0622658c0540:
Mark Hatle (1):
populate_sdk_base: Add perl modules as needing to be relocated
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo_1_4_2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo_1_4_2
Peter Seebach (1):
pseudo_git.bb and friends: Update to 1.4.2.
meta/recipes-devtools/pseudo/pseudo.inc | 9 +++++----
meta/recipes-devtools/pseudo/pseudo_1.4.1.bb | 8 --------
meta/recipes-devtools/pseudo/pseudo_1.4.2.bb | 8 ++++++++
meta/recipes-devtools/pseudo/pseudo_git.bb | 6 +++---
4 files changed, 16 insertions(+), 15 deletions(-)
delete mode 100644 meta/recipes-devtools/pseudo/pseudo_1.4.1.bb
create mode 100644 meta/recipes-devtools/pseudo/pseudo_1.4.2.bb
next reply other threads:[~2012-12-15 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 2:10 Peter Seebach [this message]
2012-12-15 2:10 ` [PATCH 1/1] pseudo_git.bb and friends: Update to 1.4.2 Peter Seebach
2012-12-24 22:47 ` Saul Wold
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=cover.1355536994.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@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