You are not logged in.
xz-utils:
...
patch -p1 < $SOURCE_DIR/patches/xz-$XZUTILS_VER/crc32.patch patch -p1 < $SOURCE_DIR/patches/xz-$XZUTILS_VER/crc64.patch
...
Out of interest, where did you find those patches?
Offline
Out of interest, where did you find those patches?
I found an outdated patch for an older version of xz-utils that didn't work on google and, after a bit more googling found out what exactly the problem was (OS X uses the symbol __MACH__ to indicate it uses the Mach-O binary format, and Hurd uses it to indicate it uses the Mach kernel, or something). So I looked through the breaking files and fixed it myself.
Offline
Cool. That explains why I could not find them!
Edit: I changed them for this line as they did not apply for me:
sed -i "s#__MACH__#__OSX__#" xz-$XZUTILS_VER/src/liblzma/check/crc{32,64}_x86.S
Offline
Edit: I changed them for this line as they did not apply for me:
sed -i "s#__MACH__#__OSX__#" xz-$XZUTILS_VER/src/liblzma/check/crc{32,64}_x86.S
Well, my hard work patching was all for naught. sed didn't even occur to me
Offline
Allan wrote:Edit: I changed them for this line as they did not apply for me:
sed -i "s#__MACH__#__OSX__#" xz-$XZUTILS_VER/src/liblzma/check/crc{32,64}_x86.S
Well, my hard work patching was all for naught. sed didn't even occur to me
Haha Well, you pick these things up when you spend too much time on packaging....
I thought it about time to make another tarball:
http://allanmcrae.com/hurd/crosshurd-20100121.tar.gz
New cross compiles: bzip, binutils, fakeroot, gawk, gzip, mpfr, xz-utils, zlib (mostly from Barrucadu)
I left gdbm and db in the "source/devel" folder as I have not actually tested them yet.
Binutils is there, but until I get gcc going I can not test it that easily. It installs some files in funny places but we can fix that building natively. ppl and cloog-ppl should be easy to build and I will tackle gcc and try getting a natively compiling "hello world". I doubt that will occur before Sunday. Once that is done, I will focus on openssl and wget if no-one has beaten me to it...
I'd guess findutils, util-linux-ng, gettext should be fairly easy to package. Try without acl/attr dep for gettext. libarchive and libfetch are BSD projects and compiled readily for linux so I guess they will be nicely portable to hurd too.
Offline
Allan, I found some spare time to try Hurd again, but the tarball won't be downloaded, have you relocated it ?
I thought it about time to make another tarball:
http://allanmcrae.com/hurd/crosshurd-20100121.tar.gz
Last edited by flamelab (2010-01-20 17:31:24)
Offline
It's OK here .
/me wants you to detele this account... please delete it.
Offline
With the newest tarball i get the following error right after cross-binutils-build:
make[1]: Leaving directory `/home/regj/hurd/build/cross-binutils-build'
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|ChangeLog:
|2010-01-06 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
|
| PR bootstrap/41818
| * Makefile.tpl (BASE_TARGET_EXPORTS): Only add TARGET_LIB_PATH
| to $(RPATH_ENVVAR) if bootstrapping.
| * Makefile.in: Regenerate.
|
|diff --git a/Makefile.in b/Makefile.in
|index e5fa1d3..dbfc1f0 100644
|--- a/Makefile.in
|+++ b/Makefile.in
--------------------------
File to patch:
Which bzip2 file is it complaining about?
Offline
One of your gcc sources is not downloaded properly.
Offline
Allan, I found some spare time to try Hurd again, but the tarball won't be downloaded, have you relocated it ?
I thought it about time to make another tarball:
http://allanmcrae.com/hurd/crosshurd-20100121.tar.gz
No. That link works for me...
Offline
Can you post please a link to a page (or if you want, write it here) describing the actual advantages of the hurd kernel over the linux/bsd/nt kernels?
Everything I found wasn't clear enough or from the developer point of view like here: http://www.gnu.org/software/hurd/hurd/advantages.html
What would a user benefit from it when it would be mature and compatible enough?
Thanks.
Offline
Can you post please a link to a page (or if you want, write it here) describing the actual advantages of the hurd kernel over the linux/bsd/nt kernels
It pretty much comes down to the design. Some people think a micro kernel design is better and some prefer a monolithic kernel design. Both designs have their pros and cons. It is hard to find a page which makes a fair comparison of Hurd and Linux, I think a better approach is to understand the concept of both micro kernels and monolithic kernels.
In case you don't know, Hurd is a micro kernel design and Linux/BSD is a monolithic kernel design.
Offline
I believe this is one major benefit of a micro kernel (from SoleSoul's posted link)
It is possible to develop and test new Hurd kernel components without rebooting the machine (not even accidentally). Running your own kernel components doesn't interfere with other users, and so no special system privileges are required. The mechanism for kernel extensions is secure by design: it is impossible to impose your changes upon other users unless they authorize them or you are the system administrator.
Another thing I noticed from reading around on the site, http://www.gnu.org/software/hurd/hurd/faq.html , there seems to be some things you could do without needing root privileges in a micro kernel, unlike linux. I wonder if that would apply to Xorg also. They did state that X is very unusable in Hurd anyway. Maybe a modification is needed?
...I'm just rambling.
Last edited by sand_man (2010-01-21 06:57:18)
Offline
Can you post please a link to a page (or if you want, write it here) describing the actual advantages of the hurd kernel over the linux/bsd/nt kernels?
Everything I found wasn't clear enough or from the developer point of view like here: http://www.gnu.org/software/hurd/hurd/advantages.html
What would a user benefit from it when it would be mature and compatible enough?
you can try
http://www.informit.com/articles/printe … ?p=1180992
which, while still having much from the developer POV, describes some user benefits of a would be 'mature' hurd system.
Offline
Allan, I've been busy over the past few days with exams. How's GCC/pacman going?
Offline
Not a lot of progress in the last few days. I have been busy with work and Arch Linux...
Offline
Ok. Well, I should be able to start doing things again by the weekend.
Offline
*prod*
I'm having difficulty with `ppl`, people! Anybody want to give it a go?
I'm currently rebuilding my cross-toolchain, I'll post the error message later. IIRC it's something about libgmpxx.
Offline
You do not actually need ppl and cloog-ppl for gcc. They are optional. I ran into issues there so I skipped them. Still can not get gcc to compile either...
Offline
Offline
I think I have figured the gcc issues. It turns out cross compiling the gcc c++ compiler is crap for gcc-4.4. And we need g++ support for gmp. I think downgrading to 4.3.x should help.
I have also started reworking the build scripts a fair bit to more closely follow CLFS as the toolchain really needed more care taken to ensure it will work correctly.
Offline
Hmm... gcc-4.3 requires a bit of patching... building now so we will see how that went!
Offline
GOOD NEWS EVERYONE!
I have managed to get the toolchain completely cross compiled. That means we can start natively compiling soon.
Closely followoing the CLFS approach, I have so far cross compiled these packages to Hurd:
glibc-2.10.1
libpthread-git
zlib-1.2.3
binutils-2.19.1
gmp-4.3.2
mpfr-2.4.2
ppl-0.10.2
cloog-ppl-0.15.7
gcc-4.3.4
ncurses-5.7
bash-4.1.002
bison-2.4
bzip2-1.0.5
coreutils-8.4
diffutils-2.8.1
findutils-4.4.2
file-5.0.4
flex-2.5.25
gawk-3.1.7
gettext-0.17
grep-2.5.4
gzip-1.3.13
m4-1.4.13
make-3.8.1
nano 2.2.1
patch-2.5.9
sed-4.2.1
tar-1.22
texinfo-4.13a
xz-utils 4.999.9beta
gnumach-git
hurd-git
grub-0.97
That means we only need fakeroot, openssl, libarchive, libfetch to build pacman and have makepkg working and to start actual packaging! (I know there was a script supplied for fakeroot but it needs adjusted...).
Offline
Offline