[lfs-support] making xz-5.2.3

[Paul Rogers]

I started working an 8.1 build some months ago, but I upgraded to gcc-7.3 and linux-4.14.26, for security reasons. Everything has been going well. (Host is LFS-7.10.) I have an error compiling xz-5.2.3, but this is the same version and build instructions as used in 8.2 with gcc-7.3. (I intend this to run on more than the i7 I'm building on, so have -mtune=generic, but that's the only departure from the book I know of. xz seems to be a place I'd want generic code.) You have no errata for it. I'm not turning up anything in Google from the mailiing list or generically for this. It does seem to me to be something internal.

/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/liblzma/api -I../../src/liblzma/common -I../../src/liblzma/check -I../../src/liblzma/lz -I../../src/liblzma/rangecoder -I../../src/liblzma/lzma -I../../src/liblzma/delta -I../../src/liblzma/simple -I../../src/common -DTUKLIB_SYMBOL_PREFIX=lzma_ -pthread -fvisibility=hidden -Wall -Wextra -Wvla -Wformat=2 -Winit-self -Wmissing-include-dirs -Wstrict-aliasing -Wfloat-equal -Wundef -Wshadow -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wlogical-op -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-declarations -Wmissing-noreturn -Wredundant-decls -march=x86-64 -mtune=generic -MT liblzma_la-lz_encoder.lo -MD -MP -MF .deps/liblzma_la-lz_encoder.Tpo -c -o liblzma_la-lz_encoder.lo `test -f 'lz/lz_encoder.c' || echo './'`lz/lz_encoder.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/liblzma/api -I../../src/liblzma/common -I../../src/liblzma/check -I../../src/liblzma/lz -I../../src/liblzma/rangecoder -I../../src/liblzma/lzma -I../../src/liblzma/delta -I../../src/liblzma/simple -I../../src/common -DTUKLIB_SYMBOL_PREFIX=lzma_ -pthread -fvisibility=hidden -Wall -Wextra -Wvla -Wformat=2 -Winit-self -Wmissing-include-dirs -Wstrict-aliasing -Wfloat-equal -Wundef -Wshadow -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wlogical-op -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-declarations -Wmissing-noreturn -Wredundant-decls -march=x86-64 -mtune=generic -MT liblzma_la-lz_encoder.lo -MD -MP -MF .deps/liblzma_la-lz_encoder.Tpo -c lz/lz_encoder.c -fPIC -DPIC -o .libs/liblzma_la-lz_encoder.o
lz/lz_encoder.c: In function 'lzma_lz_encoder_init':
lz/lz_encoder.c:556:12: warning: dereferencing 'void *' pointer
next->coder->mf.size = 0;
^~
lz/lz_encoder.c:556:12: error: request for member 'mf' in something not a structure or union
make[4]: *** [Makefile:1331: liblzma_la-lz_encoder.lo] Error 1
make[4]: Leaving directory '/usr/local/src/xz-5.2.3/src/liblzma'
make[3]: *** [Makefile:1553: all-recursive] Error 1
make[3]: Leaving directory '/usr/local/src/xz-5.2.3/src/liblzma'
make[2]: *** [Makefile:420: all-recursive] Error 1
make[2]: Leaving directory '/usr/local/src/xz-5.2.3/src'
make[1]: *** [Makefile:613: all-recursive] Error 1
make[1]: Leaving directory '/usr/local/src/xz-5.2.3'
make: *** [Makefile:480: all] Error 2

Any helpful ideas? TIA.

(I suppose a fallback might be to try compiling without -mtune, the one known difference, and later recompile xz on something like a P4 or Conroe?)
--
Paul Rogers
***@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/

[Paul Rogers]

I'm much too old to have learned C, but I went to look at that file and the line in question. It just looked "odd", not indented as the rest of the code was. So I blew away the package, reloaded and reran the build script without "-j 8" so's I could localize any error, but still with -mtune in CFLAGS, and it ran without a hitch. Fine, I'll take it. I don't know where that odd line came from, but I don't even know if I can reproduce it. I'll go on from here, see what happens, if anything.

Apologies for interrupting your weekend.
--
Paul Rogers
***@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikip