cannot compile cryptsetup
 

I cannot compile cryptsetup in my BLFS 8 system. Automake is the point of failure.

my build script, up to where the failure occurs
How I run the script
The output
I have googled the "subdir-objects" error messages. Several ideas that worked for other people are incorporated in the my build script. Naturally, they don't work. :p

Has anyone else actually gotten cryptsetup to build in a BLFS8 system?

Why don't you simply use BLFS instructions?

http://www.linuxfromscratch.org/blfs...ryptsetup.html

(It was added a few days ago, it isn't part of BLFS 8)

For future reference, "autoreconf --force --install", short "autoreconf -fi" would've done the same and probably succeeded. Many packages also come with autogen.sh script, which generate autotools files in proper manner.

Just a couple of things about the syntax of the script to make it more readable, first the "OUT_NAME=cryptsetup-2017.06.28-$ARCH-$BUILD\_lfs.txz"

Instead of escaping the underscore, which is a legal character for a bash variable the usual way to use this would be the use of '{}' which are used when the var name may be ambiguous eg "${ARCH}-${BUILD}_lfs.txz"

Second as you are specifying bash in the shebang you really should use $(command) instead of `command` for command substitution its, POSIX correct and is more readable with less chance of confusion with "'".

Also as Krejzi said use the autogen.sh script if available.

I wish that were the case, but many I've seen... Mainly where the developers are using a git repo and appear to not really be familiar with building packages for release, don't setup their autogen.sh correctly. I'll often find packages that, when building "release" will leave -g or -ggdb CFLAGS in the all: makefile. (Nettle) Some, won't invoke --copy when running autoheader, autoconf, etc. and leave the symlinks to their local system for those files (recent polkit), or docize preps missing (Freedesktop). Finally, the worst is packages with unresolved references to gobject introspection. Those will bomb the autoconf if you don't have glib and gi installed, even if the package allows --disable-introspection to be used. I suspect its because autotools can't deal with it without the reference metadata in the glib/introspection packages. :(

YMMV with autotools. CMake, on the other hand, I have yet to see complain that some parts of itself are missing or incomplete. Dependencies yes, but not anything like "oh hey, I'd like to run, but my bootstrap is missing." :D

You asked:
Because Cryptsetup is not in the BLFS 8 instructions. Oh, you meant the unstable version! I normally don't look at the unstable version of the book, because I try for, erm, stability. :)

In this case, using the version of the CryptUtils package linked from that version of the BLFS book actually worked. It didn't have a missing ./configure file. Thank you very much. :)

You know it is a legal character, and I know it is a legal character, but try to convince bash of that. Sections of the OUT_NAME just disapear if I don't put that "\_" in. There's something wacky going on there and I haven't the smarts nor the patience to go look at bash's source code. :o

If I use {} around every variable, things would look a right mess, even more like spaghetti code than I see in <redacted>. :p

you're wrong using {} makes tdhe code clearer to read as it makes it clear WHAT is a variable name and what isn't i have been scrippting with bash for years and have NEVER had to escape part of the name just used {} which is the correct way of doing it.