Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] AC_SYS_LARGEFILE
Date: Wed, 11 Nov 2009 05:09:00 -0000	[thread overview]
Message-ID: <20091111050907.GC26791@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3vdhrblbc.fsf@fleche.redhat.com>

On Tue, 03 Nov 2009 17:54:47 +0100, Tom Tromey wrote:
> >>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
> 
> Joel> This macro ran a bell, and I found:
> Joel> http://www.sourceware.org/ml/binutils/2008-11/msg00248.html
> 
> Joel> Basically, we cannot use AC_SYS_LARGEFILE on Solaris.  The little
> Joel> piece of code that I wrote to disable it on solaris-native should
> Joel> work well in this case too.
> 
> libiberty uses AC_SYS_LARGEFILE without any Solaris-specific code.  Why
> does that work?

Because the Solaris exception is required only for bfd/ and libiberty has no
ABI dependencies related to the largefile support.  bfd/ interface has such
ABI dependencies (at least `struct stat' of bfd_stat()).
	http://gcc.gnu.org/ml/gcc-patches/2009-11/msg00289.html


> If this code is still needed, then let me suggest the more painful but
> also nicer approach of a new .m4 file in config/.

There is now config/largefile.m4.


This mail thread is now closed by the checked-in ACX_LARGEFILE macro usage:
	http://sourceware.org/ml/gdb-cvs/2009-11/msg00079.html


Regards,
Jan


      parent reply	other threads:[~2009-11-11  5:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  9:44 Jan Kratochvil
2009-11-03 14:00 ` Joel Brobecker
2009-11-03 16:55   ` Tom Tromey
2009-11-03 17:07     ` Tom Tromey
2009-11-11  5:09     ` Jan Kratochvil [this message]

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=20091111050907.GC26791@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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