[uClibc]Building BB against uClibc...

[Tom Cameron]

Hello all,
	When building the latest BB source against uClibc (by using the CC=
option), I get the following error:

/mnt/lfs/usr/src/LRP-KonRAD/uClibc/extra/gcc-uClibc/gcc-uClibc-i386 -Wall
-O2 -fomit-frame-pointer -D_GNU_SOURCE -I- -I. -I.  -DBB_VER='"0.49"'
-DBB_BT='"2001.02.07-20:31+0000"' -mcpu=i586 -march=i586   -c dutmp.c -o
dutmp.o
dutmp.c: In function `dutmp_main':
dutmp.c:61: structure has no member named `ut_exit'
dutmp.c:61: structure has no member named `ut_exit'
dutmp.c:62: structure has no member named `ut_session'
dutmp.c:63: structure has no member named `ut_tv'
dutmp.c:63: structure has no member named `ut_tv'
dutmp.c:64: warning: unsigned int format, long unsigned int arg (arg 13)
make: *** [dutmp.o] Error 1

	I disabled the dutmp option, and now get the following error
message:

/mnt/lfs/usr/src/LRP-KonRAD/uClibc/extra/gcc-uClibc/gcc-uClibc-i386 -Wall
-O2 -fomit-frame-pointer -D_GNU_SOURCE -I- -I. -I.  -DBB_VER='"0.49"'
-DBB_BT='"2001.02.07-21:27+0000"' -mcpu=i586 -march=i586   -c gunzip.c -o
gunzip.o
gunzip.c: In function `gunzip_main':
gunzip.c:1335: `O_NOFOLLOW' undeclared (first use in this function)
gunzip.c:1335: (Each undeclared identifier is reported only once
gunzip.c:1335: for each function it appears in.)
make: *** [gunzip.o] Error 1

	Anyone know where the problem is?  Missing info in a header file, or
a C file?  Any help is, as always, GREATLY appreciated.

--
Thomas Cameron
Network Technician / Operations Specialist
St. Mary's Bank

> -----Original Message-----
> From:	Manuel Novoa III [SMTP:mnovoa3 at bellsouth.net]
> Sent:	Wednesday, February 07, 2001 2:09 PM
> To:	uclibc at uclibc.org
> Subject:	[uClibc]rfc: string streams in uClibc
> 
> 
> Hello everyone,
> 
> Before I was out of touch for a week, I had been working on stdio stuff in
> uClibc.  I'm about to get back to work on that and I wanted to throw out
> some
> ideas for comments/feedback.
> 
> While I was working on cleaning up the *s*printf functions that it would
> be
> fairly easy to implement "string streams" in uClibc similar to those in
> C++.
> What I had in mind was something like (and this is really just of the top
> of my
> head):
> 
> FILE *csn_fopen(const char *buffer, size_t bufsize)
>     Simulate a read-only FILE using the supplied buffer of specified size.
> 
> FILE *cs0_fopen(const char *buffer)
>     Simulate a read-only FILE using the supplied nul-terminated string.
> 
> FILE *sn_fopen(char *buffer, size_t bufsize)
>     Simulate a read-write FILE using the supplied buffer of specified
> size.
>     Note: Something like this is already done implicitly by the *s*printf
> funcs.
> 
> FILE *sn_fopen(size_t growby)
>     Simulate a read-write FILE which grows dynamically using remalloc.
> 
> FILE *sb_fopen(size_t blocksize)
>     Simulate a read-write FILE using 'blocksize' blocks allocated
> indendently
> and grouped together in some way -- as a linked list, a tree, etc.  This
> would
> be useful in a NOMMU environment.
> 
> I foresee very little code size increase for the current stdio functions
> in
> order to support the above (except possibly for the last function and
> even that shouldn't be that great depending on how you want to group the
> blocks).  Of course, this could alway be made a configurable option.
> 
> Again, I'm looking for feedback here.  All comments welcome.  Thanks.
> 
> Manuel
> 
> 
> 
> 
> _______________________________________________
> uclibc mailing list
> uclibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc