----- 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.
