[GitHub] [incubator-nuttx] AlexanderVasiljev edited a comment on issue #3826: arm-none-eabi-ld: Error: unable to disambiguate: -nostartfiles

[GitBox <gi...@apache.org>]

AlexanderVasiljev edited a comment on issue #3826:
URL: https://github.com/apache/incubator-nuttx/issues/3826#issuecomment-852912391


   See my question on binutils
   https://sourceware.org/pipermail/binutils/2021-June/116825.html
   
   The answer from nickc@redhat.com  is
   
   > The -nostartfiles option is a gcc command line option, not a linker
   > command line option.  It is used when gcc is creating an executable
   > binary and it tells gcc not to include the standard system files
   > (eg crt1.o, crtbegin.o, crtend.o etc) when gcc invokes the linker.
   > 
   > All of which means that in your build system somewhere you have:
   > 
   >    arm-none-eabi-ld -nostartfiles ...
   > 
   > whereas you probably meant to have:
   > 
   >    arm-none-eabi-gcc -nostartfiles ...
   > 
   > Note: the reason why this problem has appeared when you upgraded is
   > that we recently added some extra error checking to the linker to
   > attempt to detect mis-spelt command line options.  In particular the
   > linker interprets options that start with a single dash as if they
   > were multiple, single letter options.  So "-nostartfiles" would be
   > treated as "-n" "-o startfiles" which is probably not what the user
   > wanted.  Hence the error message.
   > 
   > Plus, just to be clear, the linker does not support a --nostartfiles
   > option.  The code that generates the error message does not actually
   > check to see if the double dash version of the option exists...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org