[uClibc]Question concerning 'mipsel' support...

Erik Andersen andersen at codepoet.org
Thu Jan 31 18:22:48 UTC 2002


On Thu Jan 31, 2002 at 11:59:27AM -0600, Steven J. Hill wrote:
> > 
> I did a grep through the entire tree (latest snapshot) for 'syscalls'
> and found only the file 'libc/sysdeps/linux/sh/bits/syscalls.h' exists
> and that none of the makefiles in any of the other architectures create
> 'bits/syscalls.h'. What am I missing here? The only file that gets
> generated is 'bits/syscall.h'.

You are clearly missing something, since in _my_ tree and the
tree in CVS there are plenty of syscalls.h files:
    $ find -name syscalls.h
    ./libc/sysdeps/linux/arm/bits/syscalls.h
    ./libc/sysdeps/linux/i386/bits/syscalls.h
    ./libc/sysdeps/linux/m68k/bits/syscalls.h
    ./libc/sysdeps/linux/powerpc/bits/syscalls.h
    ./libc/sysdeps/linux/sh/bits/syscalls.h
    ./libc/sysdeps/linux/v850/bits/syscalls.h

include/bits/syscalls.h is the arch specific implementation of
the _syscall[0-6] macros.

include/bits/syscall.h is generated at compile time by the
toplevel uClibc/Makefile headers target, which as its very last
task calls
    $(MAKE) -C libc/sysdeps/linux/$(TARGET_ARCH) headers

In the various libc/sysdeps/linux/$(TARGET_ARCH)/Makefile
files, the headers target is supposed to call
    @(TOPDIR=$(TOPDIR) CC=$(CC) /bin/sh $(TOPDIR)/extra/scripts/gen_bits_syscall_h.sh > bits/syscall.h )

which is how include/bits/syscall.h gets generated.  It looks
to me like libc/sysdeps/linux/mipsel/Makefile is doing this 
correctly.  Are you looking at some other source tree?

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



More information about the uClibc mailing list