Re: mips toolchain on macos

[Titus von Boxberg <titus at v9g dot de>]

Am 18.08.2011 um 16:19 schrieb Guylhem Aznar:

> *$ find crosstool-ng|grep install_headers
> crosstool-ng/.build/mips-osx-linux-uclibc/build/build-libc/extra/scripts/install_headers.sh
> crosstool-ng/.build/mips-osx-linux-uclibc/build/build-libc-headers/extra/scripts/install_headers.sh
> crosstool-ng/.build/src/uClibc-0.9.30/extra/scripts/install_headers.sh
> *$ find crosstool-ng|grep install_headers|xargs grep find
> crosstool-ng/.build/mips-osx-linux-uclibc/build/build-libc/extra/scripts/install_headers.sh:find
> . ! -name '.' -a ! -path '*/.*' | sed -e 's/^\.\///' -e '/^config\//d'
> \
> crosstool-ng/.build/mips-osx-linux-uclibc/build/build-libc-headers/extra/scripts/install_headers.sh:find
> . ! -name '.' -a ! -path '*/.*' | sed -e 's/^\.\///' -e '/^config\//d'
> \
> crosstool-ng/.build/src/uClibc-0.9.30/extra/scripts/install_headers.sh:find
> . ! -name '.' -a ! -path '*/.*' | sed -e 's/^\.\///' -e '/^config\//d'
> \
> 
I cannot spot a find without a path here.
I assume that the find is in uclibc's build system, since I cannot
grep it in ct-ng's own build scripts.

>> If it's a script within the build system of uclibc then you should
>> prepare a patch file for the version of eglibc.
> 
> You are the official OSX maintainer from crosstools-ng. I'd rather you
> made the patch
wow, didn't know that. thanks for the promotion!
But I think that preparing the patch can well be delegated to the users ;-)
Once you can clearly identify the file where the find in question is located in
it should not be too difficult.
There is a tutorial for hg in docs/C*.txt, and preparing a patch file
for uClibc (should the find be in it's files) is easy if you look at
the already existing patch files in crosstool-ng.

> - alternatively you could recommand installing gnu find
> in your documentation? That might be a safer choice, in case such
> linuxisms are used elsewhere.
No. That's not the way I'd go for such basic tools such as find etc.
I'd also regard the possibility to omit the path for find a severe
design flaw of the GNU software, and software that exploits this as buggy.

Regards
Titus


--
For unsubscribe information see http://sourceware.org/lists.html#faq