Ich bin bis 28.10. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
I am out of office until October 28th and won't be able to read your message. In urgent cases, please refer to <email address hidden> or for technical questions to <email address hidden>.
Mit freundlichen Grüßen / Best regards
Steffen Wolfer
--
Dipl.-Inform. Steffen Wolfer
Software Engineer Embedded Systems
** Changed in: gcc-arm-embedded
Status: Invalid => New
--
You received this bug notification because you are subscribed to GNU Arm
Embedded Toolchain.
Matching subscriptions: Älles https://bugs.launchpad.net/bugs/1689294
Title:
lto-wrapper.exe: fatal error: CreateProcess: No such file or directory
Status in GNU Arm Embedded Toolchain:
New
Bug description:
On Windows the GCC 6.3.1-2017q1 has a problem with `lto-wrapper.exe`
if the compiler `bin` directory IS NOT in the PATH environment
variable.
However this is unacceptable on our build server were we build
branches with different compiler versions. We didn't have similar
problems with any form 5.x series, but on the branch for 6.3.1 we
enabled LTO, that seem to work in general in manual builds.
It doesn't matter if the bundle in located in the directory which path
contains spaces or doesn't. It seems that while the long standing bug
for MinGW has been fixed for all other sub-tools, it's still present
for `lto-wrapper`.
Is there any workaround know to make it work without adding the
compiler directory into PATH?
Ich bin bis 28.10. nicht im Haus und kann Ihre Nachricht daher leider nicht bearbeiten. In dringenden Fällen wenden Sie sich bitte an <email address hidden> bzw. für technische Fragen an <email address hidden>.
I am out of office until October 28th and won't be able to read your message. In urgent cases, please refer to <email address hidden> or for technical questions to <email address hidden>.
Mit freundlichen Grüßen / Best regards
Steffen Wolfer
--
Dipl.-Inform. Steffen Wolfer
Software Engineer Embedded Systems
WEISS ROBOTICS GmbH & Co. KG Käferle- Str. 8
Karl-Heinrich-
D-71640 Ludwigsburg, Germany
Phone: +49 7141 94702-22 www.weiss- robotics. com
Fax: +49 7141 94702-99
http://
Sitz der Gesellschaft: Ludwigsburg
Registergericht Stuttgart, HRA725006
Pers. haftende Gesellschafterin:
Weiss Robotics Verwaltungs-GmbH, Sitz Ludwigsburg
Registergericht Stuttgart, HRB73310
Geschäftsführer: Dr. Karsten Weiß
https:/ /gcc.gnu. org/bugzilla/ show_bug. cgi?id= 89183
Is this bug fix included in 8.3.1-2019q3?
** Changed in: gcc-arm-embedded
Status: Invalid => New
-- /bugs.launchpad .net/bugs/ 1689294
You received this bug notification because you are subscribed to GNU Arm
Embedded Toolchain.
Matching subscriptions: Älles
https:/
Title:
lto-wrapper.exe: fatal error: CreateProcess: No such file or directory
Status in GNU Arm Embedded Toolchain:
New
Bug description:
On Windows the GCC 6.3.1-2017q1 has a problem with `lto-wrapper.exe`
if the compiler `bin` directory IS NOT in the PATH environment
variable.
However this is unacceptable on our build server were we build
branches with different compiler versions. We didn't have similar
problems with any form 5.x series, but on the branch for 6.3.1 we
enabled LTO, that seem to work in general in manual builds.
It doesn't matter if the bundle in located in the directory which path
contains spaces or doesn't. It seems that while the long standing bug
for MinGW has been fixed for all other sub-tools, it's still present
for `lto-wrapper`.
Is there any workaround know to make it work without adding the
compiler directory into PATH?
To manage notifications about this bug go to: /bugs.launchpad .net/gcc- arm-embedded/ +bug/1689294/ +subscriptions
https:/