Re: Compiling ext2fs.static with pthreads

[Thomas Schwinge]

Hi!

On Tue, 8 May 2012 19:16:09 -0700 (PDT), Thomas Thomas <ricinwich@yahoo.com> 
wrote:
> >On Sun, 6 May 2012 09:25:11 -0700 (PDT), Thomas Thomas <ricinwich@yahoo.com> 
> >wrote:
> >> I played around and got it to compile, though how I did so is a nasty hack.
> 
> >What kind of?
> 
> I caught the output of make to get the full compile command and added
> ../libpthread/cancel-cond.o into it manually, and saved it as a shell script.
> Barry, or someone, rewrote cancel-cond.c from cthreads into a pthreads one.
> I called it nasty because it doesn't fix the makefile, which would be the 
> clean
> solution.

Ah, OK, so that's only an infrastructure issue, which indeed should be
fixed properly at some point.


> So, it runs as a translator. Spews out some unexpected debugging info that 
> Barry
> added, but I can add files, delete files, list directories, etc. I haven't 
> tested it under
> load, however.

Oh great!  I'm not sure if somebody already had gotten that far before
you.  :-)

If you can, please do some more testing.  If you're confident you can
also use it for your main system's rootfs or any other mount points (be
sure to tell strrans to actually use your ext2fs.static instead of the
dynamically linked /hurd/ext2fs).  If your rootfs is bigger than 2 GiB
you'll have to put the ext2fs_large_stores.patch (see »apt-get source
hurd«) on top of your changes.

Summing up, what (additional) changes did you have to do?

Are you willing to transfer the copyright of your changes to the FSF so
that we can incorporate them into our code base?  Is there any employer
that can claim ownership of these changes?


> Thank you for the link on debugging translators. I tried to start a
> sub-hurd using it

How do you start the sub-hurd, and what system image are you using for
it?

> but for some reason it gets to somewhere in libc while trying to
> create its first thread and derefs a null pointer. I don't have complete 
> debugging info
> for where it falls apart. Here's the backtrace:

Hmm, difficult to tell from that alone.  


Grüße,
 Thomas

pgpsGwMy_eKo5.pgp
Description: PGP signature