All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: pseudo issue on CentOS5
Date: Tue, 19 Jul 2011 10:06:46 -0700	[thread overview]
Message-ID: <1311095211.2115.6.camel@scimitar> (raw)
In-Reply-To: <CAEsOVNdmyZSK2rv2+2zAQXpf8Txz_3=v62NZ85pO-D7esChwCQ@mail.gmail.com>

On Fri, 2011-07-15 at 21:23 +0000, McClintock Matthew-B29882 wrote:
> This bug: http://bugzilla.yoctoproject.org/show_bug.cgi?id=1177 only
> occurs on my CentOS 5 boxes (not on my Fedora 13 box). I have
> determined that this git patch
> 4b66ce472871618cfe4761861392b7f9c3c265b0 is causing the problem.
> Reverting the patch fixes this.
> 
> Still looking at this more but I thought I would share this with
> everyone and see if anyone has a more specific reason why this is
> happening.

I filed bug #1251[1] based on our conversation on IRC and a brief follow
on with Mark, who does some pseudo work.

Mark indicated that we'll need to check glibc on the CentOS machine and
find the symbol and versions for all of the realpath functions.

I need to set up a CentOS VM before I can get around to this but if you
get opportunity you could do so and update the bug?

You can use 'objdump -T' for this, i.e. (from my F15 box):
joshual@scimitar:~
$ objdump -T /lib/libc.so.6 | grep realpath
416c3f00 g    DF .text	00000041 (GLIBC_2.0)  realpath
415e60e0 g    DF .text	00000478  GLIBC_2.3   realpath
4169a330 g    DF .text	00000037  GLIBC_2.4   __realpath_chk

Thanks,
Joshua

1. http://bugzilla.yoctoproject.org/show_bug.cgi?id=1251
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre



  reply	other threads:[~2011-07-19 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 21:23 pseudo issue on CentOS5 McClintock Matthew-B29882
2011-07-19 17:06 ` Joshua Lock [this message]
2011-07-19 17:46   ` McClintock Matthew-B29882

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=1311095211.2115.6.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=yocto@yoctoproject.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.