Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: (v3) [PATCH 0/1] pseudo 1.6.*4*
Date: Thu, 22 Jan 2015 20:23:55 -0600	[thread overview]
Message-ID: <cover.1421976243.git.peter.seebach@windriver.com> (raw)

So, pseudo 1.6.3 had a silly configure bug which could prevent it
from configuring under what turn out to be very common circumstances
if you're not me doing internal development, and very rare circumstances
in my normal pseudo development cycle, and I am not quite sure why
it worked at all in my build tests. Basically, "configure ... --prefix="
needed to specify an *existing* directory, or the configure would fail.
This is now fixed.

The other changes appear to have survived, and the one chown problem that
Mark Hatle ran into turns out to have been a task running outside of pseudo,
not a bug in pseudo itself.

Sorry for the mixup with the configure thing. The issue was a naive test:
	if [ "$(cd "$opt_prefix"; pwd)" = "$(pwd)" ]; ...
and this fails if the cd doesn't work because pwd is then just the current
directory.

The reason this test came into existence is that my usual local-dev
habit involves
	configure --prefix=~/pseudo/f
("f" being a historical name), and one time I typoed it and it appeared
to configure and build, but "make install" failed strangely.

And my normal dev cycle does include nuking that directory, but I tend
to first configure, *then* nuke that directory, and that works fine.

This Root Cause Analysis was brought to you by the letters D'OH!

The following changes since commit 0bcc01121e928d0be7a0550e500425852c63cf98:

  arch-mips.inc: Add the MIPS ABIEXTENSION to toolchain name (2015-01-21 14:28:43 +0000)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib seebs/pseudo_164
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo_164

Peter Seebach (1):
  pseudo_1.6.x.bb/pseudo_git.bb: Pseudo 1.6.4

 ...do_client.c-protect-pwd_lck-against-magic.patch |   56 ----------
 ..._util-modify-interface-to-pseudo_etc_file.patch |   70 ------------
 ...nt.c-support-multiple-directories-in-PSEU.patch |  116 --------------------
 .../pseudo/{pseudo_1.6.2.bb => pseudo_1.6.4.bb}    |    7 +-
 meta/recipes-devtools/pseudo/pseudo_git.bb         |    4 +-
 5 files changed, 4 insertions(+), 249 deletions(-)
 delete mode 100644 meta/recipes-devtools/pseudo/pseudo-1.6.2/0001-pseudo_client.c-protect-pwd_lck-against-magic.patch
 delete mode 100644 meta/recipes-devtools/pseudo/pseudo-1.6.2/0002-pseudo_util-modify-interface-to-pseudo_etc_file.patch
 delete mode 100644 meta/recipes-devtools/pseudo/pseudo-1.6.2/0003-pseudo_client.c-support-multiple-directories-in-PSEU.patch
 rename meta/recipes-devtools/pseudo/{pseudo_1.6.2.bb => pseudo_1.6.4.bb} (57%)



             reply	other threads:[~2015-01-23  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  2:23 Peter Seebach [this message]
2015-01-23  2:23 ` [PATCH 1/1] pseudo_1.6.x.bb/pseudo_git.bb: Pseudo 1.6.4 Peter Seebach
2015-01-23 12:10   ` Burton, Ross

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.1421976243.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