The Arch Hurd Project

Giselher · 2010-02-27 12:18:53

Allan wrote:

Did you get anything of interest in the build output? I seem to remember battling that in the past but I thought I had gotten around that issue with some patching to glibc...

Now i compiling gcc again with different prefixes.

melpo · 2010-02-27 12:23:41

If i remember correctly this means that at least some parts of target-libgcc are not building for you.
Maybe you could post the output from 'make all-target-libgcc' in your gcc-build directory

Allan · 2010-02-27 12:25:59

I meant the build output from when you are building gcc, but anyway...

Following all those ../../..'s, it is looking for the i586-pc-gnu directory in /. Is that file anywhere on your system. Try locating the file and adding a symlink.

bobdob · 2010-02-27 13:35:56

Allan, is this how far CHFS booted for you, or did it get further?

Allan · 2010-02-27 13:39:02

That is exactly what I ended up with. I could not get any further with that approach. However, I still believe it is the better approach...

Note that it is not an issue with ext2fs.static, because transferring it to the Debian image got a nice booting system.

bobdob · 2010-02-27 13:43:23

Good to know its not just my problem. I also updated the CHFS scripts so it is mostly automatic now, except for root prompts for the symlinks at the start.

Allan · 2010-02-27 13:46:59

If you want me to host updated versions, send me a tarball by email and I will put them on my site.

bobdob · 2010-02-27 13:53:01

I will see if I can get it working today, else I'll send it to you tonite/tomorrow.

Giselher · 2010-02-27 14:57:24

Allan wrote:

I meant the build output from when you are building gcc, but anyway...
Following all those ../../..'s, it is looking for the i586-pc-gnu directory in /. Is that file anywhere on your system. Try locating the file and adding a symlink.

It seems i installed the files in cross/ so i copied.

My screenshot shows that init comes after exec. Maybe there is something wrong with the init files. libexec/rc and libexec/runsystem

EDIT:
Wohoo My first C App in Hurd.

EDIT2:
make works too, but make is very slow. It takes en eternity to build ncurses within hurd.

Last edited by Giselher (2010-02-27 16:18:38)

Calimero · 2010-03-01 21:34:34

Great project, I'm compiling along with you and hope for a pkg repo soon.

Allan, I think you forgot to change SRCDIR to SOURCE_DIR in scripts/get-sources ?
All sources ended in ~ (i686 chroot, so nevermind)

delcake · 2010-03-02 00:34:23

Sweet! This project has definitely piqued my interest if only for the "I can officially say I've done it" factor. I'll have to see if I can get this put together for me sometime, especially if more progress is made. I wish I had the experience to help contribute, but this is a little bit deeper than my experience for me to just dive in.

Allan · 2010-03-02 01:11:03

bobdob wrote:

I will see if I can get it working today, else I'll send it to you tonite/tomorrow.

Bobdob's CHFS update posted: http://allanmcrae.com/hurd/bobdob/chfs- … -01.tar.gz

Note: CHFS approach that should be easier to get gcc working but does not boot...

Giselher · 2010-03-02 18:07:58

Yes. I doesn't boot with the chfs approach.

Fist I had to remove the a line form my menu.lst.

module /lib/ld.so.1 /hurd/exec $(exec-task=task-create)

Because it didn't found the file: /lib/ld.so.1

Image: http://yfrog.com/enhurd1p

Next i got an kernel panic about an ERROR in executing boot script.
Image: http://yfrog.com/4bhurd2p

Copying ld-2.10.1.so form my booting hurd to chfs/lib/ld.so.1 works. (Bug Report)

But then i get the same message and it hangs trying to load /hurd/exec.

Last edited by Giselher (2010-03-02 20:56:51)

melpo · 2010-03-06 18:05:07

Hey

The approach from the last non CHFS pacakge(crosshurd20100224) works fine for me. I built a working system with gcc using it and I am currently using it to natively compile libarchive in qemu.
I encountered a problem with the fix you use for the gcc include dir issue:

sed -e 's@\(^NATIVE_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g' \
    gcc/Makefile.in.orig > gcc/Makefile.in

does not fix the problem for me, I still have to set it while doing make. I did of course change /tools/include to the dir I use.

libarchive requires some patching due to it using PATH_MAX, I will post my patch once I get the chance to test it.

Last edited by melpo (2010-03-06 18:28:04)

Allan · 2010-03-06 21:42:13

@melpo: My offer to host tarballs of scripts for this, so email me an updated tarball if you want.

Allan · 2010-03-07 11:27:37

And you can find melpo's progress here:
http://allanmcrae.com/hurd/melpo/crossh … 07.tar.bz2

Allan · 2010-03-07 11:29:28

melpo wrote:

libarchive requires some patching due to it using PATH_MAX, I will post my patch once I get the chance to test it.

You can be lazy... instead of properly fixing this to dynamically allocate the file names, just add

#define PATH_MAX 4000

That is the way "file" handles this. Debian patch in a PATH_MAX definition to their gcc.

melpo · 2010-03-07 13:23:13

Allan wrote:

You can be lazy... instead of properly fixing this to dynamically allocate the file names, just add
....
Debian patch in a PATH_MAX definition to their gcc.

Yeah I saw that patch, I really don't like that solution though. I believe that if we are to make a hurd distribution we should try to stick to hurd's ideas and not ignore them out of convenience.
That said, really porting every package is a lot of work and more importantly all the dynamic allocating will surely result in a lot of segfaulting.
In my opinion this is a very important topic to discuss and we should agree on a unified way of doing this soon. Please share your thoughts on this.

For now I will at least temporarily use PATH_MAX defines for the important parts of the system to get things going. I don't really think of this as a good long-term solution though.

Allan · 2010-03-07 13:28:55

I agree that it is not an ideal way to fix things. But once you have a working "base" image or installer, then you have the foundation to be idealistic about fixing issues with packages.

melpo · 2010-03-08 13:02:35

So...
I made some nice progress this weekend and got pacman/makepkg working and I have not yet experienced any problems with them in my tests. makepkg has to be run as root though because fakeroot has some big issues on hurd which probably won't be easy to fix.
After I clean things up and test the whole script I will be happy to share it.
Now for building the packages I would prefer to not build them in qemu because it takes ages (~30mins for a simple configure ) so I would at least like to be able to build the majority of packages on my normal system.
I am not really an expert on makepkg so I have to ask if there's any reason why cross-compiling in combination with makepkg is a bad idea.

Giselher · 2010-03-08 14:48:26

melpo wrote:

So...
I made some nice progress this weekend and got pacman/makepkg working and I have not yet experienced any problems with them in my tests. makepkg has to be run as root though because fakeroot has some big issues on hurd which probably won't be easy to fix.
After I clean things up and test the whole script I will be happy to share it.
Now for building the packages I would prefer to not build them in qemu because it takes ages (~30mins for a simple configure ) so I would at least like to be able to build the majority of packages on my normal system.
I am not really an expert on makepkg so I have to ask if there's any reason why cross-compiling in combination with makepkg is a bad idea.
(image)

I also experienced that building something in hurd takes some time. Is there something we can do to speed up hurd? .I don't have the newest scritpts, because my hurd works so well and i don't have much time at the moment.

PS: Thumps up, for the first person using pacman in hurd.

Last edited by Giselher (2010-03-08 14:49:47)

Allan · 2010-03-08 18:48:07

fakeroot should be built with "--with-ipc=tcp" rather than sysv on hurd. It still has issues but should work somewhat... Edit: I would use separate build() and package() steps in the PKGBUILD to avoid fakeroot usage during building.

Are you running qemu with KVM?

Edit: You can always try converting an image to use in VirtualBox or VMWare

Giselher · 2010-03-08 21:23:43

For a second i thought it would work with the first try. Well, Ii get some very strange errors booting hurd in VBox.

+ Creating a new drive and copying the files doesn't work
+ Converting form img to vdi doesn't work

I think i will use qemu a little longer.

Allan · 2010-03-08 21:27:27

OK... then KVM may be the way to go. That gave me a good speed boost for a linux vm last time I tried it. But it will probably break Hurd.... it seems everything does!

Giselher · 2010-03-08 21:39:27

Allan wrote:

OK... then KVM may be the way to go. That gave me a good speed boost for a linux vm last time I tried it. But it will probably break Hurd.... it seems everything does!

Qemu says that i don't have the device /dev/kvm. However it is a bit faster.

EDIT:
I am in the group kvm
and did "modprobe kvm"

Last edited by Giselher (2010-03-08 21:47:46)

Arch Linux

#276 2010-02-27 12:18:53

Re: The Arch Hurd Project

#277 2010-02-27 12:23:41

Re: The Arch Hurd Project

#278 2010-02-27 12:25:59

Re: The Arch Hurd Project

#279 2010-02-27 13:35:56

Re: The Arch Hurd Project

#280 2010-02-27 13:39:02

Re: The Arch Hurd Project

#281 2010-02-27 13:43:23

Re: The Arch Hurd Project

#282 2010-02-27 13:46:59

Re: The Arch Hurd Project

#283 2010-02-27 13:53:01

Re: The Arch Hurd Project

#284 2010-02-27 14:57:24

Re: The Arch Hurd Project

#285 2010-03-01 21:34:34

Re: The Arch Hurd Project

#286 2010-03-02 00:34:23

Re: The Arch Hurd Project

#287 2010-03-02 01:11:03

Re: The Arch Hurd Project

#288 2010-03-02 18:07:58

Re: The Arch Hurd Project

#289 2010-03-06 18:05:07

Re: The Arch Hurd Project

#290 2010-03-06 21:42:13

Re: The Arch Hurd Project

#291 2010-03-07 11:27:37

Re: The Arch Hurd Project

#292 2010-03-07 11:29:28

Re: The Arch Hurd Project

#293 2010-03-07 13:23:13

Re: The Arch Hurd Project

#294 2010-03-07 13:28:55

Re: The Arch Hurd Project

#295 2010-03-08 13:02:35

Re: The Arch Hurd Project

#296 2010-03-08 14:48:26

Re: The Arch Hurd Project

#297 2010-03-08 18:48:07

Re: The Arch Hurd Project

#298 2010-03-08 21:23:43

Re: The Arch Hurd Project

#299 2010-03-08 21:27:27

Re: The Arch Hurd Project

#300 2010-03-08 21:39:27

Re: The Arch Hurd Project

Board footer