From: Mike Frysinger <vapier@gentoo.org>
To: Alex McWhirter <alexmcwhirter@triadic.us>
Cc: gentoo-sparc@lists.gentoo.org
Subject: [gentoo-sparc] Re: Official SPARC64 Port
Date: Thu, 28 Jan 2016 18:26:17 -0500 [thread overview]
Message-ID: <20160128232617.GG14840@vapier.lan> (raw)
In-Reply-To: <56AA9F05.30307@triadic.us>
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
On 28 Jan 2016 18:06, Alex McWhirter wrote:
> 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.
you don't have to be a dev to get your work merged. you just have to
be a dev to do the final push yourself. so if you have changes that
you think are ready to go now, we can get them merged.
> 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
that bug indicates it's a bug when using gold. so if things are working
fine w/ld.bfd, then it's fine to move forward. that bug also makes it
sound like there's something fundamentally broken in gold that udev just
happens to trip over, so we'd simply say gold isn't yet supported for
sparc.
> 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?
let's ignore the bfd-vs-gold aspect and just assume that it's a situation
where sparc64 always fails and sparc32 always works, and there's no way
to fix the problem. if that truly is the case, packages can be masked in
the sparc64-specific linux profile. it's a bit heavy weight, but since
this scenario rarely comes up, it's not that big of a deal.
a more pertinent example would probably be something like grub-0. the
code fundamentally assumes 32-bit everywhere, and links against 32-bit
system libs, so it's not worth our effort to try and rewrite the code
to work in a 64-bit env. on amd64 non-multilib systems, we mask it,
and provide a grub-static package instead.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-28 23:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 23:06 [gentoo-sparc] Official SPARC64 Port Alex McWhirter
2016-01-28 23:26 ` Mike Frysinger [this message]
2016-01-28 23:37 ` [gentoo-sparc] " 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=20160128232617.GG14840@vapier.lan \
--to=vapier@gentoo.org \
--cc=alexmcwhirter@triadic.us \
--cc=gentoo-sparc@lists.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