thank you
]]>Disc-Devil wrote:Very Important Notice
It has come to our knowledge, that glibc with 'linuxthreads' is technically impossible to build on i586...
The most recent glibc PKGBUILD (2.3.5-8) compiles and installs cleanly without modification for i586 over here.
yeah, since when are linuxthread there? the i486 times or so? even earlier i bet. so how could they have possibly decided to not support linuxthreads on a not yet existing platform?
]]>Very Important Notice
It has come to our knowledge, that glibc with 'linuxthreads' is technically impossible to build on i586...
The most recent glibc PKGBUILD (2.3.5-8) compiles and installs cleanly without modification for i586 over here.
]]>try i586.archlinux.nl
Excellent resource - thanks.
Is there a particular reason why your directory/file structure differs from the official 686 repos e.g. ftp.archlinux.org? I've noticed the following differences:
1. You have an extra /base directory which does not exist for 686.
2. Your glibc package is only in /base, whereas the 686 repos have it in /current/os/i686.
3. Your /current/os/i586 does not include a /setup subdirectory containing pacman and packages.txt.
this is the most up2date mirror
]]>I personally have never tested the arch i586. I am just hosting it. I'll try it in vmware and see if it boots.
I use the ISO on 2004 http://archlinux.veloxis.de/i586/%20boot%20cdrom.
And binary repo on http://genesis.blogdns.net/packages/i586/.
unfortunely, I foudn the binary repo lack the most import package glibc. That cause me can't do 'pacman -Syu' which will occurs following error.
grep: /lib/libc.so.6: version `GLIBC_2.3.4' not found (required by grep)
]]>But I found both without md5 checksum.
And when I try to use
mount -o loop xxx.iso /mnt
the /mnt 's content is empty.
So, I think the iso file is broken.
Is it broken?
Aren't you building i586 packages then? Care to join us?
I'm using
CHOST=i586-pc-linux-gnu
CFLAGS="-march=c3 -O2 -pipe -fomit-frame-pointer"
I'm not sure, but I don't think -march=c3 is the same as -march=i586. I think at first c3 was just an alias for i586, but these days the gcc man page says:
i586, pentium
Intel Pentium CPU with no MMX supportc3
Via C3 CPU with MMX and 3dNOW! instruction set support. (No scheduling is implemented for this chip.)
So I'm not sure my packages would be usable by the general i586 audience.
]]>I'm currently building an Arch system from source for a VIA C3 machine that will be a fileserver/firewall/router. I think it is worth the effort compared to just going with another distribution because I like the way Arch is laid out -- it is very simple to configure, customize, and keep up to date, and most of the grunt compiling can actually be done over on my P4 Arch system.
Aren't you building i586 packages then? Care to join us?
]]>