From: Holger Hans Peter Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Upgrade glibc from 2.6.1 to 2.10.1, the 2.6.1 glibc cause ltrace compilation failed
Date: Fri, 25 Dec 2009 05:46:52 +0100 [thread overview]
Message-ID: <200912250546.52376.holger+oe@freyther.de> (raw)
In-Reply-To: <1261712573-10282-1-git-send-email-camelguo@gmail.com>
On Friday 25 December 2009 04:42:53 Guo Hongruan wrote:
> the include/sys/ptrace.h of glibc 2.6.1 does not include the PTRACE_EVENT*
> macroes, which is needed by ltrace. the one of glibc 2.10.1 does include
> them and on it the compilation of ltrace succeed ---
That is quite a bad reason to upgrade the default. The problem is you would
have to convince us that glibc 2.10.1 is working just fine for arm, armeb,
mips, mipsel, powerpc, avr, sparc, i486, i586... Or at least your commit
message should include the information that you have tested builds with it.
Then again. It is pretty common that older versions of a library do not have
newere definitions of syscalls and syscall parameters (e.g. most notable this
happened with the addition of inotify and early adaption of it). The fix is the
one you proposed. Check if the system has the definition, if not define it
locally.
regards
holger
next prev parent reply other threads:[~2009-12-25 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 3:42 [PATCH] Upgrade glibc from 2.6.1 to 2.10.1, the 2.6.1 glibc cause ltrace compilation failed Guo Hongruan
2009-12-25 4:46 ` Holger Hans Peter Freyther [this message]
2009-12-25 6:16 ` Guo Hongruan
2009-12-25 10:54 ` Holger Hans Peter Freyther
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=200912250546.52376.holger+oe@freyther.de \
--to=holger+oe@freyther.de \
--cc=openembedded-devel@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 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.