/report-sample.adoc>.
We look forward to seeing your 2024Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2024Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2024Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
ones are not always met. Indeed, if
you are not a FreeBSD contributor yet, please consider joining us: you could
help lighten someone’s burden while learning new skills, working side by side
with developers all over the world.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
ones are not always met. Indeed, if
you are not a FreeBSD contributor yet, please consider joining us: you could
help lighten someone’s burden while learning new skills, working side by side
with developers all over the world.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
ones are not always met. Indeed, if
you are not a FreeBSD contributor yet, please consider joining us: you could
help lighten someone’s burden while learning new skills, working side by side
with developers all over the world.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
On Tuesday, September 24th, 2024 at 13:22, Lorenzo Salvadore
wrote:
>
>
> On Tuesday, September 17th, 2024 at 18:43, Mark Millard mark...@yahoo.com
> wrote:
>
> > For example,
> >
> > https://lists.freebsd.org/archives/freebsd-pkg-fallout/2024-Septe
examples, starting when
> the armv7 jails on ampere2 were updated to a vintage that had
> the fix for that more overall problem for main.)
Thanks for your report. Does the attached patch fix the issue?
Cheers,
Lorenzo SalvadoreFrom 1f1cbc1717c338b4611a7379ef8b09d2ed4a4076 Mo
/report-sample.adoc>.
We look forward to seeing your 2024Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2024Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2024Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
, thus some reports arrived late
and report publication was slower than usual. Hopefully, this quarter was an
exception and next quarter we will already be back on track, with 2024Q3 report
published within October 2024.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
, thus some reports arrived late
and report publication was slower than usual. Hopefully, this quarter was an
exception and next quarter we will already be back on track, with 2024Q3 report
published within October 2024.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
, thus some reports arrived late
and report publication was slower than usual. Hopefully, this quarter was an
exception and next quarter we will already be back on track, with 2024Q3 report
published within October 2024.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
ple.adoc>.
We look forward to seeing your 2024Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
ple.adoc>.
We look forward to seeing your 2024Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
ple.adoc>.
We look forward to seeing your 2024Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
ooks like that there is not much interest in saving those
translations, so they will probably just die... It is a pity, I believe
localization is important, but FreeBSD is a voluntary project: if no
one would like to work on it, nobody will work on it.
Cheers,
Lorenzo Salvadore
le-initfini-array configure option.
Indeed, support for .init_array and .fini_array has been added to the GCC ports
but is present in the *-devel ports only for now. I will
soon proceed to enable it for the GCC standard ports too. lang/gcc14 is soon
to be added to the ports tree and will have it since the beginning.
If this is indeed the issue, switching to a -devel GCC port should fix it.
Cheers,
Lorenzo Salvadore
our OS more user-friendly. Of
course, the usual projects keep going on, such as the work on cloud-init,
OpenStack, or the GCC ports. As usual our main teams share their progress with
us.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
our OS more user-friendly. Of
course, the usual projects keep going on, such as the work on cloud-init,
OpenStack, or the GCC ports. As usual our main teams share their progress with
us.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
our OS more user-friendly. Of
course, the usual projects keep going on, such as the work on cloud-init,
OpenStack, or the GCC ports. As usual our main teams share their progress with
us.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team
lopers do try to upstream a patch, but fail. This
happened to myself in GCC too, when I was unable to get any
attention to a patch I submitted, and could not do any better
than keep the patch into the FreeBSD ports collection:
https://gcc.gnu.org/pipermail/jit/2023q3/001642.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491#c5
If you are able to help with this upstreaming, I would appreciate
it a lot. Thanks.
Cheers,
Lorenzo Salvadore
lang/gcc11-devel/.cirrus.yml
By the way, is it possible for FreeBSD to enter GCC's CI pipeline? Where
would one start? I am willing to help of course.
Cheers,
Lorenzo Salvadore
t-sample.adoc>.
We look forward to seeing your 2024Q1 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
t-sample.adoc>.
We look forward to seeing your 2024Q1 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
t-sample.adoc>.
We look forward to seeing your 2024Q1 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
and reports tend to arrive later. But
finally, here they are.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org/status
and reports tend to arrive later. But
finally, here they are.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org/status
and reports tend to arrive later. But
finally, here they are.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org/status
pdate for lang/gcc12 failed
> ===>>> Aborting update
>
Are you trying to build the port with MULTILIB option enabled on a
self-compiled host with WITHOUT_LIB32 enabled? Try disabling MULTILIB.
Cheers,
Lorenzo Salvadore
touched this block
of code since I took the GCC ports maintainership yet. We can
probably add MULTILIB for aarch64 too and I will check into it
as soon as possible.
Cheers,
Lorenzo Salvadore
pecifics for
> building lang/gcc14-devel .)
>
> I expect that slavadore will pick a notation that
> is sufficient for the builds to work.
Thanks for the suggestion. lang/gcc14-devel is having multiple
issues at the moment (and I still need to finish the GCC_DEFAULT
update to GCC 13 exp-run), so I might need a bit of time to fix
this one, but I will definitely have a look into this as soon as
possible.
Thanks,
Lorenzo Salvadore
/report-sample.adoc>.
We look forward to seeing your 2023Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2023Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2023Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
. But the free cirrus plan is good enough for small ports.
Cheers,
Lorenzo Salvadore
Sent from Proton Mail mobile
Messaggio originale
Il 1 Dic 2023, 01:25, Pat Maddox ha scritto:
> According to portscout, there are three individual maintainers who each
> maintain 1000+
/report-sample.adoc>.
We look forward to seeing your 2023Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
hich software I used, maybe binwalk), I put it on a
usb key and finally I installed it using the utility in the motherboard,
available when powering the computer, before booting windows.
Cheers,
Lorenzo Salvadore
important work has been done for
the first release of FreeBSD 14.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org
important work has been done for
the first release of FreeBSD 14.
Have a nice read.
Lorenzo Salvadore, on behalf of the Status Team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org
default should produce
more stable official packages (I have not checked: GCC ports are
very complex to maintain and I have lots of higher priorities
issues to solve). Again, users are free to disable
the option if they want faster builds and do not need any bootstrap.
Cheers,
Lorenzo Salvadore
582364160
Please let me know what are the results of your tests. Then we
will see if the issue needs more research or not. It might be
that some test is being made and is expected to fail.
In case we need to work on this, I suggest to file a bug report in bugzilla.
Cheers,
Lorenzo Salvadore
maintaining them at the moment.
Cheers,
Lorenzo Salvadore
Sent from Proton Mail mobile
Messaggio originale
Il 18 Ott 2023, 16:33, Miroslav Lachman ha scritto:
> Hi, I am running FreeBSD 13.2 amd64 with quarterly 2023Q4 packages for my
> desktop. I cannot run Wine applications
/report-sample.adoc>.
We look forward to seeing your 2023Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
/report-sample.adoc>.
We look forward to seeing your 2023Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
t; Dag-Erling Smørgrav - d...@freebsd.org
> > >
> >
> > --
> > () ascii ribbon campaign - for an 8-bit clean world
> > /\ - against html email - against proprietary attachments
> >
The issue seems to also affect lang/gcc14-devel:
https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/pe88937b01dd4_s3482f57f0f/logs/gcc14-devel-14.0.0.s20230903.log
Cheers,
Lorenzo Salvadore
/report-sample.adoc>.
We look forward to seeing your 2023Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
Hello, I am the port maintainer.
It is a well known issue unfortunately. Just disable the LTO_BOOTSTRAP option
and the build will succeed.
Cheers,
Lorenzo Salvadore
Sent from Proton Mail mobile
Messaggio originale
Il 12 Ago 2023, 15:33, Matthias Apitz ha scritto:
>
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
I am pinging this since November, if this patch has something wrong please
just tell me so that I can fix it. The PR is still open.
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon
ple.adoc>.
We look forward to seeing your 2023Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
ple.adoc>.
We look forward to seeing your 2023Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
Thanks for the work and the update.
May I suggest to submit the update to 2023Q2 status reports too?
https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_submit_your_report
Cheers,
Lorenzo Salvadore
Inviato da Proton Mail mobile
Messaggio originale
Il 8 Giu
Thanks for the work and the update.
May I suggest to submit the update to 2023Q2 status reports too?
https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_submit_your_report
Cheers,
Lorenzo Salvadore
Inviato da Proton Mail mobile
Messaggio originale
Il 8 Giu
ple.adoc>.
We look forward to seeing your 2023Q2 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +0100
>
--- Original Message ---
On Wednesday, April 19th, 2023 at 4:26 PM, Lorenzo Salvadore
wrote:
> Last modified on: April 19, 2023 by Lorenzo Salvadore
>
> Legal Notices | © 1995-2023 The FreeBSD Project All rights reserved. The mark
> FreeBSD is a registered trademark of
--- Original Message ---
On Wednesday, April 19th, 2023 at 4:26 PM, Lorenzo Salvadore
wrote:
> Last modified on: April 19, 2023 by Lorenzo Salvadore
>
> Legal Notices | © 1995-2023 The FreeBSD Project All rights reserved. The mark
> FreeBSD is a registered trademark of
been covered in
past status reports.
Have a nice read.
Lorenzo Salvadore, on behalf of the status team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org/status/report-2023-01-2023-03
been covered in
past status reports.
Have a nice read.
Lorenzo Salvadore, on behalf of the status team.
━━━
A rendered version of this report is available here:
https://www.freebsd.org/status/report-2023-01-2023-03
uct also contains software developed by other people, etc" and
> > both are
> > defined in port by LICENSE definition and LICENSE_FILE that adds additional
> > info to license.
> >
> > LICENSE= BSD2CLAUSE
> > LICENSE_FILE= ${WRKSRC}/COPYING
>
file to include the acknowledgements
required by those additional licenses (or include them in some other way).
Cheers,
Lorenzo Salvadore
> On 09/04/23 20:29, Nuno Teixeira wrote:
>
> > Hello to all,
> >
> > I'd like to define a license for ftp/tnftp from NetBSD and not sure if
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
--- Original Message ---
On Saturday, April 1st, 2023 at 11:33 AM, Gary Jennejohn wrote:
>
>
> On Sat, 01 Apr 2023 08:01:26 +
> Lorenzo Salvadore develo...@lorenzosalvadore.it wrote:
>
> > --- Original Message ---
> > On Saturday, April 1st, 2
t is good to see that Charlie is finally getting the status he deserves.
>
>
> Agreed. He's had an account on each of my systems here for years. Can't
> work without him.
I assume the toor@ we are all welcoming is the standard toor account on
FreeBSD and not a new contributor with a funny username, am I correct?
If yes, could anyone please explain why toor@ needs access to any git
repository? What problem does it solve?
Thanks,
Lorenzo Salvadore
The branch main has been updated by salvadore:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a756181cea9ee7426f164a0b1783d283b8ab19c8
commit a756181cea9ee7426f164a0b1783d283b8ab19c8
Author: Lorenzo Salvadore
AuthorDate: 2023-03-24 11:58:35 +
Commit: Lorenzo Salvadore
CommitDate
The branch main has been updated by salvadore:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a756181cea9ee7426f164a0b1783d283b8ab19c8
commit a756181cea9ee7426f164a0b1783d283b8ab19c8
Author: Lorenzo Salvadore
AuthorDate: 2023-03-24 11:58:35 +
Commit: Lorenzo Salvadore
CommitDate
adoc .
We look forward to seeing your 2023Q1 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
adoc .
We look forward to seeing your 2023Q1 reports!
Thanks,
Lorenzo Salvadore (on behalf of status@)
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
ound candidate GCC installation: /usr/bin/../lib/gcc/aarch64-redhat-linux/12
> Selected GCC installation: /usr/bin/../lib/gcc/aarch64-redhat-linux/12
> Candidate multilib: .;@m64
> Selected multilib: .;@m64
>
> If I understand right, Lorenzo indicates that he has
> more failing contexts. I've no evidence of my own of
> such.
I am sorry, I was in a hurry and I read Mark's email too
quickly. Then now I have stopped, read more carefully,
rerun the tests and everything works as intended instead.
So, the testcode works correctly at all optmization levels
on FreeBSD amd64 and Linux OpenSuse amd64, at least on my
machine.
I am sorry for my mistake.
Cheers,
Lorenzo Salvadore
if you disable it you do use -O2.
I have taken your example C code and tested it in
FreeBSD amd64 and in a virtual machine running Linux
(OpenSuse) amd64: I have got the same failure
in both cases. I used clang15. So the bug does not
depend on the OS nor on the architecture.
However, my results have a difference from yours:
in my case tests fail with any level of optimization.
At this point, I would say that the issue is in clang.
I think you should file a bug upstream.
Thanks,
Lorenzo Salvadore
he component that causes the issue and if replacing anything
with something newer (where the bug might be already fixed) or with
something supported (since FreeBSD CURRENT is under development, we
might have regressions) solves the problem.
If you find that the cause is in the FreeBSD GCC port(s), then please
open a bug report on bugzilla so that I can keep track of it and other
users with the same problem can find it there as well.
Thanks,
Lorenzo Salvadore
s!
Thanks,
Lorenzo Salvadore (on behalf of status@)
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
>
> Thanks for reading,
>
> bob prohaska
I had similar issues with other updates. I suggest you try to rebuild
textproc/libvisio01. It probably searches for libicuuc.so.70, but cannot
find it because there is libicuuc.so.72 after you have updated devel/icu.
If you build libviosio01 again it should search for the right shared object.
Cheers,
Lorenzo Salvadore
GHz results in no wifi.
> `service netif restart` finishes, with wlan0 device with no carrier.
> Is there a way to make 5GHz work in my situation or is it not yet supported?
I am using 5 GHz right now on my Intel AX201 (vendor=0x8086 device=0xa0f0).
FreeBSD-14 Current (2aaccae35db4) on Asus X515.
I did had issues once, yesterday. But it was an exeception and it probably
was not due to the FreeBSD driver.
Cheers,
Lorenzo Salvadore
that it'll just be the same again
> come FreeBSD 15, 16, 17...
>
> There needs to be a better mechanism to determine which FreeBSD version
> is being compiled for, but that shouldn't block this going in.
>
> OK.
Thanks, I will keep this concern in mind when FreeBSD 15 s
are
a report submitter, please ensure to read carefully the report authored by the
status team as well as the next Call for Reports emails to keep up with the
most recent changes.
Have a nice read.
Lorenzo Salvadore, on behalf of the status team
are
a report submitter, please ensure to read carefully the report authored by the
status team as well as the next Call for Reports emails to keep up with the
most recent changes.
Have a nice read.
Lorenzo Salvadore, on behalf of the status team
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
I would like to remind that Gerald Pfeifer already volunteered to commit this
patch
when it is approved. However the patch has not been approved yet.
Thanks,
Lorenzo Salvadore
> --- Original Mess
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
P.S.
> To test pre-built nasm causes failure on ports BUILD_DEPENDing on nasm,
> I've done below and confirmed OK, even with USE_TMPFS=yes
> on /usr/local/etc/poudriere.conf.
> So maybe TMPFS_BLACKLIST'ing nasm alone would be sufficient.
>
> 1. Built devel/nasm with ports-mgmt/pkg_replace, which builds fine,
> 2. pkg create it,
> 3. start usual poudriere run with unusual "-i" added,
> 4. after poudriere goes into shell, copy pre-built nasm package,
> to /poudriere/data/packages/(jain name)/All/,
> 5. exit shell invoked by poudriere,
> 6. once finished, delete jpeg-turbo package from
> /poudriere/data/packages/(jain name)/All/,
> 7. build jpeg-turbo using poudriere.
>
> Copying pre-build nasm package without steps 3-5 caused re-building
> nasm, which promissingly fails.
Thank you very much for reporting the issue.
As it has already been noted, the commit that broke nasm has been reverted with
https://cgit.freebsd.org/ports/commit/?id=102f7173426ac4122afd355205aa141bb50b2803
.
Investigations have started to understand the issue and a bug report has been
opened
to track the issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268528
Thanks and sorry for the broken update,
Lorenzo Salvadore
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
> From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
> From: Lorenzo Salvadore develo...@lorenzosalvadore.it
>
> Date: Wed, 16 Nov 2022 11:27:38 +01
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
I would like to remind that Gerald Pfeifer already volunteered to commit this
patch
when it is approved. However the patch has not been approved yet.
Thanks,
Lorenzo Salvadore
> --- Original Mess
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html
Thanks,
Lorenzo Salvadore
---
>From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
From: Lorenzo Salvadore
Date: Wed, 16 Nov 2022 11:27:38 +0100
Subject: [PATCH] jit: Install jit headers
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q4 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
Hello,
Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
I would like to remind that Gerald Pfeifer already volunteered to commit this
patch
when it is approved. However the patch has not been approved yet.
Thanks,
Lorenzo Salvadore
--- Original Message ---
On
Richard Biener's suggestion from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491#c5 .
Thanks,
Lorenzo Salvadore
---
>From f8e2c2ee89a7d8741bb65163d1f1c20edcd546ac Mon Sep 17 00:00:00 2001
From: Lorenzo Salvadore
Date: Wed, 16 Nov 2022 11:27:38 +0100
Subject: [PATCH] jit: Install jit he
Hello,
I would like to submit the patch below. Gerald Pfeifer already
volunteered to commit it once approved.
Thanks,
Lorenzo Salvadore
---
Update __FreeBSD_version values for the latest FreeBSD supported
versions. In particular, add __FreeBSD_version for FreeBSD 14, which is
necessary to
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
sions (the one on FreeBSD and the
one on Fedora) as similarly as possible (for example, you have
--disable-multilib
and --disable-bootstrap on FreeBSD, but --enable-multilib and
--with-build-config=bootstrap-lto on Fedora), then test again.
If the FreeBSD version has the same configuation of the Fedora version but still
fails, then the problem might be upstream and a bug report upstream should be
opened; otherwise, it is possible that something is wrong with our port and we
should fix it.
Thanks,
Lorenzo Salvadore
-submissi...@freebsd.org.
The new AsciiDoctor template can be found at:
https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc
We look forward to seeing your 2022Q3 reports!
Thanks,
Lorenzo Salvadore (on behalf of quarterly@)
ell that I received two pkg-fallout mails today: one
for gcc12 and
the other one for gcc13-devel and none of them has been updated recently. So I
guess something
changed in one of their dependencies, which might have affected some other
ports.
Cheers,
Lorenzo Salvadore
, but please warn us so
that we are aware that some report is still missing.
Many thanks to all those that have chosen to share their work with the FreeBSD
community through the quarterly reports.
Lorenzo Salvadore, on behalf of the status report team
, but please warn us so
that we are aware that some report is still missing.
Many thanks to all those that have chosen to share their work with the FreeBSD
community through the quarterly reports.
Lorenzo Salvadore, on behalf of the status report team
1 - 100 of 187 matches
Mail list logo
