[Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec)

2023-08-16 Thread admin--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 --- Comment #3 from Thorsten Otto --- Created attachment 55745 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55745=edit Possible workaround I currently use the attached patch to work around this. However it is a bit hackish as it uses a

[Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec)

2023-07-28 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 Gaius Mulley changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug modula2/110002] Using -fcpp only invokes cc1 from pre-configured path $(libexec)

2023-05-27 Thread admin--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002 --- Comment #1 from Thorsten Otto --- 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