Discussion, talk and tips
https://forum.puppylinux.com/
Tried modesetting driver by default too, but, it keeps defaulting back to vesa, which shows up on the welcome page as "Currently using vesa driver" I am going to try a clean run_woof build again and report. Thank you for all the help and a merry xmas to you.
That welcome page thing is an old and dirty piece of code. Don't trust everything it says 
The whole reason I wanted to get QuickPet was because I wanted to add a few more i386 packages so that Steam works. Seems Steam won't run unless these i386 libraries are installed. I tried manually dpkg installing them, but dependency issues come up on Jammy x64. So, I tried building them. I tried adding i386 versions of these libraries into the DISTRO_PKGS_SPECS file as such - library-i386. That didn't work. So, I tried library:i386. In both these cases, running ./1download says these packages weren't found. So, my question is, is the DISTRO_PKGS_SPECS parsed after ./1download step at all? If not, then can I simply add the i386 debs to the packages-deb folder after I run ./1download. Will these then be included in the Jammy x64 build?
If that's not the way to go, is there an alternative to add i386 debs to Jammy x64 build?
PPM doesn't understand the concept of packages for two different architectures, installed side-by-side. woof-CE uses the PPM package format and parts of PPM, so it suffers from the same design limitation and doesn't understand things like "libc6:i386". If you add the i386 repo at build time, woof-CE will start replacing some amd64 packages with i386 ones, which is not what you want.
I see only one way to do this and that's modifying woof-code/support/bdrv.sh: add dpkg --add-architecture i386, apt update and apt install whatever:i386 there.
(But I don't really see a reason to modify quicpket or woof-CE itself, if you can just apt install steam really.)
dimkr wrote: ↑Mon Dec 26, 2022 6:29 amPPM doesn't understand the concept of packages for two different architectures, installed side-by-side. woof-CE uses the PPM package format and parts of PPM, so it suffers from the same design limitation and doesn't understand things like "libc6:i386". If you add the i386 repo at build time, woof-CE will start replacing some amd64 packages with i386 ones, which is not what you want.
I see only one way to do this and that's modifying woof-code/support/bdrv.sh: add
dpkg --add-architecture i386,apt updateandapt install whatever:i386there.(But I don't really see a reason to modify quicpket or woof-CE itself, if you can just
apt install steamreally.)
Have given up on Steam for Jammy and Fossa. As for apt installing Steam, the community generally advises against it and in my attempts even after adding the sources.list manually in /etc/apt, I see Steam fails to install or run. Looking into Wine now.
BTW, as for editing woof-code/support/bdrv.sh, is there any specific area in code where I should add this or anything to be careful of?
@dimkr The building was working fine still yesterday. But, right now, when I try to build Jammy pup with the pre-built jammy pup ISO and devx sfs loaded onto Woof_run, it always fails at this error:-
Code: Select all
--2023-01-04 07:54:57-- https://busybox.net/downloads/busybox-1.35.0.tar.bz2
Resolving busybox.net (busybox.net)... 140.211.167.122
Connecting to busybox.net (busybox.net)|140.211.167.122|:443... connected.
Unable to establish SSL connection.
tar (child): busybox-1.35.0.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
cp: cannot create regular file 'busybox-1.35.0/.config': No such file or directory
../support/petbuilds.sh: line 124: cd: busybox-1.35.0: No such file or directory
make: *** No targets specified and no makefile found. Stop.
install: cannot stat 'busybox': No such file or directory
I tried using the Fossapup ISO and devx to build jammy with woof_run. But, it fails at finding Boost libs. I tried exporting BOOST_ROOT, but that didn't change anything.
It was working completely fine till yesterday. Could some change in Woof-CE have triggered this?
Nothing has changed in woof-CE, it's just a download failure of busybox according to the log you sent. Have you tried to run 3builddistro again?
Tried running it multiple times, tried using a VPN. Tried resetting my IP. Tried on a different network. Weirdly enough, I edited the petbuild file for busybox in the chroot and added an echo "Hey" Since then, the build has progressed. I will try running it again to check.
As far as I see busybox.net is down at the moment, so wait until you can download https://busybox.net/downloads/busybox-1.35.0.tar.bz2.
dimkr wrote: ↑Wed Jan 04, 2023 1:37 pmAs far as I see busybox.net is down at the moment, so wait until you can download https://busybox.net/downloads/busybox-1.35.0.tar.bz2.
Thank you for that. The issue was that while .3builddistro couldn't access the file, I was still able to download it properly with my browser and using wget.
dimkr wrote: ↑Wed Jan 04, 2023 1:37 pmAs far as I see busybox.net is down at the moment, so wait until you can download https://busybox.net/downloads/busybox-1.35.0.tar.bz2.
Unfortunately the boostlib error is back now. Busybox downloads fine though. This is what I see:-
Code: Select all
checking for boostlib >= 1.40.0... configure: We could not detect the boost libraries (version 1.40 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation.
configure: error: `boost' not found.
ERROR: failed to build abiwordThings I have tried to fix this:-
1. Tried export BOOST_ROOT=/usr/include/boost
2. Installed libboost-all-dev with PPM
Neither of these seems to fix this issue. I did check the version.hpp file, which says Boost is version 1.74.
Something about your build is broken. I'd recommend running 1download and 2createpackages again. Keep the logs and look closely, I wouldn't be surprised if the boost package is missing or partial.
It doesn't matter what you have on the Puppy you're using to run woof-CE, woof-CE sets up a chroot environment and builds packages inside the Puppy you're building. You don't need to install anything on the host.
dimkr wrote: ↑Thu Jan 05, 2023 7:31 amSomething about your build is broken. I'd recommend running 1download and 2createpackages again. Keep the logs and look closely, I wouldn't be surprised if the boost package is missing or partial.
It doesn't matter what you have on the Puppy you're using to run woof-CE, woof-CE sets up a chroot environment and builds packages inside the Puppy you're building. You don't need to install anything on the host.
You were right! It was the jammy packages file, which was somehow missing libboost-dev. I was able to pass that step after a few clean redos of run_woof. But, the struggle continues since gpicview won't build now, due to a sha256 sum mismatch. I tried manually downloading gpicview and checking its sha256sum and it was correct. I am guessing it wasn't being downloaded properly in the first place. Now, I am trying to build from the beginning by setting the time and timezone properly. This could be an issue with sourceforge not resolving properly. I m just spitballing here. Anyways, downloading without gpicview does go, as intended though. I will be updating the situation.
Update - Setting timezone and time before running builddistro fixed issue with gpicview.