mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eric Blake <eblake@redhat.com>,
	musl@lists.openwall.com, bug-gnulib@gnu.org
Subject: Re: gnulib cross-compiling issue with musl
Date: Wed, 19 Jun 2013 10:53:04 -0400	[thread overview]
Message-ID: <20130619145304.GY29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <51C0BE66.5000402@cs.ucla.edu>

On Tue, Jun 18, 2013 at 01:09:10PM -0700, Paul Eggert wrote:
> On 06/18/13 11:42, Rich Felker wrote:
> > if
> > you think it matters, you could add #elif defined _POSIX_VERSION
> > containing the if(0)
> 
> Yes, that should work, though it needs to check a couple ore
> things as well.  I pushed the following: does it work for you?
> 
> fflush, fseeko: port to musl cross-compiles
> * lib/fseeko.c (fseeko): Assume that fflushing stdin works if
> on some implementation that (1) is not known to be buggy,
> (2) claims conformance to POSIX.1-2008 or later, and (3) is being
> cross-compiled to so we can't easily check for lack of
> conformance.  This is for cross-compiling to musl.
> Reported by Rich Felker in
> <http://lists.gnu.org/archive/html/bug-gnulib/2013-06/msg00043.html>.

Thank you. This patch looks like it should solve the problem. I'll
make sure it gets tested with someone on our team doing cross compiles
and let you know if we run into any problems.

Rich


  reply	other threads:[~2013-06-19 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130618170305.GA30936@brightrain.aerifal.cx>
     [not found] ` <51C09BD9.8000503@cs.ucla.edu>
     [not found]   ` <20130618180755.GV29800@brightrain.aerifal.cx>
     [not found]     ` <51C0A7D2.4020605@cs.ucla.edu>
2013-06-18 18:42       ` Rich Felker
2013-06-18 20:09         ` Paul Eggert
2013-06-19 14:53           ` Rich Felker [this message]
2013-06-20 16:08         ` Anthony G. Basile
2013-06-20 16:38           ` Rich Felker

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=20130619145304.GY29800@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=bug-gnulib@gnu.org \
    --cc=eblake@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=musl@lists.openwall.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).