All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH]: Fix fs modules on sparc64 build with newer gcc
Date: Sat, 11 Apr 2009 23:53:33 -0400	[thread overview]
Message-ID: <1239508413.6491.11.camel@mj> (raw)
In-Reply-To: <20090411.012731.101657495.davem@davemloft.net>

On Sat, 2009-04-11 at 01:27 -0700, David Miller wrote:
> Newer versions of gcc emit references to libgcc internal
> functions __bswapsi2 and __bswapdi2 when building ufs and
> some other filesystem modules on sparc64.
> 
> Unfortunately older versions of gcc lack these symbols in
> libgcc so we can't export them universally, we have to check
> for it using configure link tests.
> 
> I commited this under the "trust dave with sparc stuff" rule.
> Let me know if it that wasn't appropriate in this case :-)

Actually, changes to configure.ac affect other users as well.  Users of
other architectures would have to run those checks.

I would try to use weak functions or something like that.  Failing that,
I would add a check for affected architectures only.  Even if that would
make the script longer, it would make it clear which architectures need
the check, which is probably a good idea.

> I also rebuild configure when commiting these changes.

I see that configure and config.h.in we built by different versions of
autoconf.  That's likely to break.

I would run autogen.sh and commit all changed files after examining the
changes.  As a courtesy to others, I install the same version of
Autoconf that the current configure script was generated with.

Adding or removing files means that DISTLIST will change.  That should
be committed as well.

Personally, I would remove all files generated by autogen.sh from the
repository.  But I don't want to do something that is inconvenient to
others.  The issue was discussed in the past and the decision was to
keep those files.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2009-04-12  3:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11  8:27 [PATCH]: Fix fs modules on sparc64 build with newer gcc David Miller
2009-04-12  3:53 ` Pavel Roskin [this message]
2009-04-12  7:58   ` David Miller
2009-04-12 21:19     ` Pavel Roskin
2009-04-13  1:05       ` David Miller
2009-04-13  5:06         ` Pavel Roskin
2009-04-13  6:31           ` David Miller
2009-05-02 14:35 ` Robert Millan

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=1239508413.6491.11.camel@mj \
    --to=proski@gnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.