Not a problem. I recall seeing an actual uClibc patch for it, although I
just made my own and emailed it to the list. The patch doesn't get
applied to the .config file but rather to the error.c file to uncomment
the existing declaration. The only reason I put forward the concept of
applying it to uClibc rather than gettext is because of the potential
number of other packages which would also end up having the same
problem. I have attached my patch to this message to save you searching.
Regards,
Brian.
Robert Connolly wrote:
> If it can be added to uClibc, in the .config file, then that's probably a
> good
> idea. The Gettext patch from uclibc.org was the first solution I found, and I
> didn't check into it after.
>
> robert
>
>
>> Robert,
>>
>> What is the reasoning behind patching gettext for the
>> error_print_progname when it could be done in uClibc to allow all
>> packages to work rather than applying a similar patch to all packages
>> which require the function call?
>>
>> Cheers,
>> Brian.
>>
>
>
>
Submitted By: Brian Cheeseman <briancheeseman at aapt dot net dot au> (BCheese)
Date: 2007-07-20
Initial Package Version: 0.9.29
Description: This enables the variable error_print_progname within uClibc 0.9.28
which is required by some packages.
--- uClibc-0.9.29/libc/misc/error/error.c.orig 2007-07-19 20:44:03 +0000
+++ uClibc-0.9.29/libc/misc/error/error.c 2007-07-19 20:44:16 +0000
@@ -47,7 +47,7 @@
/* If NULL, error will flush stdout, then print on stderr the program
name, a colon and a space. Otherwise, error will call this
function without parameters instead. */
-/* void (*error_print_progname) (void) = NULL; */
+void (*error_print_progname) (void) = NULL;
extern __typeof(error) __error attribute_hidden;
void __error (int status, int errnum, const char *message, ...)
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
