<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Error L128 Symbol not found</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/20632/error-l128-symbol-not-found</link><description> 
Hi floks 

 
When the linker error L128 happens, REFERENCE MADE TO UNRESOLVED
EXTERNAL the name is listed under the message. 
But a double click won&amp;#39;t jump to the line in the source file where
the missing name was found. 

 
And it&amp;#39;s not possible to</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Error L128 Symbol not found</title><link>https://community.arm.com/thread/74328?ContentTypeID=1</link><pubDate>Mon, 04 Sep 2006 16:11:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:94da0004-5289-466a-87c5-06091fc212aa</guid><dc:creator>HansBernhard Broeker</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;I would guess that this is because linkers &amp;quot;don&amp;#39;t do&amp;quot; source
files.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
But they still do &lt;b&gt;debug information&lt;/b&gt; --- at least enough of
it to be able to combine the debug info from all those object files
and libraries, and write debug info for the generated absolute object
module. So the linker could do it if it wanted to (read: if Keil
invested the effort to implement this feature).&lt;/p&gt;

&lt;p&gt;
It&amp;#39;s not at all unusual for linkers to be able to pin-point which
source line contained the reference that turned out to be
unfulfillable.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error L128 Symbol not found</title><link>https://community.arm.com/thread/87892?ContentTypeID=1</link><pubDate>Mon, 04 Sep 2006 05:28:25 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:152a8a8b-478c-458b-8683-37a46865f068</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
It is true that the Linker knows nothing about the source
files.&lt;/p&gt;

&lt;p&gt;
However, the point of an &lt;b&gt;IDE&lt;/b&gt; is that it should be able to
take an overview (hence &amp;quot;Integrated&amp;quot;) of the entire project, and
access all the components of the toolchain (hence, again,
&amp;quot;Integrated&amp;quot;) to solve such problems.&lt;/p&gt;

&lt;p&gt;
So there&amp;#39;s obviously an opportunity here for Keil to enhance the
integration provided by uVision to solve this problem:&lt;/p&gt;

&lt;p&gt;
At its simplest, just provide a &amp;quot;search for this symbol in the
project sources&amp;quot; facility;&lt;/p&gt;

&lt;p&gt;
More involved might be to have uVision determine the location of
the source line from the Debug information, if that is possible.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error L128 Symbol not found</title><link>https://community.arm.com/thread/46722?ContentTypeID=1</link><pubDate>Mon, 04 Sep 2006 04:24:40 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:fb01242f-9f65-4b8f-8a11-8cb8970a61b1</guid><dc:creator>Christoph Franck</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;When the &lt;b&gt;linker&lt;/b&gt; error L128 happens,&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
...&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;But a double click won&amp;#39;t jump to the line in the &lt;b&gt;source&lt;/b&gt;
file where&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
I would guess that this is because linkers &amp;quot;don&amp;#39;t do&amp;quot; source
files. That is the job of a compiler or assembler - turning source
files into object files.&lt;/p&gt;

&lt;p&gt;
Linkers work with object files, and they have little to no way of
knowing how the object file was generated, and therefore usually
can&amp;#39;t give &amp;quot;source file line numbers&amp;quot; of the problem they found.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>