Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Rainer Hurling
Am 26.01.25 um 19:12 schrieb Nuno Teixeira: I've got same pkg issue like yours. My case is happening with poudriere builds on llvm19 since I have it default. So, every pkg that depends on it, I'll get a rebuild of llvm19. Later on I will try to bump llvm19 portrevision and thus be the hacker

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) For the next days I will start using a poudriere.conf with minimal diff to .sample so it may be easier for future debug. In my case, its simple as: $ diff poudriere.conf.sample poudriere.conf < #ZPOOL=zroot --- > ZPOOL=zroot 30c30 < FREEBSD_HOST=_PROTO_://_CHANGE_THIS_ --- > FREEBSD_HOST=

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
> > I use poudriere-devel and some time ago, me and other people "complaint" > about so much rust rebuilds because of curl dependency. > In that time, we start using poudriere.conf PKG_NO_VERSION_FOR_DEPS=yes to > avoid that rebuilds. > I can confirm that poudriere-devel *without* PKG_NO_VERSION_F

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
So something happened since tomorrow that breaks this? Do you have a fix in mind? Thanks, Tatsuki Makino escreveu (domingo, 26/01/2025 à(s) 20:39): > Hello. > > My environment is that :), but I have llvm19 installed, so I will write > about what I did a little research. > > In llvm19, a file t

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Tatsuki Makino
Hello. My environment is that :), but I have llvm19 installed, so I will write about what I did a little research. In llvm19, a file that seems to have 32-bit libc++ linked. The command looks like this. find /usr/local/ -exec sh -c 'readelf -d -- ${1} 2> /dev/null | grep -e libc++\\.so\\.1' a

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
I'm building and rebuilding llvm19 since morning... Now I'm feeling less stressed by knowing that more people get to it. I use poudriere-devel and some time ago, me and other people "complaint" about so much rust rebuilds because of curl dependency. In that time, we start using poudriere.conf PKG_

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Guido Falsi
On 26/01/25 20:33, Nuno Teixeira wrote: (...) Same after a portrevision bump on llvm19: [00:00:15] [01] [00:00:00] Warning: llvm19-19.1.7_1 will be rebuilt as it misses libc++.so.1:32 [00:00:15] [01] [00:00:00] Building   devel/llvm19@default | llvm19-19.1.7_1: missed shlib PORTREVISION chase

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) Same after a portrevision bump on llvm19: [00:00:15] [01] [00:00:00] Warning: llvm19-19.1.7_1 will be rebuilt as it misses libc++.so.1:32 [00:00:15] [01] [00:00:00] Building devel/llvm19@default | llvm19-19.1.7_1: missed shlib PORTREVISION chase :( Nuno Teixeira escreveu (domingo, 26/0

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
I've got same pkg issue like yours. My case is happening with poudriere builds on llvm19 since I have it default. So, every pkg that depends on it, I'll get a rebuild of llvm19. Later on I will try to bump llvm19 portrevision and thus be the hacker of year is by this it is solved :) Something sa

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Rainer Hurling
Am 26.01.25 um 16:36 schrieb Nuno Teixeira: (...) poudriere-devel-3.4.99.20250115 poudriere.conf: + PKG_NO_VERSION_FOR_DEPS=yes EDIT: pkg 2.0.4 doesn't fixed issue Hmm. Maybe it's because of pkg, which was recently updated to 2.x? On my box, outside of Poudriere, I've been getting missing l

A few ports to review

2025-01-26 Thread Pavel Timofeev
Hello While I'm working on bringing the latest cinnamon-6.4 (I plan to finish it in the early/middle of Feb) to the ports tree right now I'd like someone to take a look at a few cinnamon-related ports: 1. editors/xed: update to 3.8.2 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282385 2. g

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) poudriere-devel-3.4.99.20250115 poudriere.conf: + PKG_NO_VERSION_FOR_DEPS=yes EDIT: pkg 2.0.4 doesn't fixed issue Nuno Teixeira escreveu (domingo, 26/01/2025 à(s) 15:21): > Ok, I can reproduce this on a new jail: > > # cd /usr/src > # make buildworld-jobs buildkernel-jobs > # poudriere

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
Ok, I can reproduce this on a new jail: # cd /usr/src # make buildworld-jobs buildkernel-jobs # poudriere jail -c -j 15amd64_newjail -m src=/usr/src # poudriere testport -j 15amd64_newjail -p main games/rocksndiamonds repeat testport command: # Warning: llvm19-19.1.7 will be rebuilt as it misses

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) Also I delete all pkg in new jail everytime I upgrade: > # make buildworld-jobs buildkernel-jobs > # ./tools/build/beinstall.sh > # reboot # poudriere pkgclean -A -j 15amd64 -p main > # poudriere jail -u -j 15amd64 # poudriere bulk -j 15amd64 -p main -f /path/to/list.ports Nuno Teixeira

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
% doas poudriere jail -s -j 15amd64 -p main % doas jexec 15amd64-main # ls -l /usr/lib32/libc++.so.1 -r--r--r-- 1 root wheel 957764 Jan 25 23:50 /usr/lib32/libc++.so.1 (My rolled BE is Jan 11 and somehow inside jail is showing Jan 25) Should I try delete jail and install a new one instead of upg

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Dimitry Andric
Does your jail have /usr/lib32/libc++.so.1? -Dimitry > On 26 Jan 2025, at 13:18, Nuno Teixeira wrote: > > > As usual everytime I upgrade: > > # make buildworld-jobs buildkernel-jobs > # ./tools/build/beinstall.sh > # reboot > > # poudriere jail -u -j 15amd64 > > # poudriere jail -l > JAILNA

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
As usual everytime I upgrade: # make buildworld-jobs buildkernel-jobs # ./tools/build/beinstall.sh # reboot # poudriere jail -u -j 15amd64 # poudriere jail -l JAILNAME VERSION OSVERSION ARCH METHOD TIMESTAMP PATH 134amd64 13.4-RELEASE-p2 1304000 amd64 http

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Dimitry Andric
On 26 Jan 2025, at 12:41, Nuno Teixeira wrote: > > Got this loop on: > > main-n275036-faa845aab611 > poudriere jail is same version > > Warning: llvm19-19.1.7 will be rebuilt as it misses libc++.so.1:32 > Building devel/llvm19@default | llvm19-19.1.7: missed shlib PORTREVISION > chase > > I

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) ls -l /lib/libc++* -r--r--r-- 1 root wheel 1010848 Jan 25 23:40 /lib/libc++.so.1 Nuno Teixeira escreveu (domingo, 26/01/2025 à(s) 11:45): > (...) > > ll /usr/lib/libc++* > -r--r--r-- 1 root wheel 9389840 Jan 25 23:40 /usr/lib/libc++.a > -r--r--r-- 1 root wheel 48 Aug 22 2023 /usr

Re: poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
(...) ll /usr/lib/libc++* -r--r--r-- 1 root wheel 9389840 Jan 25 23:40 /usr/lib/libc++.a -r--r--r-- 1 root wheel 48 Aug 22 2023 /usr/lib/libc++.so -r--r--r-- 1 root wheel 948 Jan 25 23:40 /usr/lib/libc++experimental.a Why is libc++.so.1 missing? Nuno Teixeira escreveu (domingo, 26/

poudriere loop: llvm19-19.1.7: missed shlib PORTREVISION chase

2025-01-26 Thread Nuno Teixeira
Hello all, Got this loop on: main-n275036-faa845aab611 poudriere jail is same version Warning: llvm19-19.1.7 will be rebuilt as it misses libc++.so.1:32 Building devel/llvm19@default | llvm19-19.1.7: missed shlib PORTREVISION chase It repeats this loop every time I run a testport. Any clues?