summaryrefslogtreecommitdiff
path: root/gnu/dist/libstdc++/std/dcomplex.h
diff options
context:
space:
mode:
authortv <tv@NetBSD.org>2002-02-14 19:17:32 +0000
committertv <tv@NetBSD.org>2002-02-14 19:17:32 +0000
commita194e2ca32ab8644beda0b0194de71455497bbb6 (patch)
treedabd37f13231c5f93fa3ecbcfd61501edc946311 /gnu/dist/libstdc++/std/dcomplex.h
parentc6510076433aebd05fce3ec1f6f1b7c33166e7db (diff)
Bomb if NBUILDJOBS is set, as it is badly broken in some way (as described
in toolchain/14837). This is the root of some problems thought to be of different causes by users who forget to say that they are using "build.sh -j"....
Diffstat (limited to 'gnu/dist/libstdc++/std/dcomplex.h')
0 files changed, 0 insertions, 0 deletions
d than the previous where components had to be tagged in the Makefile as modules (and if they weren't, things broke. and vice versa). 2009-09-13binutils 2.19 has changed the old behaviour of defining __start_SECTNAMEpooka for orphaned sections to using PROVIDE. What this means is that unless a rump component internally references that symbol, it will not be included in the component shared library, and hence cannot be referenced when the component is loaded. Add a workaround which works both with 2.16 and 2.19: force a reference to the __start symbol internally and hence retain it in the resulting library. 2009-05-28Use a bunch of weak symbols to determine which network componentspooka are present. This works in userspace as opposed relying in link sets, which fail miserably. Later, when the networking stack becomes modularized, we can move to a dynamic scheme like with file systems. Also, this change allows us to do proper autoconfig, namely attach the loopback interface iff it is present. 2009-01-26Convert compile-time SOCKIN_NOTHREADS into runtime rump_threads check.pooka 2008-10-02Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,pooka which delegates the work to host kernel sockets. This does not run the entire kernel TCP/IP stack in userspace and therefore does not require the ability to send or receive raw packets. This implies that root priviledges are not required. As already said above, only supports UDPv4 for now. Extending should be easy.