Allan McRae, le Mon 11 Jan 2010 10:55:56 +1000, a écrit :
> As Lenny was released about the same time that patch
> hit cvs/git, I am guessing that a patch was never needed for this
> particular issue.
Yes it was: unstable saw an upgrade to 2.9 first, and then to 2.10
Samuel
Samuel Thibault wrote:
Allan McRae, le Mon 11 Jan 2010 09:15:51 +1000, a écrit :
Samuel Thibault wrote:
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
Is there another patch for glibc-2.7 to fix this or, even better, a
patch-set for a newer glibc version?
You can peek debian's patc
Allan McRae, le Mon 11 Jan 2010 09:15:51 +1000, a écrit :
> Samuel Thibault wrote:
> >Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
> >> Is there another patch for glibc-2.7 to fix this or, even better, a
> >>patch-set for a newer glibc version?
> >
> >You can peek debian's patchset.
>
Samuel Thibault wrote:
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
Is there another patch for glibc-2.7 to fix this or, even better, a
patch-set for a newer glibc version?
You can peek debian's patchset.
Thanks. I guess this is an answer for the latter part of that question,
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
> Is there another patch for glibc-2.7 to fix this or, even better, a
> patch-set for a newer glibc version?
You can peek debian's patchset.
Samuel
Hi,
I am trying to cross-compile a GNU system and have run into an "issue"
compiling Hurd. Currently, I am cross-compiling with binutils-2.19.1,
gcc-4.1.2 and glibc-2.7 using the patches from here:
http://www.schwinge.homeip.net/~thomas/tmp/glibc-patches/ (all 00xx-
patches, cvs-MSG_NOSIGNA
