l] [-46dnqtv] command [[modifiers] args]
route: bad keyword: inet6
route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args]
route: bad keyword: inet6
route: usage: route [-j jail] [-46dnqtv] command [[modifiers] args]
Updating motd:.
Creating and/or trimming log files.
###
Why is it erroring for ipv6 when theres no ipv6 in rc.conf?
I've not tried an amd64 -current system yet.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921
Mark Linimon changed:
What|Removed |Added
Flags|mfc-stable12?, |
|mfc-stable11?
On 29/12/2023 05:46, Christopher Davidson wrote:
Hi FreeBSD mailing list,
I have recently started to look at the CURRENT isos, for installation in
a virtualbox, and while trying to install these images I have received
verification issues with the checksums.
Problem: FreeBSD installer will
Hi FreeBSD mailing list,
I have recently started to look at the CURRENT isos, for installation in a
virtualbox, and while trying to install these images I have received
verification issues with the checksums.
Problem: FreeBSD installer will error out of the installer upon verification of
, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Santiago
It might be useful to know:
* What you are running at the time;
* what the most recent c
ithout a problem ( just in case).
Thanks.
Santi
On 12/28/23 16:23, David Wolfskill wrote:
On Thu, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Sant
On Thu, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
> Hi Everyone, I'm having issues building world from current (just now).
>
> Same header missing on multiple parts.
>
> Best regards.
>
> Santiago
>
It might be useful to know:
* What you ar
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Santiago
"""
In file included from
/usr/src/contrib/llvm-project/llvm/lib/Demangle/ItaniumDemangle.cpp:13:
In file included from
/usr/src/contr
Dimitry Andric writes:
> henry vogt writes:
> > ===> usr.sbin/zic (obj,all,install)
> > Building /usr/obj/usr/src/13.2/amd64.amd64/tmp/obj-tools/usr.sbin/zic/zic.o
> > --- zic.o ---
> > /usr/src/13.2/contrib/tzcode/zic.c:464:8: error: an attribute list cannot
> > appear here
> > 464 | static A
On 13 Dec 2023, at 13:08, henry vogt wrote:
>
> attempt to compile 13.2p8 on a recent current fails: compiler issue ?
>
> ...
>
> ===> usr.sbin/zic (obj,all,install)
> Building /usr/obj/usr/src/13.2/amd64.amd64/tmp/obj-tools/usr.sbin/zic/zic.o
> --- zic.o ---
>
Hi
attempt to compile 13.2p8 on a recent current fails: compiler issue ?
...
===> usr.sbin/zic (obj,all,install)
Building /usr/obj/usr/src/13.2/amd64.amd64/tmp/obj-tools/usr.sbin/zic/zic.o
--- zic.o ---
/usr/src/13.2/contrib/tzcode/zic.c:464:8: error: an attribute list
cannot appear h
On Nov 29, 2023, at 12:21 PM, Manoel Games wrote:
>
> I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I update the
> FreeBSD-CURRENT kernel, and is it done through pkg? I installed
> FreeBSD-CURRENT without src.
As a new user you should probably run a supported rel
I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I update the
FreeBSD-CURRENT kernel, and is it done through pkg? I installed FreeBSD-CURRENT
without src.
Gary Jennejohn asks:
Did you do a clean build? This isn't mentioned in the "To rebuild
everything" text, but since you're building a different branch I
suspect that a clean build would be necessary.
Define "clean build".
The script for rebuilding world has both "make cleanworld" and
On Tue, 28 Nov 2023 12:01:47 -0500
Robert Huff wrote:
> Hello:
> I am trying to update a system running "14.0 CURRENT #0" to last
> night's Current using source.
> I read the RELNOTES; I read the directions in UPDATING under "To
> rebuild everyt
Hello:
I am trying to update a system running "14.0 CURRENT #0" to last
night's Current using source.
I read the RELNOTES; I read the directions in UPDATING under "To
rebuild everything".
I built world; built kernel; installed kernel; rebooted single
us
On 13/10/2023 07:46, Toomas Soome wrote:
On 13. Oct 2023, at 09:35, void wrote:
On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote:
Set also vfs.zfs.arc.min to some value higher than zero.
aha! that worked!!! :D
root@beer:/root# sysctl vfs.zfs.arc.min=1073741824
vfs.zfs.arc.min:
On Fri, Oct 13, 2023 at 09:46:08AM +0300, Toomas Soome wrote:
That is a bit odd, arc min used to be 64MB as lowest value - that is, it should
never be 0.
It was the default here (i.e. the value wasn't set in either loader.conf or
sysctl.conf)
world+kernel was built/installed today the 13th m
> On 13. Oct 2023, at 09:35, void wrote:
>
> On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote:
>
>> Set also vfs.zfs.arc.min to some value higher than zero.
>
> aha! that worked!!! :D
>
> root@beer:/root# sysctl vfs.zfs.arc.min=1073741824
> vfs.zfs.arc.min: 0 -> 1073741824
> roo
On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote:
Set also vfs.zfs.arc.min to some value higher than zero.
aha! that worked!!! :D
root@beer:/root# sysctl vfs.zfs.arc.min=1073741824
vfs.zfs.arc.min: 0 -> 1073741824
root@beer:/root# sysctl vfs.zfs.arc.max=8589934592
vfs.zfs.arc.max:
> On 13 Oct 2023, at 00:59, void wrote:
>
>> Try reducing your arc.max by an order of 10. This suggests that it's
>> probably failing in param_set_arc_max() in the val >= arc_all_memory()
>> comparison..
>
> Hi, thanks for replying. Sadly, your suggestion doesn't work in this case:
>
> root@
On Thu, Oct 12, 2023 at 11:27:49AM -0700, Cy Schubert wrote:
In message , void writes:
Is there a new way to set arc.max in 15-current?
It's no longer settable (except to "0") in main-n265801 (Oct 7th)
while multiuser.
# sysctl vfs.zfs.arc.max=8589934592
vfs.zfs.ar
In message , void writes:
> Is there a new way to set arc.max in 15-current?
>
> It's no longer settable (except to "0") in main-n265801 (Oct 7th)
> while multiuser.
>
> # sysctl vfs.zfs.arc.max=8589934592
> vfs.zfs.arc.max: 0
> sysctl: vfs.zfs.arc.max=858
Is there a new way to set arc.max in 15-current?
It's no longer settable (except to "0") in main-n265801 (Oct 7th)
while multiuser.
# sysctl vfs.zfs.arc.max=8589934592
vfs.zfs.arc.max: 0
sysctl: vfs.zfs.arc.max=8589934592: Invalid argument
--
Envoyé de mon iPhone
Début du message transféré :
> De: Jean-Loups
> Date: 1 octobre 2023 à 00:45:25 UTC+2
> À: freebsd-current+subscr...@freebsd.org
> Objet: FreeBSD 15 current for MAO
>
> Hello,
> I try to do work station for audio editing and video editing for YouTu
Envoyé de mon iPhone
Début du message transféré :
> De: Jean-Loups
> Date: 1 octobre 2023 à 00:45:25 UTC+2
> À: freebsd-current+subscr...@freebsd.org
> Objet: FreeBSD 15 current for MAO
>
> Hello,
> I try to do work station for audio editing and video editing for YouTu
Am 2023-09-10 18:53, schrieb Robert Clausecker:
Hi Warner,
Thank you for your response.
Am Sun, Sep 10, 2023 at 09:53:03AM -0600 schrieb Warner Losh:
On Sun, Sep 10, 2023, 7:36 AM Robert Clausecker wrote:
> Hi Warner,
>
> I have pushed a fix. It should hopefully address those failing tests.
t;
> > > There are half a dozen or do kyua tests that are likely failing because
> > of
> > > this or other reasons related to strings. When you push this fix you'll
> > > get the list. They are hidden among about 80 or so networking tests that
> > &g
Warner Losh writes:
> As for memchr,
> https://pubs.opengroup.org/onlinepubs/009696799/functions/memchr.html
> has no such permission to examine 'the entire buffer at once' nor any
> restirction
> as to the length extending beyond the address space. I'm skeptical of your
> reading
> that it all
g about 80 or so networking tests that
> > fail. I plan on disabling those tests soon If no one fixes them.
> >
> > Warner
> >
> > >
> > > Yours,
> > > Robert Clausecker
> > >
> > > Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb
so networking tests that
> fail. I plan on disabling those tests soon If no one fixes them.
>
> Warner
>
> >
> > Yours,
> > Robert Clausecker
> >
> > Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Smørgrav:
> > > Antoine Brodin w
s,
> > Robert Clausecker
> >
> > Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Smørgrav:
> > > Antoine Brodin writes:
> > > > Yuri writes:
> > > > > Either something has changed in sed(1) in CURRENT, or sed just fails
> >
ne fixes them.
Warner
>
> Yours,
> Robert Clausecker
>
> Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Smørgrav:
> > Antoine Brodin writes:
> > > Yuri writes:
> > > > Either something has changed in sed(1) in CURRENT, or sed just fails
&
7;make
buildincludes' inside the buildenv before building libc. If that still
fails, just run buildworld; it will fail in libmagic as before but it
will have built libc before failing, and you can install libc and
restart the build.
DES
Yes, that works! Now I have a working, most recent 15.0-
e Brodin writes:
> > Yuri writes:
> > > Either something has changed in sed(1) in CURRENT, or sed just fails
> > > during the configure stage of textproc/jq:
> > >
> > > sed: No error: 0
> > > checking for sys/cygwin.h... eval: ${+...}: Bad substit
Rainer Hurling writes:
> Unfortunately, here it breaks with:
> [...]
> /usr/src/lib/libc/gdtoa/machdep_ldisx.c:40:10: fatal error: 'sys/cdefs.h'
> file not found
That's because you wiped /usr/obj before starting. Try running 'make
buildincludes' inside the buildenv before building libc. If tha
Am 09.09.23 um 20:28 schrieb Dag-Erling Smørgrav:
Rainer Hurling writes:
After removing /usr/obj and 'make cleanworld',
That was unnecessary.
I tried to build libc like the following, but it fails:
[...]
$ cd /usr/src
$ make buildenv
done
inside the buildenv, run:
$ make -C lib/libc
Rainer Hurling writes:
> After removing /usr/obj and 'make cleanworld',
That was unnecessary.
> I tried to build libc like the following, but it fails:
> [...]
$ cd /usr/src
$ make buildenv
inside the buildenv, run:
$ make -C lib/libc -j$(nproc)
then exit the buildenv and run
$ sudo make -C
Am 09.09.23 um 19:04 schrieb Dag-Erling Smørgrav:
Rainer Hurling writes:
If I try to build world from todays c1b26df2972d with 15.0-CURRENT
(main-n265063-e0752f431b01), it aborts with an error.
Either update your source tree or apply aca3bd160257, then build and
install libc before
Antoine Brodin writes:
> Yuri writes:
> > Either something has changed in sed(1) in CURRENT, or sed just fails
> > during the configure stage of textproc/jq:
> >
> > sed: No error: 0
> > checking for sys/cygwin.h... eval: ${+...}: Bad substitution
> This see
Rainer Hurling writes:
> If I try to build world from todays c1b26df2972d with 15.0-CURRENT
> (main-n265063-e0752f431b01), it aborts with an error.
Either update your source tree or apply aca3bd160257, then build and
install libc before attempting buildworld.
DES
--
Dag-Erling Smørgr
Just an update.
This also happens in Poudriere, when I try to update my jails for 13.2,
14.0 and 15.0-CURRENT.
It seems, that my installed version of 15.0-CURRENT
(main-n265063-e0752f431b01) is the culprit :(
Am 09.09.23 um 13:52 schrieb Rainer Hurling:
If I try to build world from todays
If I try to build world from todays c1b26df2972d with 15.0-CURRENT
(main-n265063-e0752f431b01), it aborts with an error.
Seems it is not able to handle line 4979 of the magic file (Microsoft
Advanced Streaming Format ASF):
===> lib/libmagic (all)
echo libmagic.so.4: /usr/obj/usr/src/am
On Sat, Sep 9, 2023 at 6:47 AM Yuri wrote:
>
> Either something has changed in sed(1) in CURRENT, or sed just fails
> during the configure stage of textproc/jq:
>
> sed: No error: 0
> checking for sys/cygwin.h... eval: ${+...}: Bad substitution
>
>
> See the log:
>
Either something has changed in sed(1) in CURRENT, or sed just fails
during the configure stage of textproc/jq:
sed: No error: 0
checking for sys/cygwin.h... eval: ${+...}: Bad substitution
See the log:
https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/peb032111a352_s9c80d66ec1
El día martes, septiembre 05, 2023 a las 03:24:30p. m. -0600, Warner Losh
escribió:
> On Tue, Sep 5, 2023 at 2:22 PM Steve Kargl
> wrote:
>
> > On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote:
> > > +/*
> > > + * Some Chromebooks don't confirm to the google comment above so
On Tue, Sep 5, 2023 at 2:22 PM Steve Kargl
wrote:
> On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote:
> > +/*
> > + * Some Chromebooks don't confirm to the google comment above so do
> the
>
> s/confirm/conform ?
>
>
> > + * Chromebook workaround for all <= 2018 coreboot s
On Tue, Sep 05, 2023 at 01:29:34PM -0600, Warner Losh wrote:
> +/*
> + * Some Chromebooks don't confirm to the google comment above so do the
s/confirm/conform ?
> + * Chromebook workaround for all <= 2018 coreboot systems that have a
> + * 'blank' version. At least once Acer "
Can you try this patch? (it's cut and paste inline, so if it fails, can you
apply it by hand... it's pretty straight forward)...
The reason is in the comments... Not 100% sure about using the version
being all spaces, though...
Nor the year 2018, honestly, but it beats having a longish list (see
h
El día martes, septiembre 05, 2023 a las 11:07:07a. m. -0600, Warner Losh
escribió:
> > https://cgit.freebsd.org/src/commit/?id=319d2bf407b3762da6f1c67ffe8dce2fee587aaf
> > > >
> > > > You could try to undo that patch and build a new kernel.
> > > >
> > > ...
>
> No. Let's see if I can puzzle ou
On Tue, Sep 5, 2023 at 12:13 AM Matthias Apitz wrote:
> El día lunes, septiembre 04, 2023 a las 12:10:56p. m. -0600, Warner Losh
> escribió:
>
> > On Mon, Sep 4, 2023, 11:40 AM Michael Gmelin wrote:
> >
> > > This could also be related:
> > >
> > >
> > >
> https://cgit.freebsd.org/src/commit/?id
El día lunes, septiembre 04, 2023 a las 12:10:56p. m. -0600, Warner Losh
escribió:
> On Mon, Sep 4, 2023, 11:40 AM Michael Gmelin wrote:
>
> > This could also be related:
> >
> >
> > https://cgit.freebsd.org/src/commit/?id=319d2bf407b3762da6f1c67ffe8dce2fee587aaf
> >
> > You could try to undo t
>
> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael
> Gmelin escribió:
>
>
>
>
> On Mon, 4 Sep 2023 18:43:11 +0200
>
> Matthias Apitz wrote:
>
>
> I have a 14.0-CURRENT compiled from sources of head from August 4,
>
> which boots fine
2fee587aaf
You could try to undo that patch and build a new kernel.
Best
Michael
>matthias
>
>>>> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael
>>>> Gmelin escribió:
>>>>
>>>>
>>>>
>>&g
this on it) r368166. Will file a PR
tomorrow. Thanks
matthias
> >> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael
> >> Gmelin escribió:
> >>
> >>
> >>
> >> On Mon, 4 Sep 2023 18:43:11 +0200
> >> Matthias A
ould you please Cc me on it?
Do you know which version of FreeBSD was the last that worked for you?
Cheers
>
>
>> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael Gmelin
>> escribió:
>>
>>
>>
>> On Mon, 4 Sep 2023 18:43:11 +020
:
>
>
> On Mon, 4 Sep 2023 18:43:11 +0200
> Matthias Apitz wrote:
>
> > I have a 14.0-CURRENT compiled from sources of head from August 4,
> > which boots fine from a produced USB key, but the keyboard does not
> > work on an Acer C720 (amd64), on other laptops the keyboa
On Mon, 4 Sep 2023 18:43:11 +0200
Matthias Apitz wrote:
> I have a 14.0-CURRENT compiled from sources of head from August 4,
> which boots fine from a produced USB key, but the keyboard does not
> work on an Acer C720 (amd64), on other laptops the keyboard is fine.
>
> The
I have a 14.0-CURRENT compiled from sources of head from August 4, which
boots fine from a produced USB key, but the keyboard does not work on an
Acer C720 (amd64), on other laptops the keyboard is fine.
The keyboard works during the boot menu (for example to enable verbose
boot messages) but
El día Freitag, August 18, 2023 a las 06:17:42 +0200, Matthias Apitz escribió:
>
> I was used to use in 13.0-CURRENT the script "make-memstick.sh" to
> create memstick immages to install the system on smaller devices where
> the OS can't build from the sources, and it
"John F Carr" writes:
> I had a problem yesterday and today rebuilding a -CURRENT system from
> source: [...] The cause was an sscanf call unexpectedly failing to
> parse the input. This caused the mkmagic program (internal tool used
> to build magic number table for fi
I had a problem yesterday and today rebuilding a -CURRENT system from source:
--- magic.mgc ---
./mkmagic magic
magic, 4979: Warning: Current entry does not yet have a description for
adding a MIME type
mkmagic: could not find any valid magic files!
The cause was an sscanf call
iere.
>>
>> Screenshot of console:
>> https://people.freebsd.org/~yasu/FreeBSD-15-CURRENT-amd64-main-n265022-1554ba03b65.20230825.panic.png
>>
>
> this is a fallout from the recent timerfd commit. I'll fix it in few.
>
fixed in
https://cgit.freebsd.org/src/commit/?id=02f534b57f84d6f4f97c337b05b383c8b3aaf18c
--
Mateusz Guzik
bsd.org/~yasu/FreeBSD-15-CURRENT-amd64-main-n265022-1554ba03b65.20230825.panic.png
>
this is a fallout from the recent timerfd commit. I'll fix it in few.
--
Mateusz Guzik
Hello,
I made regular update of my amd64 system from main-n264870-e5e6a865358
to main-n265022-1554ba03b65 and system crashed with panic while
building packages with poudriere.
Screenshot of console:
https://people.freebsd.org/~yasu/FreeBSD-15-CURRENT-amd64-main-n265022-1554ba03b65.20230825
I filed this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273211
about the issue.
El día viernes, agosto 18, 2023 a las 06:17:42p. m. +0200, Matthias Apitz
escribió:
>
> I was used to use in 13.0-CURRENT the script "make-memstick.sh" to
> create memstick imm
I was used to use in 13.0-CURRENT the script "make-memstick.sh" to
create memstick immages to install the system on smaller devices where
the OS can't build from the sources, and it always worked fine for many
years. Now I'm ready to do so with my fresh compiled system (sou
Am 2023-08-15 14:24, schrieb Alexander Leidinger:
Am 2023-08-15 13:48, schrieb Alexander Leidinger:
since a while I have some strange network issues in some parts of a
particular system.
I just stumbled upon the mail which discusses issues with commit
e3ba0d6adde3, and when I look into this
El día martes, agosto 15, 2023 a las 09:39:56p. m. +0900, Tomoaki AOKI escribió:
> On Tue, 15 Aug 2023 08:35:01 +0200
> Matthias Apitz wrote:
>
> >
> > The port www/firefox stops to build in congigure phase with:
> >
> > DEBUG: Executing: `/usr/bin/clang -std=gnu99 --target=wasm32-wasi
> > /t
On Tue, 15 Aug 2023 21:39:56 +0900
Tomoaki AOKI wrote:
> On Tue, 15 Aug 2023 08:35:01 +0200
> Matthias Apitz wrote:
>
> >
> > The port www/firefox stops to build in congigure phase with:
> >
> > DEBUG: Executing: `/usr/bin/clang -std=gnu99 --target=wasm32-wasi
> > /tmp/conftest._vo3qtm2.c -c
On Tue, 15 Aug 2023 08:35:01 +0200
Matthias Apitz wrote:
>
> The port www/firefox stops to build in congigure phase with:
>
> DEBUG: Executing: `/usr/bin/clang -std=gnu99 --target=wasm32-wasi
> /tmp/conftest._vo3qtm2.c -c`
> DEBUG: The command returned non-zero exit status 1.
> DEBUG: Its erro
Am 2023-08-15 13:48, schrieb Alexander Leidinger:
since a while I have some strange network issues in some parts of a
particular system.
I just stumbled upon the mail which discusses issues with commit
e3ba0d6adde3, and when I look into this I see changes related to the use
of SO_REUSEPORT f
Hi,
since a while I have some strange network issues in some parts of a
particular system.
A build with src from 2023-07-26 was still working ok. An update to
2023-08-07 broke some parts in a strange way. I tried again with src
from 2023-08-11 didn't fix things.
What I see is... strange an
gt; ---End OPTIONS List---
>
> --MAKE_ENV--
> OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include
> OPENSSLLIB=/usr/lib ...
>
> There is a similar, but closed PR:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254323
>
I've unset PKCS11 in the port'
From: Matthias Apitz
Subject: security/openvpn does not compile in 14-CURRENT w/ poudriere
Date: Tue, 15 Aug 2023 08:16:38 +0200
>
> security/openvpn fails to build with an error message in the log:
>
> ...
> libc.so.7
> libcrypto.so.11
> libcrypto.so.30
> libdl.so.1
&g
The port www/firefox stops to build in congigure phase with:
DEBUG: Executing: `/usr/bin/clang -std=gnu99 --target=wasm32-wasi
/tmp/conftest._vo3qtm2.c -c`
DEBUG: The command returned non-zero exit status 1.
DEBUG: Its error output was:
DEBUG: | error: unable to create target: 'No available tar
security/openvpn fails to build with an error message in the log:
...
libc.so.7
libcrypto.so.11
libcrypto.so.30
libdl.so.1
liblz4.so.1
liblzo2.so.2
libnv.so.1
libpkcs11-helper.so.1
libssl.so.11
libthr.so.3
/usr/ports/security/openvpn FAILED: either of libssl libcrypto libraries linked
multiple
Resent. Not yet sent from ML but later one was sent.
Adding @freebsd.org address of Enji, as gmail does not accept mails
from dec.sakura.ne.jp, which has neither DKIM functionality nor SPF
record.
On Thu, 10 Aug 2023 16:32:32 -0700
Enji Cooper wrote:
> > On Aug 10, 2023, at 4:00 PM, Tomoaki AOKI
On Thu, 10 Aug 2023 18:09:54 -0400
Charlie Li wrote:
> Enji Cooper wrote:
> > Hmm… All lang/python27 requiring ports should be marked BROKEN and
> > removed — upstream stopped supporting 2.7 3.5 years ago (04/01/2020) :/.
> We can't entirely do that yet. Unfortunately, moinmoin, original mailman
Enji Cooper wrote:
Hmm… All lang/python27 requiring ports should be marked BROKEN and
removed — upstream stopped supporting 2.7 3.5 years ago (04/01/2020) :/.
We can't entirely do that yet. Unfortunately, moinmoin, original mailman
and the CSM for UEFI-EDK2 (used in bhyve) still staunchly requir
> On Aug 10, 2023, at 2:56 PM, Matthias Apitz wrote:
…
> Don't know if I can answer your questions. I'm building ports with
> poudriere and lang/python27 is pulled in from some other ports. The port
> lang/python27 itself is not on my list for poudriere:
>
> # grep python /usr/local/etc/poudri
ctly builds on the latest HEAD without any problem as shared in
> >> my build log. I am not sure what is wrong at your end. Neither can I see
> >> any fallout on the clusters.
> >
> > I've cc'ed freebsd-current@
> >
> > I did two times the build
at your end. Neither can I see any
>> fallout on the clusters.
>
> I've cc'ed freebsd-current@
>
> I did two times the building of lang/python27 within poudriere on
> 14.0-CURRENT:
>
> =>> Building lang/python27
> build started at Tue Aug 8 04:05
thout any problem as shared in
> >> my build log. I am not sure what is wrong at your end. Neither can I see
> >> any fallout on the clusters.
> >>
> >
> > I've cc'ed freebsd-current@
> >
> > I did two times the building of lang/p
Neither can I see any
>> fallout on the clusters.
>>
>
> I've cc'ed freebsd-current@
>
> I did two times the building of lang/python27 within poudriere on
> 14.0-CURRENT:
>
> =>> Building lang/python27
> build started at Tue Aug 8 04:05:20 CEST
El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman escribió:
> This perfectly builds on the latest HEAD without any problem as shared in my
> build log. I am not sure what is wrong at your end. Neither can I see any
> fallout on the clusters.
>
I've cc&#
query belonged in ports@ for the following reasons:
1. the question wasn't about a port problem or a PR
2. development happens on -current primarily
3. the system it concerns is running -current
When everything in ports supports Qt6. Once Plasma6 arrives Qt5 may
start to dilapidate and be
Please, use ports@ list next time. Every supported FreeBSD version uses
the same ports/ tree. Not supported FreeBSD versions require a time
machine i.e., rolling back the ports/ tree to a date before EOL.
void writes:
> How can I build making qt6 the default Qt?
When everything in ports support
Hello list,
How can I build making qt6 the default Qt?
I'm using poudriere to build. I can see that for some ports there's a
'uses: qt6' that goes in the port. What I was looking for was a default
string I can use with a poudriere make.conf like there is for python or
perl.
ty
--
Dag-Erling Smørgrav wrote:
> Michael Grimm writes:
>> I'm currently in the process to prepare for upcoming 14-STABLE. Thus,
>> I upgraded one of my sytems from 13-STABLE to 14-CURRENT.
>
> Did you run etcupdate?
I was just about to report that I somehow managed
Michael Grimm writes:
> I'm currently in the process to prepare for upcoming 14-STABLE. Thus,
> I upgraded one of my sytems from 13-STABLE to 14-CURRENT.
Did you run etcupdate?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Van: Michael Grimm
Datum: maandag, 7 augustus 2023 22:43
Aan: freebsd-current@freebsd.org
Onderwerp: 14-CURRENT | alternatives for defunct /usr/lib/pam_opie.so?
Hi,
I'm currently in the process to prepare for upcoming 14-STABLE. Thus, I
upgraded one of my sytems from 13-STABLE to 14-CU
Michael Grimm wrote on
Date: Mon, 07 Aug 2023 20:43:22 UTC :
> I'm currently in the process to prepare for upcoming 14-STABLE. Thus, I
> upgraded one of my sytems from 13-STABLE to 14-CURRENT.
>
> Everything went fine, except for programs that need /usr/lib/pam_opie.so
&g
James Gritton wrote:
> On 2023-08-07 13:29, Dimitry Andric wrote:
>> On 7 Aug 2023, at 04:50, Yoshihiro Ota wrote:
>>>
>>> Am I the only one seeing this error?
>>> I'm on 12.4-RELEASE amd64 and building CURRENT as of now.
>>>
>>> jaillex.
On 2023-08-07 13:29, Dimitry Andric wrote:
On 7 Aug 2023, at 04:50, Yoshihiro Ota wrote:
Am I the only one seeing this error?
I'm on 12.4-RELEASE amd64 and building CURRENT as of now.
jaillex.c:2228:43: error: unused parameter 'yyscanner'
[-Werror,-Wunused-parameter]
Hi,
I'm currently in the process to prepare for upcoming 14-STABLE. Thus, I
upgraded one of my sytems from 13-STABLE to 14-CURRENT.
Everything went fine, except for programs that need /usr/lib/pam_opie.so which
are:
1) jexec /usr/bin/login -u
2) redis-server
3) mariadb1011-server
On 7 Aug 2023, at 04:50, Yoshihiro Ota wrote:
>
> Am I the only one seeing this error?
> I'm on 12.4-RELEASE amd64 and building CURRENT as of now.
>
> jaillex.c:2228:43: error: unused parameter 'yyscanner'
> [-Werror,-Wunused-parameter]
> void *yyalloc (
Hi,
Am I the only one seeing this error?
I'm on 12.4-RELEASE amd64 and building CURRENT as of now.
jaillex.c:2228:43: error: unused parameter 'yyscanner'
[-Werror,-Wunused-parameter]
void *yyalloc (yy_size_t size , yyscan_t yyscanner)
^
Building -CURRENT (2023-07-17 be4c7f273508) without system compiler (with
LLVM16 from ports) results in unbootable system:Preloaded elf kernel
"/boot/kernel/kernel" at 0x82328000.
Preloaded elf obj module "/boot/kernel/zfs.ko" at 0x82329090.
Preloaded boot_
Greetings, thanks for all of your all’s work. I have a laptop I run FBSD on
with the following:
I7-10510u with an AX201.
So far, everything works though I haven’t tried to get the finger print
reader working.
Basically Friday, I synced the current tree, cleaned up the no debug kernel
file, then
101 - 200 of 14584 matches
Mail list logo
