SLES 15.2 Stacki OS Pallet Build

23 views
Skip to first unread message

Walter Szeliga

unread,
Mar 31, 2021, 5:39:10 PM3/31/21
to stacki
Hi all,
    I've been having trouble building the stacki OS pallet for SLES 15.2 using the stacki 5.6.5 github tag. 

Starting with a fresh SLES 15.2 install with the "Server" use-case option, I checked out


and switched to the 5.6.5 tag. I edited

common/src/stack/build/build/bin/os-release

to include an if branch for SLES 15.2. I also needed to make a few fiddly changes to the following files to get things to build:

common/src/foundation/python/Makefile # To add --libdir=/opt/stack/lib
common/src/foundation/python/stacki-python.conf # To add /opt/stack/lib64
common/src/stack/config/etc/ld.so.conf.d/stack.conf # To add /opt/stack/lib64

I assume these changes reflect some difference between 32-bit and 64-bit assumptions in 15.2 that weren't there previously. I then Then I did a

make bootstrap

Everything compiles and I get the message to log out and then back in again. I do so and then rerun 

make bootstrap

which then appears to complete without error (there's a lot of output, but scrolling through it, things look good). I assume the next step is to run

make preroll

which then fails after some time with

...
mkdir -p build-stacki-stacki_5.6.5/graph
mkdir -p build-stacki-stacki_5.6.5/nodes
mkdir -p build-stacki-stacki_5.6.5/pallet_hooks/common
mkdir -p build-stacki-stacki_5.6.5/pallet_hooks/sles
cp common/graph/* sles/graph/* build-stacki-stacki_5.6.5/graph/
cp common/nodes/* sles/nodes/* build-stacki-stacki_5.6.5/nodes/
cp -r common/pallet_hooks/ build-stacki-stacki_5.6.5/pallet_hooks/common/
cp: cannot stat 'common/pallet_hooks/': No such file or directory
make: [Makefile:57: preroll] Error 1 (ignored)
cp -r sles/pallet_hooks/  build-stacki-stacki_5.6.5/pallet_hooks/sles/

What's missing for an SLES build to complete and what steps remain to create the ISO for SLES?

As an aside, I also tried to build 5.6.5 from the source tar ball on the release page, with similar negative results. The difference between the github tag build and the source tar ball was that the source tar ball assumed my source tree was a git tree and failed. To continue the build, I had to comment out the VCS line in stacki/common/src/stack/build/build/etc/Rules-sles.mk. In the end I chose to just check out the code from the git source tree.

Cheers,
Walter

Reply all
Reply to author
Forward
0 new messages