From: Alex McWhirter <alexmcwhirter@triadic.us>
To: gentoo-sparc@lists.gentoo.org
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: Re: [gentoo-sparc] Re: Official SPARC64 Port
Date: Thu, 28 Jan 2016 18:37:16 -0500 [thread overview]
Message-ID: <56AAA62C.1040908@triadic.us> (raw)
In-Reply-To: <20160128232617.GG14840@vapier.lan>
On 01/28/2016 06:26 PM, Mike Frysinger wrote:
>
> 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.
I want to do a bit more testing to ensure im not going to break any
existing sparc32 installs. I am fairly certain that we are going to
break sparc32 + multilib, but considering that profile was never
officially released it may not be that big of a deal.
My main concern with sparc32 + multilib is what happens when you have
system installed with SYMLINK_LIB="yes" and later change it to "no".
> 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
True, that slipped my mind. I've already had to patch a few things that
make assumptions about things they otherwise shouldn't, sparc-utils
being a prime example which always assumes a 32bit userland and breaks
silo in a 64bit userland. So if it ends up not being an insanely
complicated issue ill take a stab at it. However, I'll save that
discussion for another day.
next prev parent reply other threads:[~2016-01-28 23:37 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 ` [gentoo-sparc] " Mike Frysinger
2016-01-28 23:37 ` Alex McWhirter [this message]
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=56AAA62C.1040908@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