Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12 April 2016 at 14:28, Kai Ruottu <kai.ruottu@xxxxxxxxxxx> wrote:
> 12.4.2016, 16:14, Kai Ruottu kirjoitti:
>>
>> But I cannot "grok" how the bare "arm-eabi" object
>> format or the generic newlib C library could provide that required
>> "operating system"
>> for threads.
>>
>
> What newlib can do is to provide code which works when used in threads :
>
> https://en.wikipedia.org/wiki/Thread_safety
>
> From my own "low-level" programming time, terms like "re-entrant" came quite
> familiar :)


Libstdc++ doesn't care about OS support for threads, it cares about an
available API for threads, such as Pthreads.

newlib includes a <pthread.h> file that implements the Pthreads API,
and so you can configure libstdc++ with --enable-threads=posix when
using newlib (although I assume this requires that newlib itself has
been configured with Pthreads support enabled).

So I stand by my assertion that using newlib does not necessarily
imply that the default thread model is "single".



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux