gcc/gcc
gcc/gcc
Watch
43
Fork
You've already forked gcc
 58
Code Issues Pull requests 58 Wiki Activity Actions

config: Update autoconf macros used for multilib support [PR103459] #228

Open
pietro wants to merge 1 commit from pietro/gcc:config-multilib into trunk
pull from: pietro/gcc:config-multilib
merge into: gcc:trunk
Conversation 5 Commits 1 Files changed 21 +66 -66
pietro commented 2026-09-05 01:37:16 +00:00
First-time contributor
Copy link

Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS and regenerate
configure scripts.

PR bootstrap/103459

config/ChangeLog:

* multi.m4: Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS.

libada/ChangeLog:

* configure: Regenerate.

libatomic/ChangeLog:

* configure: Regenerate.

libbacktrace/ChangeLog:

* configure: Regenerate.

libffi/ChangeLog:

* configure: Regenerate.

libga68/ChangeLog:

* configure: Regenerate.

libgcobol/ChangeLog:

* configure: Regenerate.

libgfortran/ChangeLog:

* configure: Regenerate.

libgm2/ChangeLog:

* configure: Regenerate.

ChangeLog:

* libgo/configure: Regenerate.

libgomp/ChangeLog:

* configure: Regenerate.

libgrust/ChangeLog:

* configure: Regenerate.

libitm/ChangeLog:

* configure: Regenerate.

libobjc/ChangeLog:

* configure: Regenerate.

libphobos/ChangeLog:

* configure: Regenerate.

libquadmath/ChangeLog:

* configure: Regenerate.

libsanitizer/ChangeLog:

* configure: Regenerate.

libssp/ChangeLog:

* configure: Regenerate.

libstdc++-v3/ChangeLog:

* configure: Regenerate.

libvtv/ChangeLog:

* configure: Regenerate.

zlib/ChangeLog:

* configure: Regenerate.

Signed-off-by: Pietro Monteiro pietro@sociotechnical.xyz

Thanks for taking the time to contribute to GCC!

Please be advised that https://forge.sourceware.org/ is currently a trial
that is being used by the GCC community to experiment with a new workflow
based on pull requests.

Pull requests sent here may be forgotten or ignored. Patches that you want to
propose for inclusion in GCC should use the existing email-based workflow,
see https://gcc.gnu.org/contribute.html

Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS and regenerate configure scripts. PR bootstrap/103459 config/ChangeLog: * multi.m4: Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS. libada/ChangeLog: * configure: Regenerate. libatomic/ChangeLog: * configure: Regenerate. libbacktrace/ChangeLog: * configure: Regenerate. libffi/ChangeLog: * configure: Regenerate. libga68/ChangeLog: * configure: Regenerate. libgcobol/ChangeLog: * configure: Regenerate. libgfortran/ChangeLog: * configure: Regenerate. libgm2/ChangeLog: * configure: Regenerate. ChangeLog: * libgo/configure: Regenerate. libgomp/ChangeLog: * configure: Regenerate. libgrust/ChangeLog: * configure: Regenerate. libitm/ChangeLog: * configure: Regenerate. libobjc/ChangeLog: * configure: Regenerate. libphobos/ChangeLog: * configure: Regenerate. libquadmath/ChangeLog: * configure: Regenerate. libsanitizer/ChangeLog: * configure: Regenerate. libssp/ChangeLog: * configure: Regenerate. libstdc++-v3/ChangeLog: * configure: Regenerate. libvtv/ChangeLog: * configure: Regenerate. zlib/ChangeLog: * configure: Regenerate. Signed-off-by: Pietro Monteiro <pietro@sociotechnical.xyz> Thanks for taking the time to contribute to GCC! Please be advised that https://forge.sourceware.org/ is currently a trial that is being used by the GCC community to experiment with a new workflow based on pull requests. Pull requests sent here may be forgotten or ignored. Patches that you want to propose for inclusion in GCC should use the existing email-based workflow, see https://gcc.gnu.org/contribute.html
config: Update autoconf macros used for multilib support [PR103459]
Some checks failed
/ format-checks (pull_request) Failing after 1m33s
Details
e592635350 
Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS and regenerate
configure scripts.

	PR bootstrap/103459

config/ChangeLog:

	* multi.m4: Update AC_OUTPUT_COMMANDS to AC_CONFIG_COMMANDS.

libada/ChangeLog:

	* configure: Regenerate.

libatomic/ChangeLog:

	* configure: Regenerate.

libbacktrace/ChangeLog:

	* configure: Regenerate.

libffi/ChangeLog:

	* configure: Regenerate.

libga68/ChangeLog:

	* configure: Regenerate.

libgcobol/ChangeLog:

	* configure: Regenerate.

libgfortran/ChangeLog:

	* configure: Regenerate.

libgm2/ChangeLog:

	* configure: Regenerate.

ChangeLog:

	* libgo/configure: Regenerate.

libgomp/ChangeLog:

	* configure: Regenerate.

libgrust/ChangeLog:

	* configure: Regenerate.

libitm/ChangeLog:

	* configure: Regenerate.

libobjc/ChangeLog:

	* configure: Regenerate.

libphobos/ChangeLog:

	* configure: Regenerate.

libquadmath/ChangeLog:

	* configure: Regenerate.

libsanitizer/ChangeLog:

	* configure: Regenerate.

libssp/ChangeLog:

	* configure: Regenerate.

libstdc++-v3/ChangeLog:

	* configure: Regenerate.

libvtv/ChangeLog:

	* configure: Regenerate.

zlib/ChangeLog:

	* configure: Regenerate.

Signed-off-by: Pietro Monteiro <pietro@sociotechnical.xyz>
forge-bot commented 2026-09-05 01:37:19 +00:00
Member
Copy link

Hi @pietro. This bot helps send your PR as a patch series to the mailing list.

Next steps

  1. Write a clear PR description. It will be used as the cover letter.
  2. To CC extra people, add lines like this at the end of the PR description: CC: Reviewer1 <revi.ewer@example.com>, Reviewer2 <an.other@example.com>.
  3. To preview the emails, comment with /preview.
  4. When ready, request review in the Reviewers section. Or, if you just want to send the series, comment with /submit.
  5. Use the cover-letter links below to follow replies.
  6. For a new patch series, push your changes, update the PR description with a Changes since vX section, and comment with /submit again.

See Submitting Patches and UsingForge.

Consider joining the gcc and gcc-patches mailing lists..
For real time communication, check the gcc irc channels.

Or join #overseers on Libera Chat, particularly if this automation is not working (stay online to get replies, IRC does not save messages if people are not online).

<!-- pr-welcome --> Hi @pietro. This bot helps send your PR as a patch series to the mailing list. ## Next steps 1. Write a clear PR description. It will be used as the cover letter. 2. To CC extra people, add lines like this **at the end** of the PR description: `CC: Reviewer1 <revi.ewer@example.com>, Reviewer2 <an.other@example.com>`. 3. To preview the emails, comment with `/preview`. 4. When ready, request review in the Reviewers section. Or, if you just want to send the series, comment with `/submit`. 5. Use the cover-letter links below to follow replies. 6. For a new patch series, push your changes, update the PR description with a `Changes since vX` section, and comment with `/submit` again. See [Submitting Patches](https://gcc.gnu.org/contribute.html#patches) and [UsingForge](https://gcc.gnu.org/wiki/UsingForge). Consider joining the [gcc and gcc-patches mailing lists.](https://gcc.gnu.org/lists.html). For real time communication, check the [gcc irc channels](https://gcc.gnu.org/wiki/GCConIRC). Or join [`#overseers`](https://web.libera.chat/#overseers) on Libera Chat, particularly if this automation is not working (stay online to get replies, IRC does not save messages if people are not online).
pietro commented 2026-09-05 01:40:49 +00:00
Author
First-time contributor
Copy link

/submit

/submit
forge-bot commented 2026-09-05 01:41:26 +00:00
Member
Copy link

Version 1 of this pull request has been stored. It includes the following commits:

<!-- pr-new-version --> Version 1 of this pull request has been stored. It includes the following commits: - config: Update autoconf macros used for multilib support [PR103459] - e59263535089bdbe483843297465be770693fd69
forge-bot commented 2026-09-05 01:41:26 +00:00
Member
Copy link

Pull Request versions:

# Base Head
1 3653b8dd68 e592635350 (diff)

In order to compare , clone this repository and run

PR=228
git fetch origin "refs/versioned_pull/${PR}/*:refs/versioned_pull/${PR}/*"
PRV1=1
PRV2=2
git range-diff "refs/versioned_pull/${PR}/${PRV1}/base..refs/versioned_pull/${PR}/${PRV1}/head"  "refs/versioned_pull/${PR}/${PRV2}/base..refs/versioned_pull/${PR}/${PRV2}/head"
<!-- pr-versions --> Pull Request versions: | # | Base | Head | | | - | ---- | ---- | - | | 1 | 3653b8dd68b0caf1c713058854d1efde9cc14329 | e59263535089bdbe483843297465be770693fd69 | [(diff)](https://forge.sourceware.org/gcc/gcc.git/compare/3653b8dd68b0caf1c713058854d1efde9cc14329...e59263535089bdbe483843297465be770693fd69) | In order to compare , clone this repository and run ``` PR=228 git fetch origin "refs/versioned_pull/${PR}/*:refs/versioned_pull/${PR}/*" PRV1=1 PRV2=2 git range-diff "refs/versioned_pull/${PR}/${PRV1}/base..refs/versioned_pull/${PR}/${PRV1}/head" "refs/versioned_pull/${PR}/${PRV2}/base..refs/versioned_pull/${PR}/${PRV2}/head" ```
forge-bot commented 2026-09-05 01:41:57 +00:00
Member
Copy link

Sent patch version 1 as a single email to gcc-patches mailing list gcc-patches@gcc.gnu.org.
Cover letter

Sent patch version 1 as a single email to gcc-patches mailing list <gcc-patches@gcc.gnu.org>. [Cover letter](https://inbox.sourceware.org/gcc-patches/bmm.hlzuualbcc.gcc.gcc.pietro.228.1.0@forge-stage.sourceware.org)
Some checks failed
/ format-checks (pull_request) Failing after 1m33s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u config-multilib:pietro-config-multilib
git switch pietro-config-multilib

Merge

Merge the changes and update on Forgejo.
git switch trunk
git merge --no-ff pietro-config-multilib
git switch pietro-config-multilib
git rebase trunk
git switch trunk
git merge --ff-only pietro-config-multilib
git switch pietro-config-multilib
git rebase trunk
git switch trunk
git merge --no-ff pietro-config-multilib
git switch trunk
git merge --squash pietro-config-multilib
git switch trunk
git merge --ff-only pietro-config-multilib
git switch trunk
git merge pietro-config-multilib
git push origin trunk
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Compat/Breaking
Breaking change that won't be backward compatible

  
Frontend/ada

   
Frontend/c

   
Frontend/c++

   
Frontend/rust
Code affecting the Rust front end

  
General/forge
Forgejo infrastructure

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Library/libgcc

   
Library/libstdc++

   
Midend/gimple

   
Midend/rtl

   
Midend/tree
  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

  
Target/aarch64

   
Target/arm

   
Target/i386
  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
Compat/Breaking
Frontend/ada
Frontend/c
Frontend/c++
Frontend/rust
General/forge
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Library/libgcc
Library/libstdc++
Midend/gimple
Midend/rtl
Midend/tree
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Target/aarch64
Target/arm
Target/i386
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gcc/gcc!228
No description provided.