Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Nov 1998 04:37:07 -0500 (EST)
From:      "Matthew N. Dodd" <winter@jurai.net>
To:        Gary Palmer <gpalmer@FreeBSD.ORG>
Cc:        Paolo Di Francesco <paipai@tin.it>, freebsd-sparc@FreeBSD.ORG
Subject:   Re: [Ultra] Compiler, again 
Message-ID:  <Pine.BSF.4.02.9811280330350.17054-100000@sasami.jurai.net>
In-Reply-To: <50503.912216979@gjp.erols.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Nov 1998, Gary Palmer wrote:
> While I can't speak authoratitively for the entire core team, I'm 99%
> certain that they would not like using gmake for the u-sparc port.
> While doing so for initial porting isn't objectionable, bringing the
> code tree back to the FreeBSD project with all the bmake files as
> gmake files would present ...  problems :)

I think the big problem is that nobody has a clue about how the whole
system fits together and doesn't understand how the makefiles tie
everything together.

There is no reason to use gmake unless you want to reinvent the world.

If that is the case, don't bother calling it 'FreeBSD'.

Just for kicks I spent a few hours today getting libc from -current to
compile on my NetBSD system.

I used 'make -m /path/to/nfs/mounted/share/mk' and fabbed up a workable
/usr/include/machine/*.h from looking at NetBSD, and the 2 FreeBSD arch
dirs.

Now, I've got libc compiling, but not linking shared, which I believe is a
toolchain issue. (actually a crt0.o issue as I have discovered.)

While I will admit that having a somewhat usable 'bmake' available on the
NetBSD host system makes things easier, getting bmake to compile on other
platforms should be fairly straight-forward (hell, I got it running on
sprite at one point.)

So, if the toolchain hackers can turn on the sparc and sparc64 stuff in
the source tree I think that getting some of the userland bits going on a
NetBSD/OpenBSD system would be do-able.

I'm a bit unsure of how to bootstrap on a NetBSD system as 'buildworld'
seems to look at /usr/lib and /usr/include (chroot tree?) (as it turns
out, defining LD_NOSTD_PATH and then LD_LIBRARY_PATH does what I need for
LD) and makes it difficult for me to provide manually compiled libraries
to link the buildworld tools against.

Anyhow, pursuing silly ideas about switching compilers and using gmake is
just throwing additional steps in an already stepful process.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-sparc" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02.9811280330350.17054-100000>