[Buildroot] [Bug 6230] New: Cannot compile gcc without threads

[Buildroot] [Bug 6230] New: Cannot compile gcc without threads

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

           Summary: Cannot compile gcc without threads
           Product: buildroot
           Version: 2012.08
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: a.nielsen at shikadi.net
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 4874
  --> https://bugs.busybox.net/attachment.cgi?id=4874
buildroot config to generate error

Since uClibc can't be compiled with threads (bug 6224), it must be compiled
without thread support.

However then gcc-final can't be compiled because it cannoy find pthread.h:

In file included from buildroot/toolchain/gcc-4.8.0/libgcc/gthr.h:148:0,
                 from buildroot/toolchain/gcc-4.8.0/libgcc/libgcov.c:31:
./gthr-default.h:35:21: fatal error: pthread.h: No such file or directory
 #include <pthread.h>
                     ^
compilation terminated.
make[3]: *** [_gcov.o] Error 1

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

--- Comment #1 from Adam Nielsen <a.nielsen@shikadi.net> 2013-05-04 05:13:21 UTC ---
Created attachment 4880
  --> https://bugs.busybox.net/attachment.cgi?id=4880
uClibc config, generated through buildroot

Add uClibc config for MMU-less with no thread support

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

--- Comment #2 from Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> 2014-02-13 13:51:49 UTC ---
I tried reproducing the problem, and get failures in uclibc, even with your
proposed .config:

In file included from libpthread/nptl/sysdeps/unix/sysv/linux/arm/fork.c:31:0:
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:61:17: error: 'fork'
undeclared here (not in a function)
 extern __typeof(fork) __libc_fork;
                 ^
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:63:1: error:
'__libc_fork' redeclared as different kind of symbol
 __libc_fork (void)
 ^
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:61:23: note: previous
declaration of '__libc_fork' was here
 extern __typeof(fork) __libc_fork;
                       ^
In file included from ./include/tls.h:6:0,
                 from libpthread/nptl/sysdeps/unix/sysv/linux/arm/fork.c:23:
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c: In function
'__libc_fork':
./libpthread/nptl/sysdeps/arm/tls.h:114:11: warning: implicit declaration of
function '__builtin_thread_pointer' [-Wimplicit-function-declaration]
  ((struct pthread *)__builtin_thread_pointer () - 1)
           ^
./include/bits/stdio-lock.h:42:22: note: in expansion of macro 'THREAD_SELF'
     void *__meself = THREAD_SELF;            \
                      ^
./include/bits/uClibc_mutex.h:96:50: note: in expansion of macro
'_IO_lock_lock'
 #define __UCLIBC_IO_MUTEX_LOCK_CANCEL_UNSAFE(M)  _IO_lock_lock(M)
                                                  ^
libpthread/nptl/sysdeps/unix/sysv/linux/arm/../fork.c:127:3: note: in expansion
of macro '__UCLIBC_IO_MUTEX_LOCK_CANCEL_UNSAFE'
   __UCLIBC_IO_MUTEX_LOCK_CANCEL_UNSAFE(_stdio_openlist_add_lock);
   ^


In any case, something is definitely broken here...

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads (uClibc-based)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Cannot compile gcc without  |Cannot compile gcc without
                   |threads                     |threads (uClibc-based)

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads (uClibc-based)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

--- Comment #3 from Gustavo Zacarias <gustavo@zacarias.com.ar> 2014-05-06 20:23:31 UTC ---
ARM nommu support is broken in general, there are several toolchain component
version restrictions that are currently unaccounted for.
Not only that but the toolchain build rules aren't properly done (the tuple is
wrong for example).

The problem is that Qemu doesn't emulate any usable (uc)linux hardware to test
with, and probably the most experienced devels who can help with this lack any
real nommu hardware that's tested with uclinux as a starting point.

Also it's probably more useful to work on modern ARM nommu support (Cortex M
series) but in general from some quick investigations i've done it's mostly
stuck with an oldish and heavily tweaked 2.6.33ish kernel.

So for ARM7TDMI who knows which kernel works properly.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads (uClibc-based)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2014-05-07 07:22:28 UTC ---
I recently got my hand on an EFM32 development board, which has a Cortex-M3
capable of running a mainline Linux kernel. Using this, I'm hoping to
progressively improve the support for ARM noMMU in Buildroot. Probably a topic
for the next release cycle, though.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 6230] Cannot compile gcc without threads (uClibc-based)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6230

Thomas De Schampheleire <patrickdepinguin@gmail.com> changed:

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

--- Comment #5 from Thomas De Schampheleire <patrickdepinguin@gmail.com> 2014-07-16 17:01:36 UTC ---
Support for ARM(7TDMI/720T/740T) has been dropped from buildroot with commit 
http://git.buildroot.org/buildroot/commit/?id=befab216a29927f598e0a3ba0b012f7e822bb235

Commit message is:
"    arch/arm: drop ARM(7TDMI/720T/740T) support

    The toolchain currently doesn't build for nommu ARM and is in need of
    serious work.
    Problem is there are no emulation targets and real ARM(7TDMI/720T/740T)
    hardware that's capable of running linux (enough memory, having a
    memory controller...) is VERY rare and uses very old versions to
    make it usable.

    The ARM nommu focus should go into Cortex M series processors that are
    obtainable at reasonable cost on modern hardware that has external
    memory controllers.
"

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.