Re: glibc-2.19-hurd+libpthread-20150515

[Samuel Thibault]

Samuel Thibault, on Sat 31 Oct 2015 11:18:21 +0100, wrote:
> Thomas Schwinge, on Fri 30 Oct 2015 21:55:42 +0100, wrote:
> > In context of preparing a new glibc-hurd+libpthread snapshot,
> > ,
> > is the procedure to merge/cherry-pick the recent patches from
> > libpthread's master branch into its master-glibc branch?
> 
> Yes.
> 
> > Could you please do and test that?
> 
> Right, doing it.

It seems good.

Samuel

Re: glibc-2.19-hurd+libpthread-20150515

[Samuel Thibault]

Thomas Schwinge, on Fri 30 Oct 2015 21:55:42 +0100, wrote:
> In context of preparing a new glibc-hurd+libpthread snapshot,
> ,
> is the procedure to merge/cherry-pick the recent patches from
> libpthread's master branch into its master-glibc branch?

Yes.

> Could you please do and test that?

Right, doing it.

> And/or should we...
> 
> On Fri, 15 May 2015 16:50:29 +0200, Samuel Thibault  
> wrote:
> > Thomas Schwinge, le Fri 15 May 2015 16:46:43 +0200, a écrit :
> > > On Thu, 7 May 2015 01:43:05 +0200, Samuel Thibault 
> > >  wrote:
> > > > I have prepared a master-glibc branch in the libpthread repo.
> > > 
> > > Thanks!  However, shouldn't that just be libpthread's master branch,
> > > nowadays?
> 
> ... pursue this?

I'd say so.

Samuel

Re: glibc-2.19-hurd+libpthread-20150515

[Thomas Schwinge]

Hi!

In context of preparing a new glibc-hurd+libpthread snapshot,
,
is the procedure to merge/cherry-pick the recent patches from
libpthread's master branch into its master-glibc branch?  Could you
please do and test that?

And/or should we...

On Fri, 15 May 2015 16:50:29 +0200, Samuel Thibault  
wrote:
> Thomas Schwinge, le Fri 15 May 2015 16:46:43 +0200, a écrit :
> > On Thu, 7 May 2015 01:43:05 +0200, Samuel Thibault 
> >  wrote:
> > > I have prepared a master-glibc branch in the libpthread repo.
> > 
> > Thanks!  However, shouldn't that just be libpthread's master branch,
> > nowadays?

... pursue this?

> > (Assuming the idea still is that libpthread is only to be
> > built as part of glibc's build process?)
> 
> With that assumption, yes.

Didn't we agree that's the only viable thing to do, or what have I
forgotten?


Grüße
 Thomas


signature.asc
Description: PGP signature

Re: glibc-2.19-hurd+libpthread-20150515

[Ludovic Courtès]

Thomas Schwinge  skribis:

> Snapshot uploaded: <http://alpha.gnu.org/gnu/hurd/>, and corresponding
> Git tags glibc-2.19-hurd+libpthread-20150515 pushed to the Savannah glibc
> and libpthread repositories.

Wonderful!  Manolis should feel relieved now.  ;-)

I thought this was 2.21, but 2.19 should be fine too.

Thank you!

Ludo’.

Re: glibc-2.19-hurd+libpthread-20150515 (was: GSoC: Manolis to work on Guix port to GNU/Hurd)

[Samuel Thibault]

Thomas Schwinge, le Fri 15 May 2015 16:46:43 +0200, a écrit :
> On Thu, 7 May 2015 01:43:05 +0200, Samuel Thibault  
> wrote:
> > Ludovic Courtès, le Wed 29 Apr 2015 21:40:13 +0200, a écrit :
> > > The last missing bit upstream is a libc-for-hurd tarball.
> > 
> > I have prepared a master-glibc branch in the libpthread repo.
> 
> Thanks!  However, shouldn't that just be libpthread's master branch,
> nowadays?  (Assuming the idea still is that libpthread is only to be
> built as part of glibc's build process?)

With that assumption, yes.

> > $ git clone git.savannah.gnu.org:/srv/git/hurd/glibc.git/
> > $ cd glibc
> > $ git checkout tschwinge/Roger_Whittaker
> > $ git clone git.savannah.gnu.org:/srv/git/hurd/libpthread.git/
> > $ cd libpthread
> > $ git checkout master-glibc
> 
> > seems to be going fine.  Thomas, can you have a look at uploading a
> > tarball of this so it can be used as a base for Guix?
> 
> Snapshot uploaded: ,

Thanks!

Samuel

glibc-2.19-hurd+libpthread-20150515 (was: GSoC: Manolis to work on Guix port to GNU/Hurd)

[Thomas Schwinge]

Hi!

On Thu, 7 May 2015 01:43:05 +0200, Samuel Thibault  
wrote:
> Ludovic Courtès, le Wed 29 Apr 2015 21:40:13 +0200, a écrit :
> > The last missing bit upstream is a libc-for-hurd tarball.
> 
> I have prepared a master-glibc branch in the libpthread repo.

Thanks!  However, shouldn't that just be libpthread's master branch,
nowadays?  (Assuming the idea still is that libpthread is only to be
built as part of glibc's build process?)

> $ git clone git.savannah.gnu.org:/srv/git/hurd/glibc.git/
> $ cd glibc
> $ git checkout tschwinge/Roger_Whittaker
> $ git clone git.savannah.gnu.org:/srv/git/hurd/libpthread.git/
> $ cd libpthread
> $ git checkout master-glibc

> seems to be going fine.  Thomas, can you have a look at uploading a
> tarball of this so it can be used as a base for Guix?

Snapshot uploaded: <http://alpha.gnu.org/gnu/hurd/>, and corresponding
Git tags glibc-2.19-hurd+libpthread-20150515 pushed to the Savannah glibc
and libpthread repositories.


Grüße,
 Thomas


signature.asc
Description: PGP signature