Displaying 12 results from an estimated 12 matches for "__use_gnu".
2005 Nov 21
5
[Bug 1122] __USE_GNU is internal glibc macro and should not be used
http://bugzilla.mindrot.org/show_bug.cgi?id=1122
Summary: __USE_GNU is internal glibc macro and should not be used
Product: Portable OpenSSH
Version: 4.2p1
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Miscellaneous
AssignedTo: bitbucket...
2002 Sep 13
2
[LLVMdev] Linux-x86 Compatability
ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a
Solarisism. Luckily, getCurrentExecutablePath isn't being currently
used anywhere in lli.
ACTION: Wrap the method contents with #ifdef __sun__ ... #else return
""; #endif. If this functionality is actually desired, it would be more
portable to hack up main() to join getcwd() with basename(argv[0]) to
find the
2002 Sep 13
0
[LLVMdev] Linux-x86 Compatability
> ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a
> Solarisism. Luckily, getCurrentExecutablePath isn't being currently
> used anywhere in lli.
It looks like under my linux box, the dladdr prototype is wrapped with a
#ifdef __USE_GNU
option... If so, perhaps the write patch is to add -DGNU-SOURCES (or
whatever that option is) to the makefiles? Can you verify that this would
fix it?
Thanks again for the help!
-Chris
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/
2016 Dec 04
2
[Release-testers] 3.9.1-rc2 is ready for testing
...mic/GCCMM
ThreadSanitizer-x86_64 :: Linux/mutex_robust.cc
ThreadSanitizer-x86_64 :: Linux/mutex_robust2.cc
These fail to find pthread_mutexattr_getrobust while linking. pthread.h on
SLES11.3 defines pthread_mutexattr_getrobust and
pthread_mutexattr_getrobust_np (depending on options like __USE_GNU) but
libpthread contains only pthread_mutexattr_getrobust_np.
ThreadSanitizer-x86_64 :: thread_name2.cc
^^ glibc 2.11 doesn't include 'pthread_setname_np'.
libc++ :: std/depr/depr.c.headers/uchar_h.pass.cpp
^^ glibc doesn't get uchar until 2.16.
libc++ ::
std/diagno...
2007 Sep 04
1
CPAN error
...>
line 33.
Constant subroutine __USE_SVID undefined at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/features.ph line 20, <STDIN>
line 33.
Constant subroutine __USE_MISC undefined at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/features.ph line 21, <STDIN>
line 33.
Constant subroutine __USE_GNU undefined at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/features.ph line 22, <STDIN>
line 33.
Constant subroutine __USE_REENTRANT undefined at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/features.ph line 23, <STDIN>
line 33.
Constant subroutine _POSIX_SOURCE undefined at
/usr/lib/per...
2006 Feb 01
0
Announce: OpenSSH 4.3 released
...st on Solaris
#1097 - Cross-compile fixes.
#1096 - ssh-keygen broken on HPUX.
#1098 - $MAIL being set incorrectly for HPUX server login.
#1104 - Compile error on Tru64 Unix 4.0f
#1106 - Updated .spec file and startup for SuSE.
#1122 - Use _GNU_SOURCE define in favor of __USE_GNU, fixing
compilation problems on glibc 2.4
Thanks to everyone who has contributed patches, reported bugs or test
releases.
Checksums:
==========
- SHA1 (openssh-4.3.tar.gz) = 0cb66e56805d66b51511455423bab88aa58a1455
- SHA1 (openssh-4.3p1.tar.gz) = b1f379127829e7e820955b2825130edd1601...
2006 Feb 01
0
Announce: OpenSSH 4.3 released
...st on Solaris
#1097 - Cross-compile fixes.
#1096 - ssh-keygen broken on HPUX.
#1098 - $MAIL being set incorrectly for HPUX server login.
#1104 - Compile error on Tru64 Unix 4.0f
#1106 - Updated .spec file and startup for SuSE.
#1122 - Use _GNU_SOURCE define in favor of __USE_GNU, fixing
compilation problems on glibc 2.4
Thanks to everyone who has contributed patches, reported bugs or test
releases.
Checksums:
==========
- SHA1 (openssh-4.3.tar.gz) = 0cb66e56805d66b51511455423bab88aa58a1455
- SHA1 (openssh-4.3p1.tar.gz) = b1f379127829e7e820955b2825130edd1601...
2004 Oct 21
3
1.0-test51
http://dovecot.org/test/
This release is built with autoconf 2.59 and libtool 1.9. We'll see how
it works out :) The required changes were done by Matthias Andree.
- The last fix for connection hanging made IDLE use 100% CPU
- We don't use Maildir/.INBOX/ directory anymore, indexes are stored
in Maildir-root
- Don't crash with FETCH BODY[n.MIME]
- Changed %p (protocol)
2012 Feb 21
5
[LLVMdev] buildbot failure in LLVM on clang-x86_64-debian-fnt
...-file-name slib.c -mrelocation-model static -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu x86-64
-momit-leaf-frame-pointer -coverage-file Output/slib.ll -resource-dir
/home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/llvm.obj/Release+Asserts/bin/../lib/clang/3.1
-D __USE_MISC -D __USE_GNU -D __USE_SVID -D __USE_XOPEN_EXTENDED -D
__USE_XOPEN -D unix -D _GNU_SOURCE -D __STDC_LIMIT_MACROS -D NDEBUG -I
/home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/test-suite.obj/MultiSource/Applications/siod
-I /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/test-suite.src/MultiSource/Applicat...
2007 Jan 06
3
Re: [nut-commits] svn commit r708 - in trunk: . clients server
With the Ipv6 patch (r708), I get:
upsclient.c: In function `upscli_connect':
upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function)
upsclient.c:469: (Each undeclared identifier is reported only once
upsclient.c:469: for each function it appears in.)
Even if it doesn't break IPv4 support, it may break portability, as
IPv6 seems to require specific functions that are
2012 Feb 21
0
[LLVMdev] buildbot failure in LLVM on clang-x86_64-debian-fnt
...ation-model static -masm-verbose
> -mconstructor-aliases -munwind-tables -target-cpu x86-64
> -momit-leaf-frame-pointer -coverage-file Output/slib.ll -resource-dir
>
> /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/llvm.obj/Release+Asserts/bin/../lib/clang/3.1
> -D __USE_MISC -D __USE_GNU -D __USE_SVID -D __USE_XOPEN_EXTENDED -D
> __USE_XOPEN -D unix -D _GNU_SOURCE -D __STDC_LIMIT_MACROS -D NDEBUG -I
>
> /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/test-suite.obj/MultiSource/Applications/siod
> -I
> /home/baldrick/osuosl/slave/clang-x86_64-debian-fnt/test-suite...
2016 Dec 02
9
3.9.1-rc2 is ready for testing
Hi,
I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in
-rc1 before I could send out a release announcement, so I decided to merge
the fix and tag -rc2 to save some testing cycles.
We can always use more testers, so if you are interested in helping, let
me know.
Thanks,
Tom