search for: __extensions__

...this is wrong, not arguing there. > So in case of that bug, the tarball > was created with Python 2. And while patches #3, #4, and #5 should fix > the majority of the visible cases of this issue, there are still > potential issues: config.h defines a series of macros (_GNU_SOURCE, > __EXTENSIONS__, etc) that change the way things are built, and strictly > depend on the platform. > > > Could we instead defend these with #ifdef HAVE_CONFIG_H? That way the > > header shouldn't be used for PyPi and shouldn't need to be bundled (so > > patch #7 would be OK). >...

On Thu, Jan 09, 2020 at 06:37:49PM +0100, Pino Toscano wrote: > There is nothing in the Python bindings that require results from > configure, and gnulib is not used already. > --- > generator/python.ml | 6 ------ > python/handle.c | 2 -- > 2 files changed, 8 deletions(-) I guess the motivation is because we cannot create this header correctly from PyPi so it'll be

...VISIBILITY_ATTRIBUTE 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | #define __EXTENSIONS__ 1 | #define _ALL_SOURCE 1 | #define _GNU_SOURCE 1 | #define _POSIX_PTHREAD_SEMANTICS 1 | #define _TANDEM_SOURCE 1 | #define HAVE_DLFCN_H 1 | #define LT_OBJDIR ".libs/" | #define HAVE_LIBM 1 | #define HAVE_LIBDL 1 | #define HAVE_READLINE_HISTORY_H 1 | #define HAVE_READLINE_READLINE_H 1 | #...

...g was configured from the libguestfs build that created it. So in case of that bug, the tarball was created with Python 2. And while patches #3, #4, and #5 should fix the majority of the visible cases of this issue, there are still potential issues: config.h defines a series of macros (_GNU_SOURCE, __EXTENSIONS__, etc) that change the way things are built, and strictly depend on the platform. > Could we instead defend these with #ifdef HAVE_CONFIG_H? That way the > header shouldn't be used for PyPi and shouldn't need to be bundled (so > patch #7 would be OK). I'll reverse the questio...

...ine HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_DLFCN_H 1 | #ifdef __cplusplus | #include <stdlib.h> | #endif | #define _XOPEN_SOURCE 600 | #define __EXTENSIONS__ 1 | #define _GNU_SOURCE | #define STDC_HEADERS 1 | #define WORDS_BIGENDIAN 1 | /* end confdefs.h. */ | #include <stdio.h> | #if HAVE_SYS_TYPES_H | # include <sys/types.h> | #endif | #if HAVE_SYS_STAT_H | # include <sys/stat.h> | #endif | #if STDC_HEADERS | # include <stdlib.h&...

.../usr/include/sys/tiuser.h:51: warning: data definition has no type or storage class and this goes on for a little while. The "guilty" part of /usr/include/sys/tpicommon.h looks like this: /* * The opthdr types are now t_uscalar_t - inspired by XTI */ #if !defined(_XPG4_2) || defined(__EXTENSIONS__) struct opthdr { t_uscalar_t level; /* protocol level affected */ t_uscalar_t name; /* option to modify */ t_uscalar_t len; /* length of option value */ }; Is there anything I can do to get around this? Ron ---------------------+------------------------...

...ot found. I specify macros are LD_LIBRARY_PATH=$LD_LIBRARY_PATH/path_of_nettle_2.4/lib and "PATH:path_of_nettle_2.4/bin/:$PATH" on ~/.bashrc . Why show an errors for requiring libnettle version 2.4? VIM command line for show data in config.log. it's show as below. 739 | #define __EXTENSIONS__ 1 740 | #define _ALL_SOURCE 1 741 | #define _DARWIN_C_SOURCE 1 742 | #define _GNU_SOURCE 1 743 | #define _POSIX_PTHREAD_SEMANTICS 1 744 | #define _TANDEM_SOURCE 1 745 | #define HAVE_FSEEKO 1 746 | #define STDC_HEADERS 1 747 | /* end confdefs.h. */ 748 | #include <nettle/ripemd160.h>...

With gcc 3.2.3 on SunOS 5.8 and R 1.7.0, configure fails for me unless I set LDFLAGS ( LDFLAGS=-L/apps/asd/unix/gnu/gcc/3.2.3/SunOS5.8/lib ). With that set it appears that configure succeeds (i.e. no error messages on the console), but config.log contains messages configure:4099: checking for gcc option to accept ANSI C configure:4160: gcc -c -g -O2 -I/usr/local/include conftest.c >&5

I am trying to compile tinc on a android tablet. When i do ./configure it does not run because the shell in not /bin/sh but /data/data/com.termux/files/usr/bin/sh. $ which sh /data/data/com.termux/files/usr/bin/sh What do i have to change to make this part of the compile work ? Greetings from Amsterdam, Perry

...nd unsigned make: *** [regress/netcat] Error 1 I guess that is what you meant about structure differences. It looks like on Solaris I can choose between msg_accrights* or msg_control*/msg_flags in struct msghdr. The latter requires _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED which will also require __EXTENSIONS__ or other useful things suddenly go away. Building openssh with CC="gcc -D__EXTENSIONS__ -D_XOPEN_SOURCE -D_XOPEN_SOURCE_EXTENDED" is possible (tested only on Solaris 9 so far). Unfortunately now that I can finally run the testsuite I see ssh-keygen dumps core in keygen-change.sh but al...

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... gcc checking whether we are using the GNU Objective C compiler... no checking whether gcc accepts -g... no checking for Objective C++ compiler... trying some possibilities checking whether g++ can compile ObjC++... no checking whether can compile ObjC++... no no working...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 configure:17280: result: no configure:17300: checking for mblen configure:17356: gcc -o conftest -O3 -m64 -mtune=native -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset

On Tue, 24 Feb 2015, Tom G. Christensen wrote: > I've switched to HEAD in the git repo and it now builds on Solaris > 2.6, 7, 8 and 9 but the testsuite still cannot be built due to the > missing <err.h>. > > I noticed one of the changes was about HOST_NAME_MAX but I don't > think that change addresses the real issue on at least these old > Solaris systems. It

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc acc...

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed check...

Hi, I am working on an old Unix system, UNIX SVR4 MP-RAS, running a Teradata database. Due to the age of the system (notably the C compiler, which won't handle v3 source code), I have built Samba 2.2.12 I want to use this to share Unix directories out to XP clients as network drives, for read-write access, keeping the file ownership as strict unix users. This all works fine, except for

...g for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... gcc checking whether we are using the GNU Objective C compiler... no checking whether gcc accepts -g... no checking for Objective C++ compiler... trying some possibilities checking whether g++ can compile ObjC++... yes g++ checking for a sed that does not truncate...

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking how to run the C preprocessor... gcc -std=gnu99 -E checking for function prototypes... yes checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for...

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking how to run the C preprocessor... gcc -std=gnu99 -E checking for function prototypes... yes checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for...

...checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking how to run the C preprocessor... gcc -std=gnu99 -E checking for function prototypes... yes checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for...