[Bug bootstrap/34474] New: find from BusyBox v1.2.2 does not support logical OR (-o argument)

[Bug bootstrap/34474] New: find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

/bin/sh ../../gcc/../move-if-change tmp-macro_list macro_list
echo timestamp > s-macro_list
rm -rf include; mkdir include
chmod a+rx include
if [ -d ../prev-gcc ]; then \
          cd ../prev-gcc && \
          make real-install-headers-tar DESTDIR=`pwd`/../gcc/ \
            libsubdir=. ; \
        else \
          (TARGET_MACHINE='armv5tejl-unknown-linux-gnu'; srcdir=`cd ../../gcc;
${PWDCMD-pwd}`; \
            SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \
            export TARGET_MACHINE srcdir SHELL MACRO_LIST && \
            cd ../build-armv5tejl-unknown-linux-gnu/fixincludes && \
            /bin/sh ./fixinc.sh ../../gcc/include \
              `echo /usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`  ); \
          rm -f include/syslimits.h; \
          if [ -f include/limits.h ]; then \
            mv include/limits.h include/syslimits.h; \
          else \
            cp ../../gcc/gsyslimits.h include/syslimits.h; \
          fi; \
        fi
Fixing headers into /scratch/gcc-4.2.2/objdir/gcc/include for
armv5tejl-unknown-linux-gnu target
Forbidden identifiers: linux unix 
Finding directories and links to directories
 Searching /usr/include/.
Making symbolic directory links
Fixing directory /usr/include into /scratch/gcc-4.2.2/objdir/gcc/include
BusyBox v1.2.2 (2007.03.26-11:07+0000) multi-call binary

Usage: find [PATH...] [EXPRESSION]

Search for files in a directory hierarchy.  The default PATH is
the current directory; default EXPRESSION is '-print'

EXPRESSION may consist of:
        -follow         Dereference symbolic links
        -name PATTERN   File name (leading directories removed) matches PATTERN
        -print          Print (default and assumed)
        -print0         Delimit output with null characters rather than
                        newlines
        -type X         Filetype matches X (where X is one of: f,d,l,b,c,...)
        -perm PERMS     Permissions match any of (+NNN); all of (-NNN);
                        or exactly (NNN)
        -mtime DAYS     Modified time is greater than (+N); less than (-N);
                        or exactly (N) days
        -mmin MINS      Modified time is greater than (+N); less than (-N);
                        or exactly (N) minutes
        -exec CMD       Execute CMD with all instances of {} replaced by the
                        files matching EXPRESSION

Cleaning up unneeded directories:
BusyBox v1.2.2 (2007.03.26-11:07+0000) multi-call binary

Usage: find [PATH...] [EXPRESSION]

Search for files in a directory hierarchy.  The default PATH is
the current directory; default EXPRESSION is '-print'

EXPRESSION may consist of:
        -follow         Dereference symbolic links
        -name PATTERN   File name (leading directories removed) matches PATTERN
        -print          Print (default and assumed)
        -print0         Delimit output with null characters rather than
                        newlines
        -type X         Filetype matches X (where X is one of: f,d,l,b,c,...)
        -perm PERMS     Permissions match any of (+NNN); all of (-NNN);
                        or exactly (NNN)
        -mtime DAYS     Modified time is greater than (+N); less than (-N);
                        or exactly (N) days
        -mmin MINS      Modified time is greater than (+N); less than (-N);
                        or exactly (N) minutes
        -exec CMD       Execute CMD with all instances of {} replaced by the
                        files matching EXPRESSION

fixincludes is done
chmod a+r include/syslimits.h
echo timestamp > stmp-fixinc
if [ -d include ] ; then true; else mkdir include; chmod a+rx include; fi
for file in .. ../../gcc/ginclude/decfloat.h ../../gcc/ginclude/float.h
../../gcc/ginclude/iso646.h ../../gcc/ginclude/stdarg.h
../../gcc/ginclude/stdbool.h ../../gcc/ginclude/stddef.h
../../gcc/ginclude/varargs.h ../../gcc/config/arm/mmintrin.h; do \
          if [ X$file != X.. ]; then \
            realfile=`echo $file | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            echo timestamp > include/$realfile; \
            rm -f include/$realfile; \
            cp $file include; \
            chmod a+r include/$realfile; \
          fi; \
        done
rm -f include/limits.h
cp xlimits.h include/limits.h
rm -f include/unwind.h
cp ../../gcc/unwind-generic.h include/unwind.h
chmod a+r include/limits.h
rm -f include/README
cp ../../gcc/../fixincludes/README-fixinc include/README
chmod a+r include/README
echo timestamp > stmp-int-hdrs
creating as
echo timestamp > stamp-as
creating collect-ld
echo timestamp > stamp-collect-ld
creating nm
echo timestamp > stamp-nm


After some debugging I found the problem is the -o argument doing logical OR.
Luckily, we can live with two separate executions of find as well. The attached
patch works for me.


-- 
           Summary: find from BusyBox v1.2.2 does not support logical OR (-o
                    argument)
           Product: gcc
           Version: 4.2.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mmokrejs at ribosome dot natur dot cuni dot cz


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #14763|0                           |1
        is obsolete|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[pinskia at gcc dot gnu dot org]

------- 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

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[aldot at gcc dot gnu dot org]

------- 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 you ENABLE_DESKTOP, but
that pulls in alot of big cruft so is nothing you want, generally.

Confirmed.


-- 

aldot at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldot at gcc dot gnu dot org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-12-15 12:49:28
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[steven at gcc dot gnu dot org]

------- 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 seems
like a highly unusual thing to do.  IMHO gcc should not have to be able to
build in such a limited environment as busybox.
3. Assuming you have good reasons for (2), is there anything stopping you from
just installing and using a POSIX conforming 'find(1)' command?

Either way, http://gcc.gnu.org/install/prerequisites.html should be updated to
reflect what we require to build gcc.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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 upgrade everything, it has only
32MB RAM and most importantly, has to run samba and sshd. Spot briefly over the
following pages.

http://martin.hinner.info/mybook/
http://ribosome.natur.cuni.cz/~mmokrejs/MyBookWorldII/
http://www.welped.com/2007/08/29/hacking-the-mybook-world-edition-into-a-php-powered-web-server/
http://chayden.net/mybook/
http://www.ismprofessional.net/pascucci/documenti/mybook/mybook-hacking-en.html
http://www.ismprofessional.net/pascucci/index.php/mybook-repository/
http://nihilisme.ca:8080/arm/
http://www.nabble.com/Re-3A-Arm-926ejs-questions-to10674608.html
http://www.dark-legion.org/en/ARM%20Holdings
http://www.arm.com/linux/ARM-Linux-Notes.pdf
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0157g/DDI0157.pdf


I don't see an issue why the bootstrap step would have to unnecessarily require
POSIX compliant find. Why? To have one exec() of find instead of two exec()
calls?

Regarding installing more apps. Well, the system has no iconv, no gettext, no
auto* tools, has only uClibc, has no libtool and e.g. to compile GNU file-4.21
I had to report two bugs to get it compiled, one of them is still not fixed.
So, no, I cannot upgrade apps and please do not require that unnecessarily. Who
cares about a bit more ugly fixinc.sh script which is used only during build
process? It does not affect resulting gcc compatibility/performance/features,
so why?
Yes, I really need to have as small as possible apps with minimum features and
I cannot even overwrite some shared libs and upgrade them (remember the
hardware has no KBD/VGA/MOUSE, serial console is a wild hack at 3.3V and so the
only sane way is to disassemble the box and mount drives elsewhere).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[aldot at gcc dot gnu dot org]

------- 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 this find isn't all that big:
$ ls -ln busybox && size busybox
-rwxr-xr-x 1 1000 1000 14492 2007-12-15 15:39 busybox
   text    data     bss     dec     hex filename
  12525     450      60   13035    32eb busybox


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[rguenth at gcc dot gnu dot org]

------- 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

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[aldot at gcc dot gnu dot org]

------- 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
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[mmokrejs at ribosome dot natur dot cuni dot cz]

------- 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 you have not heard what is exactly
required and why.

I have installed myself the whole busybox, filed a bug in it and still cannot
use stage1 compiler, but those are another 2 bugs in gcc-4.2.2.


-- 

mmokrejs at ribosome dot natur dot cuni dot cz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474

[Bug bootstrap/34474] find from BusyBox v1.2.2 does not support logical OR (-o argument)

[pinskia at gcc dot gnu dot org]

------- 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 not POSIX
compatible.  It is not common to find a non POSIX compatible find (or one that
does not support the find options).

The main reason why I don't want to see two finds is because find is actually
can be expensive.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34474