RE: nanosleep configure check in Ubuntu precise
- Douglas Torrance dtorra...@monmouthcollege.edu a écrit : Thanks again for looking at this, Christophe! I removed -DGLOBAL_DEFAULTS_SUBDIR from CFLAGS and there were no changes. As requested, I've attached the diff between the non-working configure and a working configure from Ubuntu 14.10. It looks like that 6299as_VAR snuck in on this line (1097 in the diff): CFLAGS=$CFLAGS $$as_VAR Hi, I have proposed a patch to prevent this kind of improper stuff from being generated, so at least we won't get a corrupted 'configure' script. On the other hand, it will not make your Ubuntu Precise compilation work, it will make it stop before making garbage. If it is possible, could I propose you this methodology instead: - use make dist in your recent working env - use that generated package to compile on your test-setup, skipping the then unnecessary 'autogen.sh' step. (My apologies for top posting. My employer appears to have changed some Exchange settings and I'm stuck using webmail...) From: Christophe [christophe.cu...@free.fr] Sent: Saturday, December 13, 2014 9:43 AM To: wmaker-dev@lists.windowmaker.org Subject: Re: nanosleep configure check in Ubuntu precise - Douglas Torrance dtorra...@monmouthcollege.edu a écrit : On 12/12/2014 06:31 PM, Christophe wrote: Hi according to your log file, there are way more things that just that which seems to not be properly detected. Would you happen to have the config.log to share? I was able to reproduce the failed build locally with pbuilder, and have attached the config.log. Thanks, it helps but also confuses a little bit more... There is this, coming back too frequently: command-line:0:25: warning: missing terminating character [enabled by default] command-line:0:25: error: missing terminating character [-Werror] May you give a try without the -DGLOBAL_DEFAULTS_SUBDIR to see if it is only a quoting issue? (on a side note, conceptually it should be in CPPFLAGS, but it is clearly not the problem here). There is, on the other end, also this kind of message later: gcc: error: 6299as_VAR: No such file or directory which looks legit, as the command line is reported to be: configure:12999: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DGLOBAL_DEFAULTS_SUBDIR=\GNUstep/Defaults\ 6299as_VAR -pedantic -Werror -Wno-deprecated -D_FORTIFY_SOURCE=2 -DNDEBUG conftest.c 5 It looks like the command line is being polluted somewhere in the process. Could I suspect a problem of version with autotools? 2.68 does not sound that old... It could be interesting to make a diff between your usual 'configure' that works and the one generated in this build process. I would suggest also that instead of running 'autogen.sh' in your build environment, you run instead 'make dist' in your usual dev environment and then use that package for the build, if that is not opposite to Ubuntu's build methods. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
RE: nanosleep configure check in Ubuntu precise
Thanks again for looking at this, Christophe!
I removed -DGLOBAL_DEFAULTS_SUBDIR from CFLAGS and there were no changes.
As requested, I've attached the diff between the non-working configure and a
working configure from Ubuntu 14.10.
It looks like that 6299as_VAR snuck in on this line (1097 in the diff):
CFLAGS=$CFLAGS $$as_VAR
(My apologies for top posting. My employer appears to have changed some
Exchange settings and I'm stuck using webmail...)
From: Christophe [christophe.cu...@free.fr]
Sent: Saturday, December 13, 2014 9:43 AM
To: wmaker-dev@lists.windowmaker.org
Subject: Re: nanosleep configure check in Ubuntu precise
- Douglas Torrance dtorra...@monmouthcollege.edu a écrit :
On 12/12/2014 06:31 PM, Christophe wrote:
Hi according to your log file, there are way more things that just that
which seems to not be properly detected. Would you happen to have the
config.log to share?
I was able to reproduce the failed build locally with pbuilder, and have
attached the config.log.
Thanks, it helps but also confuses a little bit more...
There is this, coming back too frequently:
command-line:0:25: warning: missing terminating character [enabled by
default]
command-line:0:25: error: missing terminating character [-Werror]
May you give a try without the -DGLOBAL_DEFAULTS_SUBDIR to see if it is only
a quoting issue? (on a side note, conceptually it should be in CPPFLAGS, but it
is clearly not the problem here).
There is, on the other end, also this kind of message later:
gcc: error: 6299as_VAR: No such file or directory
which looks legit, as the command line is reported to be:
configure:12999: gcc -c -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall
-DGLOBAL_DEFAULTS_SUBDIR=\GNUstep/Defaults\ 6299as_VAR -pedantic -Werror
-Wno-deprecated -D_FORTIFY_SOURCE=2 -DNDEBUG conftest.c 5
It looks like the command line is being polluted somewhere in the process.
Could I suspect a problem of version with autotools? 2.68 does not sound that
old...
It could be interesting to make a diff between your usual 'configure' that
works and the one generated in this build process.
I would suggest also that instead of running 'autogen.sh' in your build
environment, you run instead 'make dist' in your usual dev environment and then
use that package for the build, if that is not opposite to Ubuntu's build
methods.
--
To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
--- configure-precise 2014-12-13 16:23:22.402348498 -0600
+++ configure-utopic 2014-12-13 16:32:58.175387006 -0600
@@ -1,11 +1,9 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.68 for WindowMaker 0.95.6+20141210.
+# Generated by GNU Autoconf 2.69 for WindowMaker 0.95.6+20141210.
#
#
-# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
-# 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
-# Foundation, Inc.
+# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
#
#
# This configure script is free software; the Free Software Foundation
@@ -134,6 +132,31 @@ export LANGUAGE
# CDPATH.
(unset CDPATH) /dev/null 21 unset CDPATH
+# Use a proper internal environment variable to ensure we don't fall
+ # into an infinite loop, continuously re-executing ourselves.
+ if test x${_as_can_reexec} != xno test x$CONFIG_SHELL != x; then
+_as_can_reexec=no; export _as_can_reexec;
+# We cannot yet assume a decent shell, so we have to provide a
+# neutralization value for shells without unset; and this also
+# works around shells that cannot unset nonexistent variables.
+# Preserve -v and -x to the replacement shell.
+BASH_ENV=/dev/null
+ENV=/dev/null
+(unset BASH_ENV) /dev/null 21 unset BASH_ENV ENV
+case $- in #
+ *v*x* | *x*v* ) as_opts=-vx ;;
+ *v* ) as_opts=-v ;;
+ *x* ) as_opts=-x ;;
+ * ) as_opts= ;;
+esac
+exec $CONFIG_SHELL $as_opts $as_myself ${1+$@}
+# Admittedly, this is quite paranoid, since all the known shells bail
+# out after a failed `exec'.
+$as_echo $0: could not re-execute with $CONFIG_SHELL 2
+as_fn_exit 255
+ fi
+ # We don't want this to propagate to other subprocesses.
+ { _as_can_reexec=; unset _as_can_reexec;}
if test x$CONFIG_SHELL = x; then
as_bourne_compatible=if test -n \\${ZSH_VERSION+set}\ (emulate sh) /dev/null 21; then :
emulate sh
@@ -167,7 +190,8 @@ if ( set x; as_fn_ret_success y test
else
exitcode=1; echo positional parameters were not saved.
fi
-test x\$exitcode = x0 || exit 1
+test x\$exitcode = x0 || exit 1
+test -x / || exit 1
as_suggested= as_lineno_1=;as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested as_lineno_1a=\$LINENO
as_lineno_2=;as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested as_lineno_2a=\$LINENO
eval 'test \x\$as_lineno_1'\$as_run'\ != \x\$as_lineno_2'\$as_run
Re : nanosleep configure check in Ubuntu precise
- Douglas Torrance dtorra...@monmouthcollege.edu a écrit : Commit ff8fc10 introduced a check in the configure script for the nanosleep function. I maintain a Launchpad ppa which automatically builds Window Maker packages from next for Ubuntu. Everything builds just fine, except for the Precise Pangolin (Ubuntu 12.04) package, which results in an error: configure: error: function 'nanosleep' not found, please report to wmaker-dev@lists.windowmaker.org The full build log is available at [1]. Any ideas on what might be happening? Hi according to your log file, there are way more things that just that which seems to not be properly detected. Would you happen to have the config.log to share? Thanks! Doug [1] https://launchpadlibrarian.net/192491416/buildlog_ubuntu-precise-amd64.wmaker_0.95.6%2B20141210-0ppa20141208~ubuntu12.04.1_FAILEDTOBUILD.txt.gz -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
Re: nanosleep configure check in Ubuntu precise
On 12/12/2014 06:31 PM, Christophe wrote: Hi according to your log file, there are way more things that just that which seems to not be properly detected. Would you happen to have the config.log to share? I was able to reproduce the failed build locally with pbuilder, and have attached the config.log. Doug This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by WindowMaker configure 0.95.6+20141210, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure --prefix=/usr --mandir=/usr/share/man --includedir=/usr/include --sysconfdir=/etc --datadir=/usr/share --with-nlsdir=/usr/share/locale --with-pixmapdir=/usr/include/X11/pixmaps --with-gnustepdir=/usr/share/lib/GNUstep/System --disable-locale --enable-modelock --enable-xinerama CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DGLOBAL_DEFAULTS_SUBDIR=\GNUstep/Defaults\ CPPFLAGS=-D_FORTIFY_SOURCE=2 CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security FFLAGS=-g -O2 LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro ## - ## ## Platform. ## ## - ## hostname = gloria uname -m = x86_64 uname -r = 3.16.0-24-generic uname -s = Linux uname -v = #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin ## --- ## ## Core tests. ## ## --- ## configure:2479: checking for a BSD-compatible install configure:2547: result: /usr/bin/install -c configure:2558: checking whether build environment is sane configure:2608: result: yes configure:2749: checking for a thread-safe mkdir -p configure:2788: result: /bin/mkdir -p configure:2801: checking for gawk configure:2831: result: no configure:2801: checking for mawk configure:2817: found /usr/bin/mawk configure:2828: result: mawk configure:2839: checking whether make sets $(MAKE) configure:2861: result: yes configure:2890: checking whether make supports nested variables configure:2907: result: yes configure:3049: checking for gcc configure:3065: found /usr/bin/gcc configure:3076: result: gcc configure:3305: checking for C compiler version configure:3314: gcc --version 5 gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3325: $? = 0 configure:3314: gcc -v 5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) configure:3325: $? = 0 configure:3314: gcc -V 5 gcc: error: unrecognized option '-V' gcc: fatal error: no input files compilation terminated. configure:3325: $? = 4 configure:3314: gcc -qversion 5 gcc: error: unrecognized option '-qversion' gcc: fatal error: no input files compilation terminated. configure:3325: $? = 4 configure:3345: checking whether the C compiler works configure:3367: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DGLOBAL_DEFAULTS_SUBDIR=\GNUstep/Defaults\ -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro conftest.c 5 command-line:0:25: warning: missing terminating character [enabled by default] configure:3371: $? = 0 configure:3419: result: yes configure:3422: checking for C compiler default output file name configure:3424: result: a.out configure:3430: checking for suffix of executables configure:3437: gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -DGLOBAL_DEFAULTS_SUBDIR=\GNUstep/Defaults\ -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro conftest.c 5 command-line:0:25:
