On Tue, 2 Aug 2011 02:08:12 +0200, Samuel Thibault wrote:
Indeed. flubber however does respond. Maybe you should request for an
account there to be able to push changes via git.
I do have an account on flubber already. Should I clone the repo in my
flubber home directory, edit there and then p
On Mon, 1 Aug 2011 16:51:52 -0700 (PDT), Roland McGrath wrote:
I guess Fedora does not leave its 32bit libc.a in /usr/lib, and thus
with -nostdlib it won't find it there. You need to pass LDFLAGS
which
lead to it.
It is, but it's in a separate package called glibc-static that you
don't
get
On Mon, 01 Aug 2011 18:26:16 -0400, Andrew Engelbrecht wrote:
configfrag.ac ends like this:
# `${file}' and `$file' have different meanings here with respect to
having the
# files in the referenced directory considered for `make dist' or
not. See
#
<http://lists.gnu.or
On Tue, 2 Aug 2011 00:15:03 +0200, Samuel Thibault wrote:
Well, the Debian package does it too, but gets
config.status: linking ../i386/i386 to machine
It's odd that you get this output while the code is
AC_CONFIG_LINKS([machine:$systype/$systype
mach/machine:$systype/include
On Mon, 1 Aug 2011 23:56:03 +0200, Samuel Thibault wrote:
It should have been done at the end of ./configure (see the
configfrag.ac file): I'm getting
config.status: linking i386/i386 to machine
config.status: linking i386/include/mach/i386 to mach/machine
Here's what I'm getting:
config.stat
On Mon, 1 Aug 2011 21:56:35 +0200, Samuel Thibault wrote:
Are you building on some x86_64 linux?
Yes, 64bit Fedora.
In that case it's deemed to fail since linux will try to build
gnumach
is 64bit mode. You need to cross-compile:
I did configure using the --host=i386 flag, but I'll do it yo
Hello, I'm trying to build gnumach.gz from git, but I'm having some
issues.
I'm trying the instructions from:
http://www.gnu.org/software/hurd/microkernel/mach/gnumach/building.html
, but i'm using git, not cvs, as it appears to be more up to date and
the repos listed at
http://www.gnu.org/s
Have you tried running fsck on the disk image? It won't solve any ext2fs
server instability, but it should give you another shot at starting up.
The only trick is doing it outside of qemu, since your system isn't
booting up. Also, it's somewhat more complicated because it has multiple
partitions.
