Re: glibc devel info pages

2001-01-03 Thread Ben Collins
On Wed, Jan 03, 2001 at 04:37:44PM +1100, Brian May wrote: Ben == Ben Collins [EMAIL PROTECTED] writes: Ben By default, __USE_GNU is defined. If you want to define it (perhaps you meant ...is undefined???) Ben explicitly, then use -D_GNU_SOURCE in your CFLAGS. It doesn't seem

Re: glibc devel info pages

2001-01-03 Thread Brian May
Ben == Ben Collins [EMAIL PROTECTED] writes: Ben No, __USE_GNU is defined, unless one of the other _XXX_SOURCE Ben macros are also defined (like _SVID_SOURCE or _XOPEN_SOURCE, Ben or similar). Most likely the program you are compiling is Ben defining one of these aswell. In that

Re: glibc devel info pages

2001-01-03 Thread Eric G . Miller
On Wed, Jan 03, 2001 at 04:47:55PM +1100, Brian May wrote: #include stdio.h #include stdlib.h #include string.h #include stdarg.h but still get a warning: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include-g -O2 -Wall -c -o main.o `test -f main.c || echo './'`main.c main.c: In function

Re: glibc devel info pages

2001-01-03 Thread Richard Cobbe
Lo, on Wednesday, January 3, Ben Collins did write: On Wed, Jan 03, 2001 at 04:37:44PM +1100, Brian May wrote: Ben == Ben Collins [EMAIL PROTECTED] writes: Ben By default, __USE_GNU is defined. If you want to define it (perhaps you meant ...is undefined???) Ben

glibc devel info pages

2001-01-02 Thread Brian May
Hello, What is the quickest way to look up a include file required for a given function in glibc? Before, with the man page system, I would be able to type in man vasprintf and all the information I ever required would be presented on the screen right in front of me. Now, it seems that I have

Re: glibc devel info pages

2001-01-02 Thread Mike
Brian May wrote: Hello, What is the quickest way to look up a include file required for a given function in glibc? Before, with the man page system, I would be able to type in man vasprintf and all the information I ever required would be presented on the screen right in front of me.

Re: glibc devel info pages

2001-01-02 Thread Ben Collins
On Wed, Jan 03, 2001 at 01:56:23PM +1100, Brian May wrote: #ifdef __USE_GNU /* Write formatted output to a string dynamically allocated with `malloc'. Store the address of the string in *PTR. */ extern int vasprintf __P ((char **__restrict __ptr, __const char

Re: glibc devel info pages

2001-01-02 Thread David Purton
On Tue, 2 Jan 2001, Mike wrote: hal9000:~$ man vasprintf Reformatting vasprintf(3), please wait... PRINTF(3) Linux Programmer's Manual PRINTF(3) NAME printf, fprintf, sprintf, snprintf, vprintf, vfprintf, vsprintf, vsnprintf - formatted output

Re: glibc devel info pages

2001-01-02 Thread Paul D. Smith
%% David Purton [EMAIL PROTECTED] writes: dp On Tue, 2 Jan 2001, Mike wrote: hal9000:~$ man vasprintf dp useful dp what package provides these man pages? My system sez: $ dpkg -S vasprintf manpages-dev: /usr/share/man/man3/vasprintf.3.gz So, use: # apt-get install

Re: glibc devel info pages

2001-01-02 Thread Brian May
Ben == Ben Collins [EMAIL PROTECTED] writes: Ben By default, __USE_GNU is defined. If you want to define it (perhaps you meant ...is undefined???) Ben explicitly, then use -D_GNU_SOURCE in your CFLAGS. It doesn't seem to be the case here: gcc -DHAVE_CONFIG_H -I. -I. -I..

Re: glibc devel info pages

2001-01-02 Thread Brian May
Mike == Mike [EMAIL PROTECTED] writes: Mike So for vasprintf you would need stdarg.h Or am I reading Mike this incorrectly? Going on the presumption that I'm reading Mike this right, I take it this is not working for you? If not, Mike have you got the manpages-dev package