git
/
gcc
mirror of git://gcc.gnu.org/git/gcc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Simplify 'Makefile' dependencies for libatomic [PR81358] 

I noticed that commit r16-4315-ge63cf4b130b86dd7dde1bf499d3d40faca10ea2e
"PR81358: Enable automatic linking of libatomic" had introduced a lot of
repeated 'Makefile' dependencies for libatomic, including some nonsensical
ones, like 'configure-stage1-target-libada: maybe-all-stage1-target-libatomic'
(libada isn't bootstrapped).  That's because the code for generation of
dependencies had been put into inside an existing loop over 'target_modules'.

	PR driver/81358
	* Makefile.tpl: Move generation of dependencies for libatomic out
	of loop over 'target_modules'.
	* Makefile.in: Regenerate.
This commit is contained in:
Thomas Schwinge 2025-10-21 09:46:32 +02:00
parent 5bfa8d3a3d
commit 04df8fa9e7
2 changed files with 2 additions and 3191 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3191
Makefile.in
View File

File diff suppressed because it is too large Load Diff

2
Makefile.tpl
View File

@ -2122,6 +2122,7 @@ configure-target-[+module+]: maybe-all-target-newlib maybe-all-target-libgloss[+
ENDIF +][+ IF (lang-dep "cxx") +]
configure-target-[+module+]: maybe-all-target-libstdc++-v3[+
ENDIF +]
[+ ENDFOR target_modules +]
@if gcc-bootstrap[+ FOR target_modules +][+ IF (not (lang-dep "no_atomic"))
+][+ IF bootstrap +][+ FOR bootstrap_stage +]
@ -2133,7 +2134,6 @@ configure-stage[+id+]-target-[+module+]: maybe-all-stage[+id+]-target-libatomic[
configure-target-[+module+]: maybe-all-target-libatomic[+
ENDIF +][+ ENDFOR target_modules +]
@endif gcc-no-bootstrap
[+ ENDFOR target_modules +]
CONFIGURE_GDB_TK = @CONFIGURE_GDB_TK@
GDB_TK = @GDB_TK@