RE: unresolved symbols __eqd, __negd, __itod etc while building platform

From: Russ Keldorph [MS] (russellk_at_online.microsoft.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 18:59:11 GMT

The __imp_ prefixes are references to the import table that the linker
inserts in your module when you link with a DLL's import library. It is
more efficient to make a DLL call this way than to go through a
linker-inserted thunk. In this case, you could link with COREDLL.LIB to
resolve those references. If, for some reason, you can't link to COREDLL
and instead would like to link to the C Runtime statically, you need to
tell the compiler not to generate references to the import table and
instead generate normal calls to the helper routines. You do this by
passing the /QRimplicit-import- switch to the compiler. With that switch,
the compiler will generate direct references to __eqd, __negd, etc. 

-- 
Russ Keldorph
russellk@online.microsoft.com (Remove the 'online.' from my address to 
reach me.)
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
--------------------
> Thread-Topic: unresolved symbols __eqd, __negd, __itod etc while building 
platform
> thread-index: AcQKkyxvdDIVFj9XSgqkuOZgfq7CmQ==
> X-Tomcat-NG: microsoft.public.windowsce.embedded
> From: "=?Utf-8?B?cHBwc2FuZGVlcA==?=" <anonymous@discussions.microsoft.com>
> Subject: unresolved symbols __eqd, __negd, __itod etc while building 
platform
> Date: Mon, 15 Mar 2004 05:41:09 -0800
> Lines: 3
> Message-ID: <ABD3CDF9-1E08-46A2-BC95-DDEEA1865274@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> 	charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.windowsce.embedded
> Path: cpmsftngxa06.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsce.embedded:21151
> NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
> X-Tomcat-NG: microsoft.public.windowsce.embedded
> 
> I am trying to build a target platform using make utility for WinCE 4.0. 
During the sysgen phase, I get linking errors like "unresolved external  
symbols __imp___eqd, __imp___negd, __imp___muld etc.". I found that these 
symbols are internally used by the C runtime libraries, and they are 
exported by various libraries like corecrt.lib, ccrtcpu2.lib etc. however I 
couldnt find out why they are not been found by the linker.
Does anybody know anything about these kinda errrors?
>

Relevant Pages

  • Re: calling my custom function same as library function
    ... > malloc() is placed between their other object files and the ... > right such as the other libraries. ... > unsatisfied references to the left of the current object. ... I think you are confused about the linker action. ...
    (comp.lang.c)
  • Re: Problem Fixed
    ... I think you're a bit confused about how the linker works. ... The fileit will look for are somewhat platform specific, ... It looks like your platform uses "libfoo.dylib" for shared libraries. ... the libfoo.dylib "file" is actually a symlink to a versioned shared ...
    (SSH)
  • Re: strange linking problem
    ... I usually use C, and since strings ... the linker goes through the object ... files and looks for unsatisfied references to functions and variables. ... references by linking code from the libraries into the executable. ...
    (comp.lang.fortran)
  • Re: creating a Fortran library
    ... It is just how the Unix linker works... ... The main program has references ... which reference other libraries (quite common in all but pretty small ... You then need to specify the libraries in an appropriate ...
    (comp.lang.fortran)
  • Re: gcc linkage problems
    ... > references to symbols that are defined in the library. ... With your command line, the linker first opens ... I have extracted objects from ... > ordering for libraries objects with and without the static specifier. ...
    (comp.lang.cpp)