Re: armv4t-crosstool-linux-gnueabi problems

["Martin Guy" <martinwguy at gmail dot com>]

27 Jun 2006 09:37:50 UT, herwig@gdsys.de <herwig@gdsys.de> wrote:
> desperately in need for a NPTL-enabled Linux/glibc

Hi! I'm forwarding your request to the crossgcc list; I haven't seen
this exact problem, but someone else might recognise the symptoms. It
seems stupid of me to ask "is the execute permission bit set on the
dropbear executable, and on /, /usr and /usr/sbin", but normally
shared-ilbrary problems result in "File not found".

   M

---- rest of forwarded message ---

my coworker and I came across your prebuild toolchain for the armv4t.
After hours of testing different kernel configurations (EABI is
switched on) with the new toolchain, we found out, that we can start
our busybox only if we link it statically. Now that busybox starts,
there is still a problem starting any dynamically linked executable.
The output is always the same:
> ---
> usb 1-1: new full speed USB device using lh7a404-ohci and address 2
> usb 1-1: configuration #1 chosen from 1 choice
> eth1: register 'asix' at usb-lh7a404-1, DLink DUB-E100 USB Ethernet, 00:80:c8:38:07:00
> IP-Config: Complete:
>       device=eth1, addr=10.3.0.52, mask=255.255.0.0, gw=255.255.255.255,
>      host=catcenter_eabi, domain=, nis-domain=(none),
>      bootserver=10.3.0.1, rootserver=10.3.0.1, rootpath=
> Looking up port of RPC 100003/2 on 10.3.0.1
> Looking up port of RPC 100005/1 on 10.3.0.1
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 88K
> init started:  BusyBox v1.1.0 (2006.06.27-07:48+0000) multi-call binary
>
> Please press Enter to activate this console.
> Starting pid 32, console /dev/ttyAM1: '/bin/sh'
>
>
> BusyBox v1.1.0 (2006.06.27-07:48+0000) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> ~ # dropbear
> -sh: dropbear: Permission denied
> ~ # uname -a
> Linux catcenter_eabi 2.6.16 #49 PREEMPT Tue Jun 27 10:53:51 CEST 2006 armv4tl unknown
> ~ #
> ---
>
> I've compiled a static strace with the arm-eabi.patch and its output comes here:
>
> ---
> execve("/usr/sbin/dropbear", ["dropbear"], ["USER=root", "OLDPWD=/usr/sbin", "HOME=/", "TERM=vt102", "PATH=/usr/bin:/bin:/usr/sbin:/sb"..., "SHELL=/bin/sh", "PWD=/home"]) = -1 EACCES (Permission denied)
> dup(2)                                  = 3
> fcntl64(3, F_GETFL)                     = 0x2 (flags O_RDWR)
> fstat64(3, {st_dev=makedev(0, 11), st_ino=1879786051, st_mode=S_IFCHR|0644, st_nlink=1, st_uid=1012, st_gid=1012, st_blksize=4096, st_blocks=0, st_rdev=makedev(204, 17), st_atime=2006/06/27-07:51:20, st_mtime=2005/10/12-14:07:19, st_ctime=2006/06/27-07:51:20}) = 0
> ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x1500, c_oflags=0x5, c_cflags=0x1cb2, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000
> _llseek(3, 0, 0xbea638e8, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
> write(3, "strace: exec: Permission denied\n", 32) = 32
> close(3)                                = 0
> munmap(0x40000000, 4096)                = 0
> io_submit(0x1, 0x1, 0 <unfinished ... exit status 1>
> ---
>
> We did not have any problems with our project compiled with a non-eabi gcc-3.4.5-glibc-2.3.6 toolchain apart from the SEGV-->SIGKILL problem with linuxthreads and kernel 2.6.
>
> You seem to be one of the few people who may have a clue about this armv4/eabi phenomenon or whatever this might be. If you have an idea, could you please let us know about it? :) Or perhaps you know a document or person that could help us...
>
> I suppose you will need further information, but I did not want to send you too much spam in case this is off-topic for you.
>
>
> Thanks in advance
>
> Björn
>
> ------------
> Björn Herwig
> Guntermann & Drunck GmbH
> Abteilung: F & E
> Dortmunder Str. 4a
>
> D-57234 Wilnsdorf
> Germany
>
> Tel.: +49 (0) 2739 8901-100
> Fax.: +49 (0) 2739 8901-120
> E-Mail.: herwig@gdsys.de

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