[bug #35340] dbuskit fails in configure when using clang and --non-fragile-abi

[Sebastian Reitenbach]

URL:
  <http://savannah.gnu.org/bugs/?35340>

                 Summary: dbuskit fails in configure when using clang and
--non-fragile-abi
                 Project: GNUstep
            Submitted by: buzzdee
            Submitted on: Fr 20 Jan 2012 11:52:52 GMT
                Category: Libraries
                Severity: 3 - Normal
              Item Group: Installation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

having the following in the environment:

CC="clang" CPP="clang -E" OPTFLAG="${CFLAGS}" LD="clang"

and gnustep-make is configured with with non-fragile-abi, then 
configure breaks here:

configure: WARNING: unrecognized options: --enable-debug, --disable-strip,
--disable-silent-rules
configure: loading site script /home/ports/infrastructure/db/config.site
checking build system type... i386-unknown-openbsd5.0
checking host system type... i386-unknown-openbsd5.0
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... (cached) o
checking whether we are using the GNU C compiler... (cached) yes
checking whether clang accepts -g... (cached) yes
checking for clang option to accept ISO C89... none needed
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by clang... clang
checking if the linker (clang) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... (cached) 131072
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking for clang option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... match_pattern
/lib[^/]+(\.so\.[0-9]+\.[0-9]+|\.so|_pic\.a)$
checking for ar... (cached) ar
checking for strip... (cached) strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from clang object... ok
checking how to run the C preprocessor... clang -E
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking for dlfcn.h... (cached) yes
checking for objdir... .libs
checking if clang supports -fno-rtti -fno-exceptions... yes
checking for clang option to produce PIC... -fPIC -DPIC
checking if clang PIC flag -fPIC -DPIC works... yes
checking if clang static flag -static works... yes
checking if clang supports -c -o file.o... yes
checking if clang supports -c -o file.o... (cached) yes
checking whether the clang linker (clang) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... openbsd5.0 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking target system type... i386-unknown-openbsd5.0
checking whether we are using the GNU C compiler... (cached) yes
checking whether clang accepts -g... (cached) yes
checking for clang option to accept ISO C89... (cached) none needed
checking how to run the C preprocessor... clang -E
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether the compiler supports atomic operations... yes
checking for DBUS... yes
checking whether the compiler supports -Wdeclaration-after-statement...
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... yes
checking whether gcc accepts -g... yes
yes
checking how to run the Objective C preprocessor... /lib/cpp
configure: error: in `/home/ports/pobj/gnustep-dbuskit-0.1/dbuskit-0.1':
configure: error: Objective C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
*** Error code 1


reason is: after checking for gcc and finding clang, it later checks for an
objective-c compiler, and takes it from OBJC environment variable. All other
softwares I have in the OpenBSD ports tree just take the info from the CC
environment variable.

maybe this could be done for dbuskit too?




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?35340>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/