Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 14 Jan 2014 16:45:53 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Re: Am I using PRIxPTR wrong?  Musl-libc complains, glibc
 doesn't

On Tue, Jan 14, 2014 at 09:37:28PM +0000, David Wuertele wrote:
> Rich Felker <dalias <at> aerifal.cx> writes:
> > On Tue, Jan 14, 2014 at 10:06:01PM +0100, Szabolcs Nagy wrote:
> > > * David Wuertele <dave+gmane <at> wuertele.com> [2014-01-14 20:36:36 +0000]:
> > > > ** Both native (x86_64 glibc) and target (arm musl-libc) define
> > > > ** PRIxPTR as "lx", but uintptr_t as unsigned int:
> > > 
> > > musl defines it to "x" on 32bit archs
> > 
> > Maybe I misread; it looks like David's problem is finding "lx" in the
> > header while the actual type is "unsigned int". Perhaps this is due to
> > using an older version of musl where the "lx" was there incorrectly?
> 
> I'm using musl-0.9.14, I see that 9.15 just came out this month.
> Did 0.9.14 have the problem?

I know a problem like this was fixed sometime not too long ago, and it
was probably between the 0.9.14 and 0.9.15 releases.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.