Comment 9 for bug 1689294

Revision history for this message
stewo (wolfer-y) wrote : [Autoreply] [Bug 1689294] Re: lto-wrapper.exe: fatal error: CreateProcess: No such file or directory

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
Karl-Heinrich-Käferle-Str. 8
D-71640 Ludwigsburg, Germany

Phone: +49 7141 94702-22
Fax: +49 7141 94702-99
http://www.weiss-robotics.com

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ß

Further analysis suggests that missing make.exe in PATH is the root
cause of the reported error message. As make.exe is not part of GCC, but
is needed in -flto=n, user must make sure that make.exe be accessible in
PATH.

** Changed in: gcc-arm-embedded
       Status: Confirmed => Invalid

--
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:
  Invalid

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:
https://bugs.launchpad.net/gcc-arm-embedded/+bug/1689294/+subscriptions