From: Alex McWhirter <alexmcwhirter@triadic.us>
To: gentoo-sparc@lists.gentoo.org
Subject: Re: [gentoo-sparc] Official SPARC64 Port
Date: Mon, 1 Feb 2016 14:29:47 -0500 [thread overview]
Message-ID: <56AFB22B.5090405@triadic.us> (raw)
In-Reply-To: <20160201174452.GH7732@vapier.lan>
On 02/01/2016 12:44 PM, Mike Frysinger wrote:
> On 29 Jan 2016 19:55, Alex McWhirter wrote:
>> On 01/29/2016 07:44 PM, Mike Frysinger wrote:
>>> On 29 Jan 2016 19:28, Alex McWhirter wrote:
>>>> Regarding the issue with pcitutils, it is indeed and issue with gold. It
>>>> turns out udev is broken as well, as in it wont start.
>>>>
>>>> binutils has supposedly fixed this issue upstream, i may try to emerge
>>>> 9999 later tonight. perhaps eudev fairs a bit better than udev? Would
>>>> there be any issue with moving to eudev as a default?
>>> arches should not be picking any defaults like udev. we should be using
>>> the same default across all linux systems. especially if the only point
>>> is to workaround a bug in gold.
>>>
>>> is the fix in binutils-2.26 ? that's going into the tree in a bit ...
>>> i'm waiting for some feedback from upstream before i push it.
>> I can check to see if the fix is in .26, but eudev does work without
>> issue for what it's worth. pciutils is also compiling without issue with
>> eudev.
>>
>> I will try pulling 9999 and see if the issue is no longer there, if it's
>> been resolved there then ill check into .26
>>
>> Without that fix, sparc64 is probably a no-go. I suppose we could always
>> patch .25 if needed.
> why ? as i said, gold is not the default, and we don't hold up issues
> because of gold compatibility. if sparc64 w/ld.bfd works fine, then
> that's all we need.
> -mike
>
It looks like udev is hard coded to use gold, i may have to hack around
with configure.ac to get it to compile with bfd.
next prev parent reply other threads:[~2016-02-01 19:29 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
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 [this message]
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=56AFB22B.5090405@triadic.us \
--to=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