Re: undefined reference to `__alloca'

2017-11-19 Thread Earnestly
On Sun, Nov 19, 2017 at 03:24:46PM -0500, Paul Smith wrote: > you will need to clean your Git workspace after you pull. Thank you, the new commits seem to have resolved all the issues I was having. And thank you for your patience while trying to diagnose this. Also no worries about the git worksp

Re: undefined reference to `__alloca'

2017-11-19 Thread Paul Smith
On Sat, 2017-11-18 at 23:02 +, Earnestly wrote: > > # if _GNU_GLOB_INTERFACE_VERSION >= GLOB_INTERFACE_VERSION > > > > and see if that works. > > Yes! This solves the issue and it also solves the __stat issues as > well. I pushed a change that should allow this to work properly. Note it ca

Re: undefined reference to `__alloca'

2017-11-18 Thread Earnestly
On Sat, Nov 18, 2017 at 04:48:12PM -0500, Paul Smith wrote: > One way to fix this would be to change the second #if line above to be: > > # if _GNU_GLOB_INTERFACE_VERSION >= GLOB_INTERFACE_VERSION > > and see if that works. Yes! This solves the issue and it also solves the __stat issues as well

Re: undefined reference to `__alloca'

2017-11-18 Thread Paul Smith
On Sat, 2017-11-18 at 21:19 +, Earnestly wrote: > [I've also found that `make update' is apparently subject to `make -j4' > race conditions resulting in errors like: > > wget: unable to resolve host address ‘cvs.savannah.gnu.org’ > make: *** [Makefile;1584: get-doc/fdl.texi] Error 4 I

Re: undefined reference to `__alloca'

2017-11-18 Thread Earnestly
On Sat, Nov 18, 2017 at 01:54:47PM -0500, Paul Smith wrote: > That change was made to make's internal usage of glob so that it works > with the latest glibc without errors: before that change if you tried > to use the system glibc glob and it had the newest glibc, make could > crash. Ah yes, I rem

Re: undefined reference to `__alloca'

2017-11-18 Thread Paul Smith
On Sat, 2017-11-18 at 18:35 +, Earnestly wrote: > > Also curious: why does the build decide to compile/link the version > > of glob that comes with make? If you're using glibc then it should > > use the one that comes with glibc instead. > > Wasn't this specifically done to workaround make us

Re: undefined reference to `__alloca'

2017-11-18 Thread Earnestly
On Sat, Nov 18, 2017 at 01:02:00PM -0500, Paul Smith wrote: > Thanks for the good info on your version of make and GCC... but... can > you provide details on what operating system you're using? I'm currently using Arch Linux currently on kernel 4.13.11 with a lot of packages built from latest deve

Re: undefined reference to `__alloca'

2017-11-18 Thread Paul Smith
On Sat, 2017-11-18 at 16:17 +, Earnestly wrote: > However I am now getting: Thanks for the good info on your version of make and GCC... but... can you provide details on what operating system you're using? I can't reproduce this on any of my systems so I'm just curious. Is it just the newer

Re: undefined reference to `__alloca'

2017-11-18 Thread Earnestly
On Thu, Nov 02, 2017 at 11:40:50AM +, Earnestly wrote: > Hi, > > For reference my system has the following versions and environs: > > * gcc 7.2.0 > * glibc 2.26.9000 (commit 2fac6a6cd5) > * make 4.2.90 (commit baa57d2) [patched, see below] > > * CPPFLAGS -D_FORTIFY_SOURCE=2 > * CFLAGS -march=x8