Hi:
Now I am running buildroot under cygwin for building a
cross-toolchain and there are several problems, following is the one I
don't know how to walk around
After installing uclibc, uclibc.mk trying to cd to utils and compile
readelf.c for host machine, which includes link.h and other he
On Thu, Jun 04, 2009 at 03:28:53PM +0800, Amker.Cheng wrote:
>Hi:
>Now I am running buildroot under cygwin for building a
>cross-toolchain and there are several problems, following is the one I
>don't know how to walk around
>After installing uclibc, uclibc.mk trying to cd to utils and comp
i dont see any value in continuing to include/maintain our readelf.c. does
anyone actually care ?
-mike
signature.asc
Description: This is a digitally signed message part.
___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/list
the ldd & ldconfig seem to be very useful, But I didn't find any
description about readelf in FAQ,
I'm curious about the initial purpose of including readelf.c,
considering that it already in binutils.
Thanks
On Fri, Jun 5, 2009 at 12:29 PM, Mike Frysinger wrote:
> i dont see any value in continui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
> i dont see any value in continuing to include/maintain our readelf.c. does
> anyone actually care ?
> -mike
>
I agree with you. elfutils and/or binutils provide a well supported
tools. I vote for remove it too.
Carmelo
>
>
On Wed, Jun 17, 2009 at 1:59 AM, Carmelo AMOROSO wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mike Frysinger wrote:
>> i dont see any value in continuing to include/maintain our readelf.c. does
>> anyone actually care ?
>> -mike
>>
> I agree with you. elfutils and/or binutils provi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Khem Raj wrote:
> On Wed, Jun 17, 2009 at 1:59 AM, Carmelo AMOROSO
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Mike Frysinger wrote:
>>> i dont see any value in continuing to include/maintain our readelf.c. Â does
>>> anyone act