On Mon, May 05, 2025 at 10:17:58PM +1200, Jonathan Chen wrote:
> Hi,
>
> I'm running 14-stable/amd64, updated 2025-03-14, and I'm currently seeing
> www/chromium builds failing with:
>
> gen/third_party/blink/renderer/core/css/css_property_names.cc:354:7: error:
> fallthrough annotation does not
On Sun, Mar 23, 2025 at 10:15:03PM +, Jonathan Chen wrote:
> Hi,
>
> Building www/chromium 134.0.6998.165 on my 14-STABLE/amd64 currently fails
> with:
>
> ../../third_party/webrtc/modules/video_capture/linux/pipewire_session.cc:90:3:
> error: no matching function for call to 'pw_node_add_l
TL;DR: poudriere build log for www/chromium ends with:
...
===
===
= env: 'PKG_NOTES=build_timestamp built_by'
'PKG_NOTE_build_timestamp=2025-01-25T15:03:22+00:00'
'PKG_NOTE
On Tue, Dec 24, 2024 at 05:55:54PM +0300, Gleb Popov wrote:
> On Tue, Dec 24, 2024 at 5:47 PM David Wolfskill wrote:
> >
> > I don't get it. Why would pkg want to be installing "-nox11"
> > versions of things?
>
> Why not? You specified a port origin ra
As an experiment, I set up my newest laptop to update only via
freebsd-update and installed only pre-built packages. (I am far more
accustomed to building FreeBSD from source, as well as updating ports
either via portmaster or by buidling my own packages, so there's a
fairly high probability that
On Wed, Aug 28, 2024 at 07:19:54AM -0700, Cy Schubert wrote:
> I should have checked ports-committers first. Looks like the fix went in
> this morning.
>
Confirmed: after updating my ports tree (in my case, to
main-n675360-efd8eb280e0b), I was able to (eventually!) build
chromium-128.0.6613.
My build machine gets the task of building packages for www/chromium
for the machines that actually use it. And it (and its earlier
instantiation) has been using poudriere-devel for package-building
since July, 2015.
Given the VuXML entry for chromium and the recent update of the latter
to 128.0.
TL;DR: I found that I needed to (manually) reinstall
bind-tools-9.18.28.pkg & bind918-9.18.28.pkg.
For my small installation at home (2 "production" machines; 1 "build"
machine, and some laptops that are (along with the build machine)
treated as "development" machines), I build my own pack
On Sat, Aug 10, 2024 at 08:05:25PM -0700, Steve Kargl wrote:
> How is perl 5.36.3 the default version when it dies with
>
> WARNING: re-sorting MANIFEST
> *** [MANIFEST.srt] Error code 1
>
> make: stopped making "all" in /usr/ports/lang/perl5.36/work/perl-5.36.3
> --- lib/auto/re/re.so ---
> Unsu
A PR (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279111) has been
opened with the intent to supply a suitable LICENSE for the x11-wm/piewm
port.
I am the maintainer of the port (out of self-defense, more than anything
else); I am unable to determine what would make sense in this case:
* Th
On Sat, May 11, 2024 at 07:29:29AM -0700, David Wolfskill wrote:
> TL;DR: As the Subject says; log & info at
> https://www.catwhisker.org/~david/FreeBSD/ports/firefox/
>
Today's poudriere run built www/firefox OK. Details of the environment:
Build machine wa
TL;DR: As the Subject says; log & info at
https://www.catwhisker.org/~david/FreeBSD/ports/firefox/
Additional detail:
I have 2 broad categories of FreeBSD machines here at home (all amd64):
* Development machines (a build machine & some laptops)
* Production machines (a multi-homed "traffic cop"/g
On Thu, Mar 14, 2024 at 07:44:47PM +0100, Emmanuel Vadot wrote:
>
> Hi David,
>
> On Thu, 14 Mar 2024 06:49:18 -0700
> David Wolfskill wrote:
> ...
> > The complete build typescript may be found at
> > https://www.catwhisker.org/~david/FreeBSD/ports/drm-515-
On Thu, Mar 14, 2024 at 07:44:47PM +0100, Emmanuel Vadot wrote:
>
> Hi David,
>
> On Thu, 14 Mar 2024 06:49:18 -0700
> David Wolfskill wrote:
>
> > This is on my laptop, during a source-based update from
> > main-n268772-906521f8176b to main-n268800-6a6ec90681
This is on my laptop, during a source-based update from
main-n268772-906521f8176b to main-n268800-6a6ec90681cf, in the "make
buildkernel" phase, as a result of:
g1-70(15.0-C)[3] grep PORT /etc/src.conf
PORTS_MODULES+=x11/nvidia-driver-390
PORTS_MODULES+=graphics/drm-515-kmod
(which has been there
On Mon, Mar 04, 2024 at 08:12:14PM -0800, David Wolfskill wrote:
> ...
> For the last "yes" entry, the build machine was running:
> FreeBSD 14.0-STABLE #33 stable/14-n266091-1e9df419f14c: Sat Dec 30 11:51:06
> UTC 2023
> r...@freebeast.catwhisker.org:/common/S1/ob
On Tue, Mar 05, 2024 at 12:35:33PM +0900, Tatsuki Makino wrote:
> I recently saw a similar problem and thought I had looked into something, but
> this was it.
> https://lists.freebsd.org/archives/freebsd-ports/2024-February/005546.html
>
> David Wolfskill wrote on 2024/03/05 10
Well... I had managed to get myself confused. In fairness, some of the
clues I was getting were misleading (at best).
TL;DR: After rebuilding a few packages, re-installing them, finding
that that didn't help, then force-re-installing the most recently-built
package for dns/libidn (libidn-1.38_1;
On Mon, Mar 04, 2024 at 12:25:30PM +0900, Tatsuki Makino wrote:
> ...
> One of the reasons for the name libc.so.6 was also present, including the
> following
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260434
> Or, if linux emulator is used, it also contains *.6 of lib.c.
>
Ah: Thank
On Mon, Mar 04, 2024 at 08:03:53AM +0900, Tatsuki Makino wrote:
> Hello.
>
> David Wolfskill wrote on 2024/03/04 03:33:
> > ld-elf.so.1: /usr/local/lib/libtasn1.so.6: version LIBTASN1_0_3 required by
> > /usr/local/lib/libgnutls.so.30 not defined
>
> I don't kno
On Sun, Mar 03, 2024 at 01:01:36PM -0600, rob...@rrbrussell.com wrote:
> On Sun, Mar 3, 2024, at 12:33, David Wolfskill wrote:
> > I have a local package-builder that's (generally) been working quite
> > well for me since Jul 2015 (through a couple of hardware replacement
I have a local package-builder that's (generally) been working quite
well for me since Jul 2015 (through a couple of hardware replacements,
sure, but the approach remains the same).
Today, in trying to chase down what was causing my central "hub" machine
to whine:
ld-elf.so.1: /usr/local/lib/libt
Symptom was:
albert(14.0-S)[4] sudo service named restart
Password:
named not running? (check /var/run/named/pid).
ld-elf.so.1: /usr/local/lib/libfstrm.so.0: version LIBFSTRM_0.2.0 required by
/usr/local/lib/libdns-9.18.24.so not defined
/usr/local/etc/rc.d/named: ERROR: named-checkconf for
/usr
On Thu, Nov 30, 2023 at 10:29:55PM -0500, AN wrote:
> ...
> > origin/2023Q3
> > origin/2023Q4
> > origin/HEAD -> origin/main
> > origin/main
> >
> > (so, remove the "origin/" part to get the branch name)/(so, remove the
> > "origin/" part to get the branch name)/
> ...
> Thanks for your qui
On Thu, Nov 30, 2023 at 08:24:47PM -0500, AN wrote:
> Hi:
>
> I just upgraded a system to src 14-stable. What is the exact command to
> checkout and track the 14-stable branch of ports?
There is no such thing as "the 14-stable branch of ports."
FreeBSD source ("src") and ports are separate repo
This was while the build host was running stable/12
(stable/12-n236282-b083794291d2). A subsequent attempt whlie it was
running stable/13 (stable/13-n256426-d03af6473e64) was OK.
Log is in https://www.catwhisker.org/~david/FreeBSD/ports/chromium/;
there's a compressed copy and an uncompressed one
On Fri, Apr 14, 2023 at 02:44:01AM +, j...@chen.org.nz wrote:
> Hi,
>
> I'm seeing the following build failure for electron22-22.3.5_1 on
> STABLE-13/amd64 after the latest devel/icu update:
>
Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270817
(which directly references
On Thu, Apr 13, 2023 at 07:03:52AM -0700, David Wolfskill wrote:
> ...
> So the "U_NOEXCEPT" lines are in the (older) icu-72.1,1.
>
> But on machines that have been updated this morning, I see:
>
> freebeast(12.4-S)[6] pkg info -o icu\*
> icu-73.1,1
On Thu, Apr 13, 2023 at 06:33:37AM -0700, David Wolfskill wrote:
> On Thu, Apr 13, 2023 at 03:26:53PM +0200, Dimitry Andric wrote:
> ...
> > In file included from ../../base/time/time_exploded_icu.cc:14:
> > ../../third_party/icu/source/common/unicode/locid.h:297:27: error: ex
On Thu, Apr 13, 2023 at 03:26:53PM +0200, Dimitry Andric wrote:
> On 13 Apr 2023, at 14:05, David Wolfskill wrote:
> >
> > Details in https://www.catwhisker.org/~david/FreeBSD/ports/chromium/
> > (Log is under 12/ in there.)
> ...
>
> The lines you posted didn'
Details in https://www.catwhisker.org/~david/FreeBSD/ports/chromium/
(Log is under 12/ in there.)
Overview:
Ports tree is at main-n615777-7e591c4f2380; build machine was running:
FreeBSD freebeast.catwhisker.org 12.4-STABLE FreeBSD 12.4-STABLE #206
stable/12-n236099-59f3510ea793: Mon Apr 10 10:3
So... I tried several times to submit this bug via bugzilla, and each
time was told (after about a minute of waiting):
Secure Connection Failed
An error occurred during a connection to bugs.freebsd.org.
The page you are trying to view cannot be shown because the
Sorry for the noise; I see (now) that
author Jan Beich 2022-11-26 14:01:23 +
committer Jan Beich 2022-11-26 14:17:10
+
commit 4b211242030e4160d54bd302770c253c5392d2ee (patch)
devel/glib20: unbreak some C++ consumers after 27fe5eff9577
should address the issues I noted.
Peace,
I note that the devel/glib20 port was just updated from 2.74.1 to
2.74.2 recently.
Ports that failed to build were graphics/gegl and net/wireshark.
Copies of logs are in
https://www.catwhisker.org/~david/FreeBSD/ports/2022-11-26/
Those for stable/12 are in the "12" subdirectory; similarly for "1
On Thu, Nov 24, 2022 at 10:22:01AM -0500, Michael Jung wrote:
> ...
> As of 2022-11-24 ~10:00 AM EST if you have /usr/ports made using
> portsnap or poudriere tracking main
> ...
> poudriere:
>
> ===> apache24-2.4.54 : Error from apache.mk. WITH(OUT)_MODULES has been
> removed, use www_apache2
On Thu, Nov 10, 2022 at 12:15:31PM +0100, Thierry Thomas wrote:
> Hello,
>
> Trying to run poudriere (bulk or testport) fails with this error:
>
> [00:00:05] Error: Dependency loop detected:
> These packages depend on each other: libgd-2.3.3_3,1 libavif-0.11.1 aom-3.5.0
> libjxl-0.7.0 openexr-3.
On Sun, Sep 25, 2022 at 11:30:07PM -0300, Nilton Jose Rizzo wrote:
> Hi all,
>
> I'm updated my box to last 14-current today and I get error on ports
> compialtion.
>
Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266561
Peace,
david
--
David H. Wolfskill
On Sun, Sep 11, 2022 at 02:08:24PM -0700, David Wolfskill wrote:
> On Sun, Sep 11, 2022 at 07:21:16PM +0200, Jan Beich wrote:
> > David Wolfskill writes:
> >
> > > | Adding test "reftest wrapping-in-boxes-in-boxes.ui"
> > > | Program python
On Sun, Sep 11, 2022 at 07:21:16PM +0200, Jan Beich wrote:
> David Wolfskill writes:
>
> > | Adding test "reftest wrapping-in-boxes-in-boxes.ui"
> > | Program python3 (gi) found: NO
> > |
> > | testsuite/introspection/meson.build:1:0: ERROR: python3 is m
On Sun, Sep 11, 2022 at 06:28:35PM +0300, Dima Panov wrote:
>
> Just curious -- did you rebuild/reinstall *ALL* 'py3*-*' modules after
> bump default python from 3.8 to 3.9?
>
Not sure -- that was a while back, and I only keep build typescripts for
a limited time.
In any case, given t
On Sun, Sep 11, 2022 at 05:47:31PM +0300, Dima Panov wrote:
> Moin!
>
> On 11.09.2022 17:04, David Wolfskill wrote:
> > ...
> > The tail end of that "full log" reads:
> >
> > | Adding test "reftest wrapping-in-boxes-in-boxes.ui"
>
Of my "development" machines, one is a headless "build machine" and the
other two are laptops (one around 10 years old that I'm trying to
retire; the other only about 6 years old that I'm trying to be able to
use the way I can the older one -- but that;s tangential to the issue at
hand).
The build
On Sat, Sep 10, 2022 at 09:00:36PM +0200, Muhammad Moinur Rahman wrote:
> ...
> So far I cannot reproduce this.
>
> http://pdr.bofh.network/data/latest-per-pkg/tex-web2c/20210325/131-default.log
After the "poudriere bulk" completed, I re-ran it (without changing the
ports tree or the underlying s
This is on my "build machine," presently running:
FreeBSD freebeast.catwhisker.org 13.1-STABLE FreeBSD 13.1-STABLE #161
stable/13-n252375-3f4e44f38c9: Sat Sep 10 11:25:03 UTC 2022
r...@freebeast.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 1301507 1301507
with a port
On Fri, Aug 26, 2022 at 04:06:39PM +0200, Jan Beich wrote:
> ...
> Disable LTO_BOOTSTRAP port option or see
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254
Good to know; thanks.
In any case, one of the laptops finished OK (after having increased
tmpfs to 8G). (I had needed to suspend
Saw this on a couple of laptops, each of which is configured to use a
swap-backed tmpfs for /tmp -- started at 2G, which didn't work so well.
Looks as if they are over the worst of it, and I've seen /tmp/get to
4.8G used -- in cdase this helps someone else avoid some of the hassle.
(This was amd6
On Wed, Aug 17, 2022 at 09:05:06PM -0400, Jesús Daniel Colmenares Oviedo wrote:
> ...
> But you are using DNS.
Of course.
> Can you try to reproduce the problem without DNS?
Probably not: I have booted the machine in environments where there is
no PTR record for the IP address; no issues.
> I
On Wed, Aug 17, 2022 at 06:06:33PM -0400, Jesús Daniel Colmenares Oviedo wrote:
> ...
> You need an entry in /etc/hosts for each display name in `xauth list`.
> Look at my /etc/hosts:
>
> ```
> $ egrep '^[^#]' /etc/hosts
> ::1 localhost localhost.my.domain
> 127.0.0.1 localhost localhost.my.domain
f email messages (in this thread) from
Martin Waschbüsch, Moin Rahman, and Brooks Davis.
Specifically, the last-cited message:
| Date: Fri, 12 Aug 2022 21:08:42 +0000
| From: Brooks Davis
| To: David Wolfskill
| Cc: freebsd-po...@freebsd.org
| Subject: Re: devel/llvm13 build: "ninja: bu
On Fri, Aug 12, 2022 at 09:08:42PM +, Brooks Davis wrote:
> An ill-advised update was made to textproc/py-sphinx-markdown-tables which
> broke llvm13 and later. Hopefully it will be reverted soon.
>
> -- Brooks
>
Just a confirmation that a local
git revert 5a0fd27b2f9b47b120800
On Fri, Aug 12, 2022 at 09:08:42PM +, Brooks Davis wrote:
> An ill-advised update was made to textproc/py-sphinx-markdown-tables which
> broke llvm13 and later. Hopefully it will be reverted soon.
>
> -- Brooks
>
Ah -- thanks. That provides me with enough clue to work something out,
I
This was using poudriere, on a real amd64 machine with:
Aug 12 04:13:35 freebeast kernel: real memory = 206152138752 (196602 MB)
Aug 12 04:13:35 freebeast kernel: avail memory = 200736665600 (191437 MB)
in both:
FreeBSD 12.3-STABLE #89 stable/12-n235538-4291bca854b: Fri Aug 12 03:33:24 PDT
2022
On Mon, Aug 30, 2021 at 09:32:18AM -0700, Kevin Bowling wrote:
> On Sun, Aug 29, 2021 at 1:36 PM David Wolfskill wrote:
> >
> > On Sun, Aug 29, 2021 at 01:32:19PM -0700, Kevin Bowling wrote:
> > > See if it is reproducible with a 13 or main kernel, there is a locking
>
It doesn't seem to cause a real "problem," but... it doesn't look
quite ideal, either:
E.g.:
g1-48(12.2-S)[1] cd /usr/ports/www/chromium/
g1-48(12.2-S)[2] make showconfig
make: "/common/ports/www/chromium/Makefile" line 210: warning: "/usr/bin/grep
mempcpy /usr/include/string.h" returned non-zero
On Mon, Aug 30, 2021 at 09:32:18AM -0700, Kevin Bowling wrote:
> On Sun, Aug 29, 2021 at 1:36 PM David Wolfskill wrote:
> >
> > On Sun, Aug 29, 2021 at 01:32:19PM -0700, Kevin Bowling wrote:
> > > See if it is reproducible with a 13 or main kernel, there is a locking
>
On Sun, Aug 29, 2021 at 01:32:19PM -0700, Kevin Bowling wrote:
> See if it is reproducible with a 13 or main kernel, there is a locking change
> which may interact differently on the different branches so that would
> be a good thing to know. This may need nvidia help since the error
> seems to be
A few days ago, I returned home from a couple of weeks away (during
which I did not do my usual daily updates to FreeBSD & installed ports).
Yesterday, when I updated my main laptop's stable/12 environment, I
found that the machine did not initialize X11 (I use xdm) as expected;
rather, the screen
On Thu, Jun 17, 2021 at 01:53:26PM +0200, Jan Beich wrote:
> ...
> Force-remove mesa-libs then rebuild all its direct dependencies.
> libGL, libEGL, libGLESv2, etc. moved to libglvnd but libgbm, libglapi
> remained in mesa-libs, so some of the ports (e.g., mesa-dri, xorg-server,
> sdl2)
> would de
On Thu, Jun 17, 2021 at 04:04:07AM -0700, David Wolfskill wrote:
> ...
> So... at this point, I am unclear on how to make both x11/nvidia-driver
> and things from the above list like ... Web browsers (for example) able
> to coexist on the same system.
> ...
OK; I muddled throug
On my laptops, I have been using x11/nvidia-driver (quite successfully)
for several years.
As I update FreeBSD base and installed ports daily on those machines, I
have
PORTS_MODULES+=x11/nvidia-driver
in /etc/src.conf, so the kernel modules get rebuilt when the kernel
does; that has all worked q
60 matches
Mail list logo
