search for: msg00421

...ethods of specifying a library on the command line. I think that this method is actually more intuitive than either the method used by the linker script INPUT command or by --library. FWIW, I looked into the history of the colon prefix. It was added in https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. Unfortunately, the rationale given is that it was merely a port of a vxworks linker extension. I couldn't trace the history any further than that to find the actual design discussion. The linker script command INPUT uses a different scheme and the command already had this search order 20...

...e command >> line. I think that this method is actually more intuitive than either the >> method used by the linker script INPUT command or by --library. FWIW, I >> looked into the history of the colon prefix. It was added in >> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >> Unfortunately, the rationale given is that it was merely a port of a >> vxworks linker extension. I couldn't trace the history any further than >> that to find the actual design discussion. The linker script command INPUT >> uses a different scheme and the comma...

...I think that this method is actually more intuitive than either the >>>> method used by the linker script INPUT command or by --library. FWIW, I >>>> looked into the history of the colon prefix. It was added in >>>> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >>>> Unfortunately, the rationale given is that it was merely a port of a >>>> vxworks linker extension. I couldn't trace the history any further than >>>> that to find the actual design discussion. The linker script command INPUT >>>> uses...

...d is actually more intuitive than either the >>>>>> method used by the linker script INPUT command or by --library. FWIW, I >>>>>> looked into the history of the colon prefix. It was added in >>>>>> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >>>>>> Unfortunately, the rationale given is that it was merely a port of a >>>>>> vxworks linker extension. I couldn't trace the history any further than >>>>>> that to find the actual design discussion. The linker script command INPU...

...d is actually more intuitive than either the >>>>>> method used by the linker script INPUT command or by --library. FWIW, I >>>>>> looked into the history of the colon prefix. It was added in >>>>>> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >>>>>> Unfortunately, the rationale given is that it was merely a port of a >>>>>> vxworks linker extension. I couldn't trace the history any further than >>>>>> that to find the actual design discussion. The linker script command INPU...

...tive than either the >>>>>>>> method used by the linker script INPUT command or by --library. FWIW, I >>>>>>>> looked into the history of the colon prefix. It was added in >>>>>>>> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >>>>>>>> Unfortunately, the rationale given is that it was merely a port of a >>>>>>>> vxworks linker extension. I couldn't trace the history any further than >>>>>>>> that to find the actual design discussion. The li...

...;>>>>>>>>> method used by the linker script INPUT command or by --library. FWIW, I >>>>>>>>>> looked into the history of the colon prefix. It was added in >>>>>>>>>> https://www.sourceware.org/ml/binutils/2007-03/msg00421.html. >>>>>>>>>> Unfortunately, the rationale given is that it was merely a port of a >>>>>>>>>> vxworks linker extension. I couldn't trace the history any further than >>>>>>>>>> that to find the actual d...

At Sony we offer autolinking as a feature in our ELF toolchain. We would like to see full support for this feature upstream as there is anecdotal evidence that it would find use beyond Sony. In general autolinking (https://en.wikipedia.org/wiki/Auto-linking) allows developers to specify inputs to the linker in their source code. LLVM and Clang already have support for autolinking on ELF via