------- distros ------- I have been compiling Wine, and other software, in a few puppy distros. I label pet packages with version numbers indicating which pup they were compiled in. This also indicates the lowest glibc version number the software will successfully run with. Also indicates whether software was stripped or not. v1.1 puppy 431 stripped=true v1.2 puppy 431 stripped=false v2.1 racy 5.5 stripped=true v2.2 racy 5.5 stripped=false v3.1 tahrpup 6.0.5 PAE stripped=true v3.2 tahrpup 6.0.5 PAE stripped=false v4.1 tahrpup64 6.0.5 stripped=true v5.1 S15Pup32 stripped=true v6.1 S15Pup64 stripped=true example: wine-5.0_v3.1 - wine-5.0 compiled in tahrpup 6.0.5 PAE. will run in any(?) pup with glibc version 2.19 and above. Wine was stripped. For general use, I recommend packages that are 'stripped=true'. For submitting bug reports to the software developers, I recommend packages that are 'stripped=false'. It appears 'stripped=false' provides more useful information. [references] Strip_(Unix) strip What constitutes a good backtrace? How to compile Wine without debugging symbols Compiler Optimizations optimizations [/references] --------- # puppy 431 --------- mirrors | /distro/4.3__1/puppies-431.1-main-Xserver.iso mirrors | /distro/4.3__1/devx_430.sfs kernel release 2.6.30.5 # uname --kernel-release compiler version 4.2.2 # gcc --version glibc 2.6.1 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'puppy 431', when installed into a puppy distro with a glibc: - before 2.6.1, will possibly fail - of 2.6.1 and above, will possibly succeed -------- # racy 5.5 -------- mirrors | /distro/racy5.5/racy-5.5.iso mirrors | /distro/racy5.5/devx_racy_5.5.sfs kernel release 3.0.66 # uname --kernel-release compiler version 4.3.4 # gcc --version glibc 2.10.1 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'racy 5.5', when installed into a puppy distro with a glibc: - before 2.10.1, will possibly fail - of 2.10.1 and above, will possibly succeed ----------------- # tahrpup 6.0.5 PAE ----------------- mirrors | /distro/tahrpup-6.0.5_PAE/tahr-6.0.5_PAE.iso mirrors | /distro/tahrpup-6.0.5_PAE/devx_tahr_6.0.5.sfs kernel release 3.14.56 # uname --kernel-release compiler version 4.8.4 # gcc --version glibc 2.19 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'tahrpup 6.0.5 PAE', when installed into a puppy distro with a glibc: - before 2.19, will possibly fail - of 2.19 and above, will possibly succeed --------------- # tahrpup64 6.0.5 --------------- mirrors | /distro/tahr64-6.0.5/tahr64-6.0.5.iso mirrors | /distro/tahr64-6.0.5/devx_tahr64_6.0.5.sfs kernel release 3.14.54 # uname --kernel-release compiler version 4.8.4 # gcc --version glibc 2.19 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'tahrpup64 6.0.5', when installed into a puppy distro with a glibc: - before 2.19, will possibly fail - of 2.19 and above, will possibly succeed -------- # S15Pup32 -------- kernel release 5.10.156 # uname --kernel-release compiler version 11.2.0 # gcc --version glibc 2.33 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'S15Pup32', when installed into a puppy distro with a glibc: - before 2.33, will possibly fail - of 2.33 and above, will possibly succeed -------- # S15Pup64 -------- kernel release 5.15.80 # uname --kernel-release compiler version 11.2.0 # gcc --version glibc 2.33 # ldd --version # /lib/libc.so.6 # getconf GNU_LIBC_VERSION software compiled in 'S15Pup64', when installed into a puppy distro with a glibc: - before 2.33, will possibly fail - of 2.33 and above, will possibly succeed ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- packages needed for compiling: ------- # dir2pet ------- https://gitlab.com/version2013/puppylinux/blob/master/dir2pet https://github.com/puppylinux-woof-CE/woof-CE/blob/testing/woof-code/rootfs-skeleton/usr/bin/dir2pet - Put 'dir2pet' in '/mnt/home/compile' - Give the file execute permission. # chmod a+x dir2pet ----------- # splitpkg.sh ----------- https://gitlab.com/version2013/puppylinux/blob/master/splitpkg.sh - Put 'splitpkg.sh' in '/mnt/home/compile' - Give the file execute permission. # chmod a+x splitpkg.sh http://www.oldforum.puppylinux.com/puppy/viewtopic.php?p=905715#905715 - Or download 'splitpkg.tar.gz', extract and place in '/mnt/home/compile' ------------------ Edited 2023 Apr 24 ------------------
Make a free website with Yola