bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Oskit-mach success with gcc-3.0


From: Jeff Bailey
Subject: Re: Oskit-mach success with gcc-3.0
Date: Fri, 19 Apr 2002 14:44:42 -0700
User-agent: Mutt/1.3.28i

On Fri, Apr 19, 2002 at 05:04:57PM -0400, Roland McGrath wrote:

> > I had a moment, so I decided to try building oskit-mach with
> > gcc-3.0.  Note that this is linked against an oskit build with
> > gcc-2.95.4.  It appears to work (boot, mount filesystem, ping
> > localhost)

> Great!  Thanks for verifying that this works.

At lunch I started a compile of oskit with gcc-3, and it appears to
have built.  I'm going to play with an all gcc-3 based
oskit+oskit-mach when I get home tonight.

> > Aside from the usual two patches, it compiled fine.  

> I don't know what patches you are talking about.

This patch to Makefile.in was reported by James Morrison a few months
ago:

cvs server: Diffing .
Index: Makefile.in
===================================================================
RCS file: /cvsroot/hurd/gnumach/Makefile.in,v
retrieving revision 1.22.2.17
diff -u -p -r1.22.2.17 Makefile.in
--- Makefile.in 4 Mar 2002 19:18:10 -0000       1.22.2.17
+++ Makefile.in 19 Apr 2002 21:42:22 -0000
@@ -269,7 +269,7 @@ magic-symbols := etext edata end
 
 
 OSKIT_LIBDIR = @OSKIT_LIBDIR@
-OSKIT_LIBS = -loskit_kern -loskit_lmm -loskit_com -loskit_smp \
+OSKIT_LIBS = -loskit_kern -loskit_lmm -loskit_com \
             -loskit_exec -loskit_unsupp \
             -loskit_dev -loskit_linux_dev -loskit_diskpart \
 
@@ -327,7 +327,7 @@ init-%.c:
 
 kernel-%.o: $(OSKIT_LIBDIR)/multiboot.o $(objfiles) init-%.o
        $(CC) $(CFLAGS) -nostdlib -nostartfiles $(LDFLAGS) -r -o $@ \
-             -Wl,-\( $^ $(OSKIT_LIBS) -Wl,-\) -lgcc
+             -Wl,-\( $^ -L$(OSKIT_LIBDIR)/.. $(OSKIT_LIBS) -Wl,-\) -lgcc
 
 #
 # Installation


> > However, i386asm.symc has the following:

> The trivial patch I just checked in fixes this (it's just harmless
> warnings).

Thanks.

Tks,
Jeff Bailey



reply via email to

[Prev in Thread] Current Thread [Next in Thread]