From: Alex McWhirter <alexmcwhirter@triadic.us>
To: gentoo-sparc@lists.gentoo.org, Mike Frysinger <vapier@gentoo.org>
Subject: [gentoo-sparc] Official SPARC64 Port
Date: Thu, 28 Jan 2016 18:06:45 -0500 [thread overview]
Message-ID: <56AA9F05.30307@triadic.us> (raw)
I'm going to try to keep all future discussion of this in this thread
for now on.
If you've kept up with the sparc list lately (seems like very few people
do these days) i've been working on fixing up the sparc port to include
a pure 64bit port. Basically here is where we stand in regard to the
completion of this project.
Profiles:
sparc32: Done
sparc32-multilib: Done
sparc64: Done
sparc64-multilib: Done
Stage3's
sparc32: Booting
sparc32-multilib: Booting
sparc64: Booting + Fairly Well Tested
sparc64-multilib: Booting
Install ISO: TODO
The profiles have all been reworked quite a bit, which is why i feel the
need to test all of them thoroughly.
It's also worth noting that at this moment i am not an official Gentoo
developer, although i am working towards having that goal met in the
very near future. So at this point it's possible all of my work is junk
as no one has really looked over it but me :p, so keep that in mind.
That being said, i am posting this from an Ultra 45 with ZFS and a
native 64bit userland ;)
Ok, so now on to an issue...
pciutils will not compile on sparc64, which i believe could be udev
related. See the error below.
../../lib64/libudev.so: Only registers %g[2367] can be declared using
STT_REGISTER
It seems like systemd also has a similar issue.
https://sourceware.org/bugzilla/show_bug.cgi?id=19019
Originally it was decided to use the old sparc keyword for sparc32 and
sparc64, but in this case we have an app that will compile on sparc32
but not sparc64. How should this be handled? A new keyword would be a
pain, so is there another way of dealing with this?
next reply other threads:[~2016-01-28 23:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 23:06 Alex McWhirter [this message]
2016-01-28 23:26 ` [gentoo-sparc] Re: Official SPARC64 Port Mike Frysinger
2016-01-28 23:37 ` Alex McWhirter
2016-01-28 23:46 ` Mike Frysinger
2016-01-30 0:28 ` [gentoo-sparc] " Alex McWhirter
2016-01-30 0:44 ` Mike Frysinger
2016-01-30 0:55 ` Alex McWhirter
2016-02-01 9:24 ` Alex McWhirter
2016-02-01 17:44 ` Mike Frysinger
2016-02-01 19:29 ` Alex McWhirter
2016-02-01 20:24 ` Mike Frysinger
2016-02-01 20:34 ` Alex McWhirter
2016-02-01 20:51 ` Mike Frysinger
2016-02-01 22:03 ` Alex McWhirter
2016-02-04 18:40 ` Alex McWhirter
2016-02-04 21:54 ` Mike Frysinger
2016-02-04 23:44 ` Alex McWhirter
2016-02-07 10:35 ` Alex McWhirter
2016-02-08 15:21 ` Mike Frysinger
2016-02-08 20:48 ` Alex McWhirter
2016-02-09 5:11 ` Alex McWhirter
2016-02-09 6:14 ` Mike Frysinger
2016-02-13 9:26 ` Alex McWhirter
2016-02-13 11:25 ` Mike Frysinger
2016-02-13 17:32 ` Alex McWhirter
2016-02-13 21:26 ` Alex McWhirter
2016-02-14 0:44 ` Mike Frysinger
2016-02-14 23:44 ` Alex McWhirter
2016-02-15 2:13 ` Mike Frysinger
2016-02-17 22:11 ` Alex McWhirter
2016-02-17 22:46 ` Mike Frysinger
2016-02-17 22:52 ` Alex McWhirter
2016-02-19 8:37 ` Alex McWhirter
2016-03-11 3:53 ` Alex McWhirter
2016-08-08 22:52 ` Jack Morgan
2016-08-09 5:14 ` alexmcwhirter
2016-08-10 18:45 ` Jack Morgan
2016-08-31 17:26 ` alexmcwhirter
2016-09-01 0:46 ` Jack Morgan
2016-09-04 19:27 ` [gentoo-sparc] -fPIC vs -fpic = Headaches alexmcwhirter
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=56AA9F05.30307@triadic.us \
--to=alexmcwhirter@triadic.us \
--cc=gentoo-sparc@lists.gentoo.org \
--cc=vapier@gentoo.org \
/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