Re: Exporting libc patches

Howdy! Thomas Schwinge skribis: > On Sat, 29 Oct 2011 15:39:00 +0200, l...@gnu.org (Ludovic > =?iso-8859-1?Q?Court=E8s?=) wrote: [...] >> Besides, the part of the Savannah patch that touches >> sysdeps/i386/configure fails to apply to Sourceware’s glibc >> (unsurprisingly):

Re: Exporting libc patches

Hi! On Sat, 29 Oct 2011 15:39:00 +0200, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > In related issues, I’m still failing to do this: > > --8<---cut here---start->8--- > $ tg export --linearize for-upstream-glibc > Already up-to-date! > skip empt

Re: Exporting libc patches

Hi Thomas, Thomas Schwinge skribis: > On Thu, 13 Oct 2011 17:16:59 +0200, I wrote: >> On Wed, 23 Mar 2011 14:30:17 +0100, l...@gnu.org (Ludovic >> =?iso-8859-1?Q?Court=E8s?=) wrote: >> > A further complication is that ‘tg remote --populate’ did not fetch the >> > ‘baseline’ branch, which is con

Re: Exporting libc patches

Hi! On Thu, 13 Oct 2011 17:16:59 +0200, I wrote: > On Wed, 23 Mar 2011 14:30:17 +0100, l...@gnu.org (Ludovic > =?iso-8859-1?Q?Court=E8s?=) wrote: > > A further complication is that ‘tg remote --populate’ did not fetch the > > ‘baseline’ branch, which is consequently reported as a missing > > depe

Re: Exporting libc patches

Hi Thomas, Thomas Schwinge skribis: > On Sun, 16 Oct 2011 21:35:29 +0200, l...@gnu.org (Ludovic > =?iso-8859-1?Q?Court=E8s?=) wrote: >> In the meantime I’ve changed the commit SHA1 [0], and it does lead to a > >> [0] >> http://git.savannah.gnu.org/cgit/hydra-recipes.git/commit/?id=7f49a0c373af

Re: Exporting libc patches

Hi! On Sun, 16 Oct 2011 21:35:29 +0200, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > In the meantime I’ve changed the commit SHA1 [0], and it does lead to a > [0] > http://git.savannah.gnu.org/cgit/hydra-recipes.git/commit/?id=7f49a0c373af0e592c8ee4302ddbab6722b20fd4 I still don'

Re: Exporting libc patches

Hi Thomas, Thomas Schwinge skribis: > On Wed, 23 Mar 2011 14:30:17 +0100, l...@gnu.org (Ludovic > =?iso-8859-1?Q?Court=E8s?=) wrote: [...] >> A further complication is that ‘tg remote --populate’ did not fetch the >> ‘baseline’ branch, which is consequently reported as a missing >> dependency

Re: Exporting libc patches

Hi! On Wed, 23 Mar 2011 14:30:17 +0100, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > I’m looking at how to export patches from the > ‘tschwinge/Roger_Whittaker’ branch to continuously test on Hydra whether > they still apply to upstream glibc. > > To that end, the idea I had was to

Re: Exporting libc patches

Hi! On Mon, 06 Jun 2011 14:39:39 +0200, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > l...@gnu.org (Ludovic Courtès) skribas: > > > I’m looking at how to export patches from the > > ‘tschwinge/Roger_Whittaker’ branch to continuously test on Hydra whether > > they still apply to upst

Re: Exporting libc patches

Hi, l...@gnu.org (Ludovic Courtès) skribis: > Samuel Thibault skribis: > >> Ludovic Courtès, le Mon 06 Jun 2011 14:39:39 +0200, a écrit : >>> @@ -79,6 +79,8 @@ >>> extern int __dup (int __fd); >>> extern int __dup2 (int __fd, int __fd2); >>> libc_hidden_proto (__dup2) >>> +extern int __dup3 (

Re: Exporting libc patches

Hello! Samuel Thibault skribis: > Ludovic Courtès, le Mon 06 Jun 2011 14:39:39 +0200, a écrit : >> @@ -79,6 +79,8 @@ >> extern int __dup (int __fd); >> extern int __dup2 (int __fd, int __fd2); >> libc_hidden_proto (__dup2) >> +extern int __dup3 (int __fd, int __fd2, int __flags); >> +libc_hid

Re: Exporting libc patches

Hallo! On Mon, 06 Jun 2011 18:39:09 +0200, l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) wrote: > Samuel Thibault skribis: > > Ludovic Courtès, le Mon 06 Jun 2011 14:39:39 +0200, a écrit : > >> @@ -79,6 +79,8 @@ > >> extern int __dup (int __fd); > >> extern int __dup2 (int __fd, int __fd2)

Re: Exporting libc patches

Samuel Thibault skribis: > Ludovic Courtès, le Mon 06 Jun 2011 14:39:39 +0200, a écrit : >> @@ -79,6 +79,8 @@ >> extern int __dup (int __fd); >> extern int __dup2 (int __fd, int __fd2); >> libc_hidden_proto (__dup2) >> +extern int __dup3 (int __fd, int __fd2, int __flags); >> +libc_hidden_prot

Re: Exporting libc patches

Ludovic Courtès, le Mon 06 Jun 2011 14:39:39 +0200, a écrit : > @@ -79,6 +79,8 @@ > extern int __dup (int __fd); > extern int __dup2 (int __fd, int __fd2); > libc_hidden_proto (__dup2) > +extern int __dup3 (int __fd, int __fd2, int __flags); > +libc_hidden_proto (__dup3) It seems Ulrich added a

Re: Exporting libc patches

Hi! (I hear there’s a deadline approaching, so trying to see how I could do something useful. ;-)) l...@gnu.org (Ludovic Courtès) skribas: > I’m looking at how to export patches from the > ‘tschwinge/Roger_Whittaker’ branch to continuously test on Hydra whether > they still apply to upstream gl

Exporting libc patches

Hello! I’m looking at how to export patches from the ‘tschwinge/Roger_Whittaker’ branch to continuously test on Hydra whether they still apply to upstream glibc. To that end, the idea I had was to do something along these lines: git checkout tschwinge/Roger_Whittaker tg export --linearize