public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: maarten@murphy.belgonet.be
To: "Jared H. Hudson" <jhhudso@volumehost.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Made sparc32 port of gentoo
Date: Thu, 11 Apr 2002 17:15:07 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0204111711160.17596-100000@murphy.localnet> (raw)
In-Reply-To: <Pine.LNX.4.44.0204101642410.15027-100000@volumehost.com>

Jared,

Another one with old Sparc hardware :). I'll be sure to lower the stage1
CPU requirements to hopefully include support for sun4c and better though
I might not be able to test it on anything less than sun4m. I use sun4u 
for building.

cheers,
maarten

On Wed, 10 Apr 2002, Jared H. Hudson wrote:

> 
> That's awesome. Congrats. I've thought about doing the same thing, but all 
> my Sun's are Sunstation 1's and 2's. So, I've not looked forward to 
> compiling on them. I would email Daniel directly if I were you, concerning 
> this. drobbins@gentoo.org
> 
> -Jared H.
> 
> On Wed, 10 Apr 2002 maarten@murphy.belgonet.be wrote:
> 
> > Hi,
> > 
> > I've made a sparc32 port of Gentoo but I couldn't find any mention of
> > porting in the documentation. I'd like to know:
> > 
> > 1) Are you 'friendly' towards ports?
> > 
> > 
> > 2) Can I put the stage 1 tarball on your site?
> > 
> > 
> > 3) Can you setup a new CVS tree so it can be accessed like:
> > SYNC="rsync://cvs.gentoo.org/gentoo-sparc-portage"
> > 
> > 
> > 3) The linux-headers packages contain 2 platform specific lines, can these 
> > be wrapped using uname -m statements?
> > 
> > cp -ax ${S}/include/asm-i386/* ${D}/usr/include/asm
> > [...]
> > cp "${ROOT}usr/src/linux-${KV}/arch/i386/defconfig" .config
> > 
> > Shall I write a patch?
> > 
> > 
> > 4) I'm working on a 64-bit capable version using redhat's gcc
> > 2.96-20000731 for compiling sparc64 (the kernel prefers this). Would it be
> > possible to have this package stored on your site? There are >300 patches
> > that are applied to this tree so I'd rather not duplicate that work and
> > publish a patched tree immediately. This problem is going away anyway as
> > we'll reportely have decent sparc64 capability in the upcoming gcc 3.1
> > tree.
> > 
> > Thanks!
> > maarten
> > 
> > 
> > 
> > 
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> > 
> 
> -- 
> Using the internet as it was originally intended...
> for the further research of pornography and pipebombs.
> 



  reply	other threads:[~2002-04-11 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 13:38 [gentoo-dev] Made sparc32 port of gentoo maarten
2002-04-10 21:44 ` Jared H. Hudson
2002-04-11 15:15   ` maarten [this message]
2002-04-11 19:02     ` Paul de Vrieze
2002-04-11 19:09       ` Marc Soda
2002-04-11 13:14 ` Karl Trygve Kalleberg
2002-04-11 15:11   ` maarten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0204111711160.17596-100000@murphy.localnet \
    --to=maarten@murphy.belgonet.be \
    --cc=gentoo-dev@gentoo.org \
    --cc=jhhudso@volumehost.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox