Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?
--- Begin Message --- Hi folks, Am 21.01.2021 um 04:24 schrieb Denis Ovsienko via tcpdump-workers : >> s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian >> platform, so we can do some testing of operation on big-endian >> machines. Just as a tiny comment: big-endian is also checked on Solaris Sparc with the OpenCSW farm buildbot already hooked up in the Github CI. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] build failures on Solaris
--- Begin Message --- Hi Denis, Am 03.08.2021 um 00:34 schrieb Denis Ovsienko via tcpdump-workers : > Though it is not clear why the 64-bit directories are not in PATH. This is because you need to decide whether you want to build against the 32 or 64 bit ABI. Solaris nowadays always runs a 64 bit kernel but allows programs and libraries to be in 32 bit, although you cannot mix 32 and 64 bit within a linked executable. Of course it would be possible to switch the PATH to be 64 bit only on Solaris 10 but was not done due to historical reasons. On Solaris 11 most binaries are 64 bit now but are located in /usr/bin which makes this thing a bit convoluted. When you try to build a 64 bit binary the correct way is to set PATH and PKG_CONFIG_PATH as described here: https://www.opencsw.org/manual/for-developers/index.html The /64 suffix in bin/ and lib/ is a symlink to the respective architecture and simplifies cross-platform build between Sparc and x86. I hope this helps. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] build failures on Solaris
--- Begin Message --- Hi Guy, Am 03.08.2021 um 09:26 schrieb Guy Harris : > On Aug 3, 2021, at 12:07 AM, Dagobert Michelsen wrote: > >> The /64 suffix in bin/ and lib/ is a symlink to the respective architecture >> and simplifies cross-platform build between Sparc and x86. > > For whatever reason, /usr/bin/64 isn't present on my Solaris 11.3 (x86-64) VM: > > solaris11$ ls /usr/bin/64 > /usr/bin/64: No such file or directory > solaris11$ uname -a > SunOS solaris11 5.11 11.3 i86pc i386 i86pc > > The same is true of the directory containing the installed-from-IPS gcc: > > solaris11$ which gcc > /usr/ccs/bin/gcc > solaris11$ ls /usr/ccs/bin/64 > /usr/ccs/bin/64: No such file or directory > > and Sun/Oracle C: > > solaris11$ which cc > /opt/developerstudio12.5/bin/cc > solaris11$ ls /opt/developerstudio12.5/bin/64/cc > /opt/developerstudio12.5/bin/64/cc: No such file or directory > > Sun/Oracle don't appear to have made as vigorous an effort to make this work > as OpenCSW have. The reason is probably that it is usually not important if you use the 32 or 64 bit binary - you just want the one that is suitable which was historically done by hardlinking the name to isaexec searching to ISAs from most to least optimal or linker ISA features nowadays. This is obviously not the case for *-config where you want exactly 32 or 64 bit depending on your build ISA. To make things worse Solaris 11 has a mixture of 32 and 64 bit binaries in /bin, but again which most of the time does not make a difference. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
