All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCH 1/2] attr/acl: add SSTATEPOSTINSTFUNC
Date: Wed, 05 Oct 2011 10:45:59 -0700	[thread overview]
Message-ID: <4E8C97D7.8020909@intel.com> (raw)
In-Reply-To: <1317742614.13337.47.camel@phil-desktop>

On 10/04/2011 08:36 AM, Phil Blundell wrote:
> On Sat, 2011-09-24 at 11:56 -0700, Saul Wold wrote:
>> +fix_symlink () {
>> +	# Remove bad symlinks&  create the correct symlinks
>> +	if test -L ${libdir}/lib${BPN}.so ; then
>> +		rm -rf ${libdir}/lib${BPN}.so
>> +		ln -sf ${base_libdir}/lib${BPN}.so ${libdir}/lib${BPN}.so
>> +	fi
>
> This breaks the build for me on micro.  I end up with a symlink pointing
> to itself:
>
> lrwxrwxrwx 1 pb pb 76 2011-10-04
> 16:09 /home/pb/oe/build-epia/build/tmp-eglibc/sysroots/x86_64-linux/lib/libattr.so ->  /home/pb/oe/build-epia/build/tmp-eglibc/sysroots/x86_64-linux/lib/libattr.so
>
> with predictably bad results.
>
Not good, I guess the change here would be to test if base_libdir and 
libdir are the same, would you confirm that this test would be right?

Thanks
	Sau!

> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




  reply	other threads:[~2011-10-05 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24 18:56 [PATCH 0/2] v2 of attr/acl with qemuimage-testlib fix Saul Wold
2011-09-24 18:56 ` [PATCH 1/2] attr/acl: add SSTATEPOSTINSTFUNC Saul Wold
2011-10-04 15:36   ` Phil Blundell
2011-10-05 17:45     ` Saul Wold [this message]
2011-10-05 18:32       ` Phil Blundell
2011-09-24 18:56 ` [PATCH 2/2] qemuimage-testlib: set a default geometry for xterm Saul Wold
2011-09-25 14:29 ` [PATCH 0/2] v2 of attr/acl with qemuimage-testlib fix Richard Purdie
2011-09-25 17:07   ` Richard Purdie

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=4E8C97D7.8020909@intel.com \
    --to=saul.wold@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.