From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC PATCH] configure check for ld's --no-relax flag
Date: Sun, 21 Sep 2014 21:50:30 +0400 [thread overview]
Message-ID: <20140921215030.1af8c476@opensuse.site> (raw)
In-Reply-To: <541F04CC.3040509@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2530 bytes --]
В Sun, 21 Sep 2014 19:03:08 +0200
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> On 04.08.2014 16:53, Andrey Borzenkov wrote:
> > В Mon, 04 Aug 2014 10:45:22 +0400
> > Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com> пишет:
> >
> >> Hi!
> >>
> >> On 08/01/2014 07:40 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> >>> On 01.08.2014 17:35, Andrey Borzenkov wrote:
> >>>> В Fri, 1 Aug 2014 16:15:56 +0400
> >>>> Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com> пишет:
> >>>>
> >>>>> Early versions of binutils doesn't support --no-relax flag, so
> >>>>> commit 063f2a04d158ec1b275a925dfbae74b124708cde prevents building
> >>>>> with such versions.
> >>>>>
> >>>>> Signed-off-by: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
> >>>>> ---
> >>>>> conf/Makefile.common | 8 ++++++++
> >>>>> configure.ac | 10 ++++++++++
> >>>>> 2 files changed, 18 insertions(+), 0 deletions(-)
> >>>>>
> >>>>> diff --git a/conf/Makefile.common b/conf/Makefile.common
> >>>>> index e4c301f..5bda66f 100644
> >>>>> --- a/conf/Makefile.common
> >>>>> +++ b/conf/Makefile.common
> >>>>> @@ -8,11 +8,19 @@ unexport LC_ALL
> >>>>> # Platform specific options
> >>>>> if COND_sparc64_ieee1275
> >>>>> CFLAGS_PLATFORM += -mno-app-regs
> >>>>> +if COND_LD_SUPPORTS_NO_RELAX
> >>>>> LDFLAGS_PLATFORM = -Wl,-melf64_sparc -Wl,--no-relax
> >>>>> +else
> >>>>> + LDFLAGS_PLATFORM = -Wl,-melf64_sparc -mno-relax
> >>>>> +endif
> >>>>
> >>>> TBO I think commit should simply be reverted. "Uniformity" is rather
> >>>> poor excuse for breaking existing systems.
> >>>>
> >>> This commit is needed for clang to compile for sparc64. Given that
> >>> sparc64 clang still doesn't really work I'm ok with reverting, at least
> >>> for now.
> >>
> >> But, it this case, maybe it would be better to consider
> >> reviewing/applying this patch? Just to not return to this issue after
> >> some time?
> >>
> >> Andrey, Vladimir, what do you think?
> >>
> >
> > Yes, commit message was pretty confusing. This leaves the question,
> > whether combination of clang and binutils that do not support
> > -Wl,--no-relax exists though :) Otherwise I agree, we should use this
> > patch.
> >
> I think we could try to push for clang to have -mno-relax. They're
> usually pretty responsive and we'll probably need few fixes for few
> other clang problems anyway. For now I just reverted it.
Did you push it?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-09-21 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 12:15 [RFC PATCH] configure check for ld's --no-relax flag Stanislav Kholmanskikh
2014-08-01 15:35 ` Andrey Borzenkov
2014-08-01 15:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-08-04 6:45 ` Stanislav Kholmanskikh
2014-08-04 14:53 ` Andrey Borzenkov
2014-09-21 17:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-09-21 17:50 ` Andrei Borzenkov [this message]
2014-09-21 18:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20140921215030.1af8c476@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).