Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Nov 1998 22:54:23 -0500 (EST)
From:      Alfred Perlstein <bright@hotjobs.com>
To:        "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc:        Greg Lehey <grog@lemis.com>, Paolo Di Francesco <paipai@tin.it>, freebsd-sparc@FreeBSD.ORG, Jordan Hubbard <jkh@FreeBSD.ORG>
Subject:   Re: [Ultra] Compiler, again 
Message-ID:  <Pine.BSF.4.05.9811272240140.1605-100000@bright.fx.genx.net>
In-Reply-To: <7427.912220688@zippy.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help

I want to address several issues that popped up so far today... w3rd

---

The issue about cross compiling, i'm seriously thinking of installing
ultraP to make cross compiling an almost non-issue.  Since their
compiler/toolchain work all that is needed is the small patch given to me
via email to get gcc to produce what would become FreeBSD-sparc64 friendly
code.

--

Which gcc/egcs probably the one that comes with ultraP, we are striving
for correctness and egcs is supposedly VERY broken for usparc64, even
though i've annoyed the lists about gcc2.8.1 i think for consistancy's
sake we should try to use 2.7.2.2 if there are patches to get it to
generate correct asm code.

--

About using gmake to build gcc:

ugh, NO GMAKE, don't use it for our current tree and we shouldn't have to
for the sparc tree :)

I think the way most things that use configure/gmake are brough into the
tree is this:

1) configure is run to make gmake files.
2) those generated files are then clobbered into a bmake structure
(if i'm wrong someone pipe up and tell at what stage the files are
bmake'd)

I got mid-way bmaking perl5 for 3.0 before someone piped up that they had
it 90% done, and a week later it was brought in.

This won't be a problem, .: no gmake :)

--

About the binutils, it's already been explained why these are needed, I
don't see how we are to compile things unless we have ld, and gas amongst
other things.  You can NOT build a kernel without ld because the object
files must be linked as the final stage of the build.

This is a mute point, binutils seemed to build fine for target
sparc64-elf, gcc was the one that gave me a headache.  I wasn't able to
verify the correctness of the binutils because of my lack of a 64bit
producing gcc.

--

Lastly i want to thank all those who have taken interest, this is really
encouraging and the pointers and code that people have dragged out of the
closet to get me looking in the right direction is VERY MUCH appreciated.

thank you,
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/                        3.0-current

On Fri, 27 Nov 1998, Jordan K. Hubbard wrote:

> I don't have enough context to even really comment on this.  There is
> a SPARC port? What stage is it at - conceptual or close to working?
> Is this an embedded solution or an attempt to bring FreeBSD, in all
> its glory, to the SPARc platform?  If it's the former, then I guess
> the answer is "don't really care" since that's a local preference
> issue.  If it's the latter, then the question of which make to use
> isn't even a question: BSD make.  It wouldn't be "BSD" otherwise.
> 
> - Jordan
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-sparc" in the body of the message
> 


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.05.9811272240140.1605-100000>