> why this current release code won't work

https://lists.gnu.org/archive/html/info-gnu/2016-06/msg00005.html says 
make-4.2.1 is from 2016-06-11.  In the email thread I cited previously, for 
what looked like the same errors, we see Paul writing, over a year after that 
release, on 2017-11-19, "I pushed a change that should allow this to work 
properly".  So the reason that the current release code won't work is, I 
suggest, because there hasn't been a new release that includes that change.  
Why not cut to the chase, prove it, tell us and thus help to encourage a new 
release?  If you want a shortcut, perhaps Paul's patch was:

http://git.savannah.gnu.org/cgit/make.git/commit/?id=48c8a116a914a325a0497721f5d8b58d5bba34d4

But patching configure.ac sounds like something that would then need the full 
build-from-git procedure, with autotools, rather than the build from a release 
tarball, in which case I think you'd be better off with the git head.  Still, 
perhaps you could patch whatever file the configure script is generating there 
as a quick proof of concept.

On Apr 2, 2018, at 07:03, Dennis Clarke 
<dcla...@blastwave.org<mailto:dcla...@blastwave.org>> wrote:

On 01/04/18 05:29 PM, Paul Smith wrote:
On Sun, 2018-04-01 at 16:56 -0400, Dennis Clarke wrote:
So I could just lift that out of glibc 2.27 and drop it into the make
  source tree and have a go at it.  Is that the idea here ?
You could try, but I'm not optimistic that it will just work.

"just work" ?  nope.  not even close.

I think the way forward is to get the latest code from GNU make's Git
repository and see if that works:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsavannah.gnu.org%2Fgit%2F%3Fgroup%3Dmake&data=01%7C01%7CMartin.Dorey%40hitachivantara.com%7C3aaed7f79d5f44e9e21408d598a289ba%7C18791e1761594f52a8d4de814ca8284a%7C0&sdata=A3q0nOCtgUS08XtpHymxJQOZ2qTFK9f8Kuo3wgXKhaI%3D&reserved=0

Well sure ... however before I get there I am still baffled why this
current release code won't work on an old 32-bit intel debian server?

I just compiled kernel 4.15.15 on that machine and am running it now.

Certainly if I can compile and run a new kernel on the same machine I
would think I can compile GNU make from sources?  Or am I stretching
here?

root@phobos:~# cat /proc/version
Linux version 4.15.15-genunix (admsys@phobos) (gcc version 7.3.0 (Debian 
7.3.0-13)) #1 SMP Sun Apr 1 22:27:12 UTC 2018


Be sure to read the README.git file for information on building from
Git, rather than from a source distribution (it requires extra packages
to be installed, such as autotools).

yep .. autoreconf and its brethern however I suspect something else is
going on here.

Dennis

_______________________________________________
Bug-make mailing list
Bug-make@gnu.org<mailto:Bug-make@gnu.org>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.gnu.org%2Fmailman%2Flistinfo%2Fbug-make&data=01%7C01%7CMartin.Dorey%40hitachivantara.com%7C3aaed7f79d5f44e9e21408d598a289ba%7C18791e1761594f52a8d4de814ca8284a%7C0&sdata=yjRoh86gJtY5iJrwAVzEcjD5kfyBTIIEgC9Fjx2qFCo%3D&reserved=0
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Reply via email to