public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug modula2/110002] New: Using -fcpp only invokes cc1 from pre-configured path $(libexec)
@ 2023-05-27 8:49 admin@tho-otto.de
2023-05-27 8:53 ` [Bug modula2/110002] " admin@tho-otto.de
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: admin@tho-otto.de @ 2023-05-27 8:49 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002
Bug ID: 110002
Summary: Using -fcpp only invokes cc1 from pre-configured path
$(libexec)
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: gaius at gcc dot gnu.org
Reporter: admin@tho-otto.de
Target Milestone: ---
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec) 2023-05-27 8:49 [Bug modula2/110002] New: Using -fcpp only invokes cc1 from pre-configured path $(libexec) admin@tho-otto.de @ 2023-05-27 8:53 ` admin@tho-otto.de 2023-07-28 15:13 ` gaius at gcc dot gnu.org 2023-08-17 5:06 ` admin@tho-otto.de 2 siblings, 0 replies; 4+ messages in thread From: admin@tho-otto.de @ 2023-05-27 8:53 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 --- Comment #1 from Thorsten Otto <admin@tho-otto.de> --- When using -fcpp, gm2cc1 invokes cc1 only from the configured $(libexec) directory, eg. /usr/lib64/gcc/x86_64-suse-linux/13/cc1. But when installed in a different directory, it should use <installdir>/../lib64/gcc/x86_64-suse-linux/13/cc1 first, like the driver does. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec) 2023-05-27 8:49 [Bug modula2/110002] New: Using -fcpp only invokes cc1 from pre-configured path $(libexec) admin@tho-otto.de 2023-05-27 8:53 ` [Bug modula2/110002] " admin@tho-otto.de @ 2023-07-28 15:13 ` gaius at gcc dot gnu.org 2023-08-17 5:06 ` admin@tho-otto.de 2 siblings, 0 replies; 4+ messages in thread From: gaius at gcc dot gnu.org @ 2023-07-28 15:13 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 Gaius Mulley <gaius at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Last reconfirmed| |2023-07-28 --- Comment #2 from Gaius Mulley <gaius at gcc dot gnu.org> --- Confirmed thanks for the bug report - will fix. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec) 2023-05-27 8:49 [Bug modula2/110002] New: Using -fcpp only invokes cc1 from pre-configured path $(libexec) admin@tho-otto.de 2023-05-27 8:53 ` [Bug modula2/110002] " admin@tho-otto.de 2023-07-28 15:13 ` gaius at gcc dot gnu.org @ 2023-08-17 5:06 ` admin@tho-otto.de 2 siblings, 0 replies; 4+ messages in thread From: admin@tho-otto.de @ 2023-08-17 5:06 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 --- Comment #3 from Thorsten Otto <admin@tho-otto.de> --- Created attachment 55745 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55745&action=edit Possible workaround I currently use the attached patch to work around this. However it is a bit hackish as it uses a global variable to access argv[0]. Using GetArgV() does not seem to work because that module was not yet initialized. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-08-17 5:06 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-05-27 8:49 [Bug modula2/110002] New: Using -fcpp only invokes cc1 from pre-configured path $(libexec) admin@tho-otto.de 2023-05-27 8:53 ` [Bug modula2/110002] " admin@tho-otto.de 2023-07-28 15:13 ` gaius at gcc dot gnu.org 2023-08-17 5:06 ` admin@tho-otto.de
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).