--- Comment #13 from pinskia at gcc dot gnu dot org 2007-12-16 12:58
---
Well it is we assume a lot of things are POSIX support so I don't see why we
have to document find here really. Yes we document we need a POSIX shell but
that is because a semi common target (Solaris)'s /bin/sh is
--- Comment #12 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-16 11:06 ---
Please update the docs first and update configure to check for at least some of
the required features. Users are not going to realize their utilities do not
conform to POSIX completely. And so far y
--- Comment #11 from aldot at gcc dot gnu dot org 2007-12-15 17:55 ---
Using programs that are required by SUSv3 in their complete feature set is
fine.
--
aldot at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #10 from rguenth at gcc dot gnu dot org 2007-12-15 16:31
---
Why do you need to bootstrap gcc on a small NAS box? Use a cross-compiler.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474
--- Comment #9 from aldot at gcc dot gnu dot org 2007-12-15 14:44 ---
Is suggest you get a current busybox-1.8.2 and just turn on the applets you
need, including DESKTOP support for find (which is a required feature according
to SUSv3, as steven mentioned).
With everything turned on thi
--- Comment #8 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-15 14:01 ---
The hardware is a Western Digital MyBookWorldII small NAS system, and it is
bundled with the linux and just these tools. Everybody is glad that at least a
working old gcc is available. We just can't
--- Comment #7 from steven at gcc dot gnu dot org 2007-12-15 13:25 ---
Three questions:
1. According to the 'find(1)' man pages, -o is specified in POSIX. Should GCC
support non-POSIX find commands? IMHO, no.
2. Why would you build in a busybox environment in the first place? This see
--- Comment #6 from aldot at gcc dot gnu dot org 2007-12-15 12:49 ---
(In reply to comment #4)
> None of these works:
>
> find . -type l -or -type d -print
> find . -type l OR -type d -print
> find . -type l or -type d -print
>
In current busybox (IIRC >= 1.6) these are available if yo
--- Comment #5 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-15 11:00 ---
Created an attachment (id=14767)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14767&action=view)
fixinc.in.patch
There was one more left ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?i
--- Comment #4 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-15 10:59 ---
None of these works:
find . -type l -or -type d -print
find . -type l OR -type d -print
find . -type l or -type d -print
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-12-15 03:49 ---
does changing -o to -or work? I would rather not do two finds.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474
--- Comment #2 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-15 03:31 ---
Created an attachment (id=14764)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14764&action=view)
fixinc.in.patch
--
mmokrejs at ribosome dot natur dot cuni dot cz changed:
What
--- Comment #1 from mmokrejs at ribosome dot natur dot cuni dot cz
2007-12-15 03:29 ---
Created an attachment (id=14763)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14763&action=view)
fixinc.in.patch
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474
13 matches
Mail list logo
