Article 6QEKP SBO fontforge: compiling for multilib, 32bit fails

SBO fontforge: compiling for multilib, 32bit fails

by
jr_bob_dobbs
from LinuxQuestions.org on (#6QEKP)
I'm running Slackware 15.0, with Alien Bob's multilib bits added.

I was attempting to compile fontforge, using the slackbuild from Slackbuilds.org. It compiles all the way and builds fine for 64 bit. For 32 bit it fails.
Code:root@moonshadow:fontforge # . /etc/profile.d/32dev.sh
root@moonshadow (32bit):/home/bob/compile/fontforge# OUTPUT=$(pwd) \
> ARCH="i586" \
> CFLAGS="-O2 -march=i586 -mtune=i686" \
> CXXFLAGS="-O2 -march=i586 -mtune=i686" \
> ./fontforge.SlackBuild > ./slack_log_32.txt
CMake Error at /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find Python3 (missing: Python3_EXECUTABLE Python3_INCLUDE_DIRS
Python3_LIBRARIES Development Interpreter Development.Module
Development.Embed) (Required is at least version "3.3")

Reason given by package:
Interpreter: Wrong architecture for the interpreter "/usr/bin/python3"

Call Stack (most recent call first):
/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.21/Modules/FindPython/Support.cmake:3166 (find_package_handle_standard_args)
/usr/share/cmake-3.21/Modules/FindPython3.cmake:485 (include)
cmake/PackageUtils.cmake:41 (find_package)
CMakeLists.txt:137 (find_package_auto)

root@moonshadow (32bit):/home/bob/compile/fontforge#The documenation for compiling things for multilib mentions that one should always add "--build=$ARCH-slackware-linux" to the ./configure line, but this slackbuild uses cmake so the above is impossible. I am wondering if that is the cause?

At this point I haven't got enough disk space to set up a 32-bit only slackware just to compile one package, so I'm stuck. Does anyone have a clue?
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments