Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status/2024Q4/gcc.adoc: Add report #451

Closed
wants to merge 1 commit into from

Conversation

lsalvadore
Copy link
Member

No description provided.

Copy link
Contributor

@pauamma pauamma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with changes to lines 12, 17 (if confirmed by a native speaker), and 22.


Contact: Lorenzo Salvadore <[email protected]>

The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run] to update GCC default version from 13 to 14 is getting forward.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd change the link text to be all of "exp-run to update GCC default version from 13 to 14".


If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding `-fpermissive` to `CFLAGS` in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds.
The `-fpermissive` flag switches those errors back to warnings.
However, it is preferable that upstream updates its code to remove those warnings completely so that `-fpermissive` is not necessary, possibily with FreeBSD ports maintainers support.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "updates" should be "update" (subjunctive), but I'll defer to a native US English speaker.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left that as it is for now (I am not a native English speaker either). If it is wrong, we can always fix it after the commit.


Work has been done on some bugs too, mainly upstream:
- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210[] has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version;
- link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008[] has been fixed: this was an issue with posix_falloacte failing on FreeBSD on a ZFS filesystem;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/posix_falloacte/posix_fallocate/

freebsd-git pushed a commit that referenced this pull request Jan 1, 2025
Reviewed by:	status (Pau Amma <[email protected]>)
Pull Request:	#451
@lsalvadore
Copy link
Member Author

Merged, thanks!

@lsalvadore lsalvadore closed this Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants