This is the mail archive of the newlib@sources.redhat.com mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: asprintf

From: Shaun Jackman <sjackman at gmail dot com>
To: Jeff Johnston <jjohnstn at redhat dot com>
Cc: newlib at sources dot redhat dot com
Date: Tue, 25 Jan 2005 16:38:42 -0800
Subject: Re: asprintf
References: <7f45d93905012514066eb482dd@mail.gmail.com> <41F6D551.1030005@redhat.com>
Reply-to: Shaun Jackman <sjackman at gmail dot com>

Sorry, my mistake. I got a hold of the wrong end of the stick. I was
in fact linking against an old library that had asprintf, but no
vasprintf. Thanks for the explanation of EL/IX.

Incidentally, I'm looking at these functions that are somewhat
atypical for an embedded system because I'm looking at compiling
busybox with newlib. With a healthy does of ifdefs, I've managed to
compile it. I'm gonna cross my fingers and hope for a shell prompt
now.

Cheers,
Shaun

> No.  You need to understand what is happening.  If you don't configure a
> specific EL/IX level, everything gets built (i.e. EL/IX level is not defined to
> be level 1, 2, 3, etc..).  If you specifically configure with EL/IX level 1,
> then the EL/IX level will be set to 1 and asprintf will not be included as per
> the EL/IX standard.  If you specify EL/IX level 2 or above, then you get
> asprintf, again per the standard.
> 
> -- Jeff J.

References:
- asprintf
  - From: Shaun Jackman
- Re: asprintf
  - From: Jeff Johnston

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]