Fatal linker error with C++ 2006

[JørgenBerntsen]

Hi

I'm using C++ 2006 and the newest EurekaLog on a Win XP machine.

When I want to deploy my application with ComponentPack from TMS and EurekaLog I get a fatal linker error message (no problems when building with runtime libraries and dynamic RTL libraries)!

If I don't use EurekaLog the applications is build without any problems.

Have anybody experienced anything similar?

Any help or suggestions is greatly appriciated,

Jørgen

[easyblue]

Hello

I have similar problem at C++6 between TMS and Eurekalog.

And the problem is due to a bug in Borland.

Workround is to deactivate Eurekalog during TMS component compile and installation, so TMS components have no Eurekalog function.

And then activate Eurekalog in application who uses TMS.

Next month we will have C++2006. I will test again then.

[Tms]

Hello

I have tried your suggestion. However, it don't work for me. Still get the
fatal linker error.

Looking forward to hear about your experience with C++ 2006 next month!

Thanks for your help, Jørgen

"easyblue" <rong.liang@siemens.com> wrote in message
news:easyblue.25gpha@no-mx.news.eurekalog.com...
>
> Hello
>
> I have similar problem at C++6 between TMS and Eurekalog.
>
> And the problem is due to a bug in Borland.
>
> Workround is to deactivate Eurekalog during TMS component compile and
> installation, so TMS components have no Eurekalog function.
>
> And then activate Eurekalog in application who uses TMS.
>
> Next month we will have C++2006. I will test again then.
>
>
> --
> easyblue
> ------------------------------------------------------------------------
> easyblue's Profile: http://news.eurekalog.com/member.php?userid=64
> View this thread: http://news.eurekalog.com/showthread.php?t=297
>

[admin]

Hi,

JørgenBerntsen wrote:
> Hi
>
> I'm using C++ 2006 and the newest EurekaLog on a Win XP machine.
>
> When I want to deploy my application with ComponentPack from TMS and
> EurekaLog I get a fatal linker error message (no problems when building
> with runtime libraries and dynamic RTL libraries)!
>
> If I don't use EurekaLog the applications is build without any
> problems.
>
> Have anybody experienced anything similar?
>
> Any help or suggestions is greatly appriciated,
>
> Jørgen

I'm sorry but is a known C++Builder 6 bug (did not solved in the last
C++Builder 2006 version).

The bug is caused from the extensive .MAP file created by linker.

I hope that the next BDS 2006 Update 2 definitely solve this bug.

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[admin]

Hi,

Tms wrote:
> Hello
>
> I have tried your suggestion. However, it don't work for me. Still get the
> fatal linker error.
>
> Looking forward to hear about your experience with C++ 2006 next month!
>
> Thanks for your help, Jørgen
>
> [...]

Try to simply disabled the Map File creation.

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[vleonty]

My project has Map File creation disabled, but I still get this linker fatal error?

I am using BDS 2006, C++ (Update 2), TMS component pack, and EurekaLog 6.0.2.

Any suggestions?

[admin]

Try to do this:

1)...Close all opened Delphi/CBuilder instances;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containing the ExceptionLog.* or ?ExceptionExpert.* files;
4)...download and install the last EurekaLog version;
5)...restart your PC.

I'm waiting to your feedback as soon as possible, ok? :)

[vleonty]

Try to do this:

1)...Close all opened Delphi/CBuilder instances;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containing the ExceptionLog.* or ?ExceptionExpert.* files;
4)...download and install the last EurekaLog version;
5)...restart your PC.

I'm waiting to your feedback as soon as possible, ok? :)

I followed your instructions, but I still get the "Linker Fatal Error".

Just to recap, after following your instructions, I am now using EurekaLog 6.0.3 with BDS 2006 (Update 2), and TMS Component Pack v3.9. I am assuming you can recreate this problem?

I have a report filed on the CodeGear site with a sample project. Since there are 3rd party libraries involved, I suspect CodeGear will ignore it or shift the responsibility. You can access that project if you an account with CodeGear/BDN. The report number is 45034 and the web site is, http://qc.codegear.com/wc/qcmain.aspx.

[vleonty]

I followed your instructions, but I still get the "Linker Fatal Error".

Just to recap, after following your instructions, I am now using EurekaLog 6.0.3 with BDS 2006 (Update 2), and TMS Component Pack v3.9. I am assuming you can recreate this problem?

I have a report filed on the CodeGear site with a sample project. Since there are 3rd party libraries involved, I suspect CodeGear will ignore it or shift the responsibility. You can access that project if you an account with CodeGear/BDN. The report number is 45034 and the web site is, http://qc.codegear.com/wc/qcmain.aspx.

Did you verify this?

[gzo]

Very same problem here... Seems to be an internal bug of ilink32.exe. Shame on Borland, again...

[admin]

I have solved this issue in the last EurekaLog 6.0.4 RC 3.

Now EurekaLog create the .MAP file directly from the .TDS file, without the Linker help! :)

Try it please.

[vleonty]

I have solved this issue in the last EurekaLog 6.0.4 RC 3.

Now EurekaLog create the .MAP file directly from the .TDS file, without the Linker help! :)

Try it please.

It worked for me. Thank you for finding a quick resolution to this.

[admin]

You are welcome! ;)

[Unregistered]

I posted a reply to your comment on CodeGear QC45034 regarding this problem, but I'm not sure you keep close enough watch to see it.

I'm interested in getting a good test case together for this if it is still present in CB 2009.

- Leo Siefert

[admin]

Hi,
I was able to reproduce it only compiling a big application with the TMS components but without EurekaLog.

So it's impossible was any EurekaLog related issue! :)

[Ben]

In C++ Builder 2007 with EurekaLog 6.0.20, I compiled my app in the IDE linking to ExceptionLog.obj, with map generation disabled. I have EurekaLog disabled for the project, so I can process it afterward on our build server, but not on all our developer machines. See command-line below:

F:\fc\Dlls\FcDbSecurity>emake --el_config"F:\fc\Eureka.eof" --el_alter_exe"FcDbS
ecurity.cbproj;Debug_Build\FcDbSecurity.dll"
Loading EurekaLog options...
Map file 'Debug_Build\FcDbSecurity.map' not found.

I thought that the map file would be generated from the tds file. Is there something else I must do?

[Alex]

Hi,

Map file can be generated from TDS file.
And it is generated from TDS for C++ Builder. But basic map file still need to be present (i.e. info from TDS is being injected into map file). You should not turn off map generation.