Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: C++ Builder Seattle- Link error LME288. Can you reproduce?


This question is answered.


Permlink Replies: 36 - Last Post: May 17, 2017 7:02 AM Last Post By: Wiktor Wandacho...
Sean Hoffman

Posts: 126
Registered: 3/28/99
C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 17, 2015 3:21 PM
Greetings folks, can anyone reproduce the following:

1. Create a new blank 32 bit Windows FMX application, using the new compiler
2. Uncheck "use classic borland compiler"
3. Uncheck "link with dynamic runtime library"
4. Uncheck "build with runtime packages"
5. Drop on a TFDPhysSQLiteDriverLink component on the main form.
6. Try to build.

I get the following error:

ilink32 command line
d:\rs10\bin\ilink32.exe -G8 -L.\Win32\Debug;d:\rs10\lib\Win32\debug;d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;
d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP -j.\Win32\Debug;d:\rs10\lib\Win32\debug;
d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP
-l.\Win32\Debug -v -Gn -GA"C:\Users\sean\AppData\Local\Temp\vfsE49D.tmp"="E:\src\TestRS10\Main.fmx" -aa -V5.0 -Tpe c0fmx32w memmgr.lib sysinit.obj
.\Win32\Debug\TestRS10.obj .\Win32\Debug\Main.obj , .\Win32\Debug\TestRS10.exe , .\Win32\Debug\TestRS10.map , rtl.lib fmx.lib FireDACSqliteDriver.lib
FireDACCommonDriver.lib FireDACCommon.lib xmlrtl.lib dbrtl.lib import32.lib cp32mt.lib , , TestRS10.res
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilc: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ild: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilf: 0x00010000 / 0x0a000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ils: 0x0003b000 / 0x08000000
[ilink32 Warning] Warning: unknown heap name : 0x08000000 / 0x08000000
[ilink32 Warning] Warning: Error detected (LME288)
[ilink32 Error] Error: Unable to perform link
Failed
Elapsed time: 00:00:04.8

Johannes Weinert

Posts: 90
Registered: 7/19/02
Re: C++ Builder Seattle- Link error LME288. Can you reproduce? [Edit]
Correct
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 18, 2015 12:29 AM   in response to: Sean Hoffman in response to: Sean Hoffman
Dear Sean,

I tried with the 10 Seattle Trial on a Windows 7 64bit machine and it
compiles and links fine. I will post my project into the attachment group.

Regards

Hans

Am 18.09.2015 um 00:22 schrieb Sean Hoffman:
Greetings folks, can anyone reproduce the following:

1. Create a new blank 32 bit Windows FMX application, using the new compiler
2. Uncheck "use classic borland compiler"
3. Uncheck "link with dynamic runtime library"
4. Uncheck "build with runtime packages"
5. Drop on a TFDPhysSQLiteDriverLink component on the main form.
6. Try to build.

I get the following error:

ilink32 command line
d:\rs10\bin\ilink32.exe -G8 -L.\Win32\Debug;d:\rs10\lib\Win32\debug;d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;
d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP -j.\Win32\Debug;d:\rs10\lib\Win32\debug;
d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP
-l.\Win32\Debug -v -Gn -GA"C:\Users\sean\AppData\Local\Temp\vfsE49D.tmp"="E:\src\TestRS10\Main.fmx" -aa -V5.0 -Tpe c0fmx32w memmgr.lib sysinit.obj
.\Win32\Debug\TestRS10.obj .\Win32\Debug\Main.obj , .\Win32\Debug\TestRS10.exe , .\Win32\Debug\TestRS10.map , rtl.lib fmx.lib FireDACSqliteDriver.lib
FireDACCommonDriver.lib FireDACCommon.lib xmlrtl.lib dbrtl.lib import32.lib cp32mt.lib , , TestRS10.res
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilc: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ild: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilf: 0x00010000 / 0x0a000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ils: 0x0003b000 / 0x08000000
[ilink32 Warning] Warning: unknown heap name : 0x08000000 / 0x08000000
[ilink32 Warning] Warning: Error detected (LME288)
[ilink32 Error] Error: Unable to perform link
Failed
Elapsed time: 00:00:04.8

Sean Hoffman

Posts: 126
Registered: 3/28/99
Re: C++ Builder Seattle- Link error LME288. Can you reproduce? [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 18, 2015 4:58 AM   in response to: Johannes Weinert in response to: Johannes Weinert
Thank you kindly Johannes.
Jean-Marc Dupuis

Posts: 1
Registered: 5/16/98
Re: C++ Builder Seattle- Link error LME288. Can you reproduce? [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 20, 2015 11:26 AM   in response to: Sean Hoffman in response to: Sean Hoffman
Sean Hoffman wrote:
Thank you kindly Johannes.
Hi
I noticed the same problem under Win10 64 Bits
I found a way to solve the problem
ILINK32 must be running in Windows 7 compatibility mode
this solved my problem
Sean Hoffman

Posts: 126
Registered: 3/28/99
Re: C++ Builder Seattle- Link error LME288. Can you reproduce? [Edit]  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 21, 2015 7:58 AM   in response to: Jean-Marc Dupuis in response to: Jean-Marc Dupuis
Jean-Marc Dupuis wrote:
Sean Hoffman wrote:
Thank you kindly Johannes.
Hi
I noticed the same problem under Win10 64 Bits
I found a way to solve the problem
ILINK32 must be running in Windows 7 compatibility mode
this solved my problem

I can confirm that this did fix the problem with the sample project, with one caveat. After designating ilink32 to run in Windows 7 Compatibility mode, I also had to run the IDE as an administrator.

Unfortunately it did not fix the problem for my "real" project.
Ian Chodera

Posts: 1
Registered: 2/19/07
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 27, 2015 3:39 AM   in response to: Sean Hoffman in response to: Sean Hoffman
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian

Sean Hoffman wrote:
Greetings folks, can anyone reproduce the following:

1. Create a new blank 32 bit Windows FMX application, using the new compiler
2. Uncheck "use classic borland compiler"
3. Uncheck "link with dynamic runtime library"
4. Uncheck "build with runtime packages"
5. Drop on a TFDPhysSQLiteDriverLink component on the main form.
6. Try to build.

I get the following error:

ilink32 command line
d:\rs10\bin\ilink32.exe -G8 -L.\Win32\Debug;d:\rs10\lib\Win32\debug;d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;
d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP -j.\Win32\Debug;d:\rs10\lib\Win32\debug;
d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP
-l.\Win32\Debug -v -Gn -GA"C:\Users\sean\AppData\Local\Temp\vfsE49D.tmp"="E:\src\TestRS10\Main.fmx" -aa -V5.0 -Tpe c0fmx32w memmgr.lib sysinit.obj
.\Win32\Debug\TestRS10.obj .\Win32\Debug\Main.obj , .\Win32\Debug\TestRS10.exe , .\Win32\Debug\TestRS10.map , rtl.lib fmx.lib FireDACSqliteDriver.lib
FireDACCommonDriver.lib FireDACCommon.lib xmlrtl.lib dbrtl.lib import32.lib cp32mt.lib , , TestRS10.res
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilc: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ild: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilf: 0x00010000 / 0x0a000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ils: 0x0003b000 / 0x08000000
[ilink32 Warning] Warning: unknown heap name : 0x08000000 / 0x08000000
[ilink32 Warning] Warning: Error detected (LME288)
[ilink32 Error] Error: Unable to perform link
Failed
Elapsed time: 00:00:04.8

Sean Hoffman

Posts: 126
Registered: 3/28/99
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 27, 2015 3:50 AM   in response to: Ian Chodera in response to: Ian Chodera
Ian Chodera wrote:
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian


Ian, thank you for your reply. I believe the linker needs to be re-written, but for whatever reason that hasn't happened yet. In any case, the most consistent way I've found to avoid this error is to open the IDE independently and then open a project from within the IDE. Do not EVER click on a project file in Explorer and open the IDE by extension association. Thus far that's worked for me since having this problem (crossing my fingers).
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 17, 2015 7:52 AM   in response to: Sean Hoffman in response to: Sean Hoffman
Sean Hoffman wrote:
Ian Chodera wrote:
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian


Ian, thank you for your reply. I believe the linker needs to be re-written, but for whatever reason that hasn't happened yet. In any case, the most consistent way I've found to avoid this error is to open the IDE independently and then open a project from within the IDE. Do not EVER click on a project file in Explorer and open the IDE by extension association. Thus far that's worked for me since having this problem (crossing my fingers).

I currently get the problem around once every two weeks now. Opening the project file from within the IDE does not work for me. Ritual dances with removing temp files, changing page file size and reboot-reboot-rebooting sometimes help; at the moment it doesn't and now I'm close to sacrificing a black goat when the next full moon comes around.

Why, I am a bit frustrated, yes.

Oddly enough, when building my projects through msbuild instead of the IDE, everything works fine. Does that give any clue as to where the problem may lie?
Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 17, 2015 8:34 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Hi - I can understand your frustration, because I have similar problems with the linker.
How do you use MSBuild - I tried it for my project.
But I get "There is no target in the project" as answer from MSBuild.
What command line did you use - can you give an example.
Regards Oliver
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 17, 2015 11:34 PM   in response to: Oliver Weinheimer in response to: Oliver Weinheimer
Oliver Weinheimer wrote:
Hi - I can understand your frustration, because I have similar problems with the linker.
How do you use MSBuild - I tried it for my project.
But I get "There is no target in the project" as answer from MSBuild.
What command line did you use - can you give an example.
Regards Oliver

Probably this is because you need to call rsvars.bat first, to set up the proper environment.

The relevant snippet from my build command script:
call "C:\Program Files (x86)\Embarcadero\Studio\17.0\bin\rsvars.bat"
msbuild.exe myProject.groupproj /t:Make /p:config=Debug
Alternatively, you can pass /t:Build and/or /p:config=Release.

HTH
Jeroen

Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 18, 2015 1:31 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Thanks for your answer!
Does not work for me - msbuild does not like my project files - but also sample project files distributed with RAD Studio 10 does not work on my PC.
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 18, 2015 1:33 AM   in response to: Oliver Weinheimer in response to: Oliver Weinheimer
Oliver Weinheimer wrote:
Thanks for your answer!
Does not work for me - msbuild does not like my project files - but also sample project files distributed with RAD Studio 10 does not work on my PC.

What version of msbuild do you use?
Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 18, 2015 1:37 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Microsoft (R) Build Engine Version 3.5.30729.5420

It is too old?
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 18, 2015 1:43 AM   in response to: Oliver Weinheimer in response to: Oliver Weinheimer
Oliver Weinheimer wrote:
Microsoft (R) Build Engine Version 3.5.30729.5420

It is too old?

I don't know... I cannot find any mention of a minimal version of msbuild to use in the documentation of Embarcadero. FWIW, I use 4.0.30319.34209; the version coming with .Net 4. You could give it a try.
Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 18, 2015 1:48 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Jeroen ter Hofstede wrote:
Oliver Weinheimer wrote:
Microsoft (R) Build Engine Version 3.5.30729.5420

It is too old?

I don't know... I cannot find any mention of a minimal version of msbuild to use in the documentation of Embarcadero. FWIW, I use 4.0.30319.34209; the version coming with .Net 4. You could give it a try.

This version is also on my PC but cmd takes the older one - it is maybe a path thing - I will check this ...
Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 8, 2016 5:32 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
I am now able to compile my project with MSBuild from command line.
I am using this line:

MSBuild /p:Platform=Win64 /v:diag myproject_CX.cbproj /p:config=Debug

One problem was that the file myproject_CX.cbproj contained an additional line with: </ProjectExtensions>.

After deleting this line MSBuild works.
After some builds within the IDE the additional </ProjectExtensions> was again in the cbproj file. Seems to be a problem of the IDE saving the cbproj file!?

One great advantage of using MSBuild is that linker heaps are displayed if a link fails.
Until now i was copying the ilink64 command line from the messages window in order to get the linker heaps information - that was a pain. Via MSBuild it is much easier.
Vladimir Ulchenko

Posts: 248
Registered: 1/12/00
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 21, 2015 2:08 AM   in response to: Oliver Weinheimer in response to: Oliver Weinheimer
On Thu, 17 Dec 2015 08:34:27 -0800, Oliver Weinheimer <> wrote:

Hi - I can understand your frustration, because I have similar problems with the linker.

guess why I stopped using ilink ~10 years ago, switched to ulink and never looked back
anticipating possible questions I must emphasize that I have no idea how well it supports bcb versions more recent than 2007 I've been using

--
Vladimir Ulchenko aka vavan
Oliver Weinheimer

Posts: 73
Registered: 8/20/04
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 21, 2015 8:13 AM   in response to: Vladimir Ulchenko in response to: Vladimir Ulchenko
I will give it a try ...

but most important things for C++Builder should definitly be the compilers and linkers.
Embarcadero SOLD RAD Studio 10 with bcc64 and bcc32c with all optimizations off, that was not nice.
The linker is not working reliable since years.
For me it does not make sense to use another linker, maybe it makes more sense not using C++Builder at all.
The linker should be one of the core parts of C++Builder und they treat it as a useless piece of software!
At least it would be a great sign if there say that there is hope to get a new linker.
But I never read it on any roadmap.
Vladimir Ulchenko

Posts: 248
Registered: 1/12/00
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 21, 2015 11:30 PM   in response to: Oliver Weinheimer in response to: Oliver Weinheimer
On Mon, 21 Dec 2015 08:13:48 -0800, Oliver Weinheimer <> wrote:

The linker is not working reliable since years.

sad but true

For me it does not make sense to use another linker, maybe it makes more sense not using C++Builder at all.

sure, if you have no vcl specific code there's no point to use bcb

--
Vladimir Ulchenko aka vavan
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 23, 2015 4:13 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Jeroen ter Hofstede wrote:
Sean Hoffman wrote:
Ian Chodera wrote:
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian


Ian, thank you for your reply. I believe the linker needs to be re-written, but for whatever reason that hasn't happened yet. In any case, the most consistent way I've found to avoid this error is to open the IDE independently and then open a project from within the IDE. Do not EVER click on a project file in Explorer and open the IDE by extension association. Thus far that's worked for me since having this problem (crossing my fingers).

I currently get the problem around once every two weeks now. Opening the project file from within the IDE does not work for me. Ritual dances with removing temp files, changing page file size and reboot-reboot-rebooting sometimes help; at the moment it doesn't and now I'm close to sacrificing a black goat when the next full moon comes around.

Why, I am a bit frustrated, yes.

Oddly enough, when building my projects through msbuild instead of the IDE, everything works fine. Does that give any clue as to where the problem may lie?

I created a trivial C program: 'int main () { return 0; }' and compiled it in the IDE.
Linking failed (in IDE), as expected. Linking with msbuild succeeded.

I fired up procmon and made traces of ilink32.exe, both when started from IDE and from msbuild. I took the ilink32.exe process invocation from both traces (only differing in details) and put them in a batch file. When running the batch file, both succeeded.

(By the way: both traces are more or less the same upto and including the point that ilink32.exe probes whether the ilc, .ild, .ilf, .ils, and .tds files exist. After that point the successful invocation goes on to create these files, while the failing one cleans up and exits. No clue as to why.)

Since about an hour ago, also the msbuild-invoked link and the previous successful links from the batch file also fail.

From previous posts I see this problem already exists for years. This is completely unacceptable. We cannot afford the risk of development halting or builds failing with no reliable solution or even workaround.
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 24, 2015 1:04 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Jeroen ter Hofstede wrote:
Jeroen ter Hofstede wrote:
Sean Hoffman wrote:
Ian Chodera wrote:
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian


Ian, thank you for your reply. I believe the linker needs to be re-written, but for whatever reason that hasn't happened yet. In any case, the most consistent way I've found to avoid this error is to open the IDE independently and then open a project from within the IDE. Do not EVER click on a project file in Explorer and open the IDE by extension association. Thus far that's worked for me since having this problem (crossing my fingers).

I currently get the problem around once every two weeks now. Opening the project file from within the IDE does not work for me. Ritual dances with removing temp files, changing page file size and reboot-reboot-rebooting sometimes help; at the moment it doesn't and now I'm close to sacrificing a black goat when the next full moon comes around.

Why, I am a bit frustrated, yes.

Oddly enough, when building my projects through msbuild instead of the IDE, everything works fine. Does that give any clue as to where the problem may lie?

I created a trivial C program: 'int main () { return 0; }' and compiled it in the IDE.
Linking failed (in IDE), as expected. Linking with msbuild succeeded.

I fired up procmon and made traces of ilink32.exe, both when started from IDE and from msbuild. I took the ilink32.exe process invocation from both traces (only differing in details) and put them in a batch file. When running the batch file, both succeeded.

(By the way: both traces are more or less the same upto and including the point that ilink32.exe probes whether the ilc, .ild, .ilf, .ils, and .tds files exist. After that point the successful invocation goes on to create these files, while the failing one cleans up and exits. No clue as to why.)

Since about an hour ago, also the msbuild-invoked link and the previous successful links from the batch file also fail.

From previous posts I see this problem already exists for years. This is completely unacceptable. We cannot afford the risk of development halting or builds failing with no reliable solution or even workaround.

Oh well.. Created a Quality Central issue for it: RSP-13247 (https://quality.embarcadero.com/browse/RSP-13247).
Jeroen ter Hofs...

Posts: 11
Registered: 10/7/15
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 11, 2016 6:22 AM   in response to: Jeroen ter Hofs... in response to: Jeroen ter Hofs...
Jeroen ter Hofstede wrote:
Jeroen ter Hofstede wrote:
Jeroen ter Hofstede wrote:
Sean Hoffman wrote:
Ian Chodera wrote:
The LME288 error has been an issue with ILink32 since before the great flood (at least XE3). Search google for lots of suggestions on how to fix it. The problem is that none of the suggestions actually works for everyone. Suggestions include removing temp files, rebooting, re-installing the IDE, re-installing windows, modifying the windows page file and so on. There are multiple reports of it on Quality Central.

The biggest problem is that once it strikes one project, ALL of your projects are affected. You are unable to rebuild ANY project until it is magically goes away again. And it happens completely out of the blue, its not related to any particular change to your source code.

Please. Please Embarcadero do make an attempt to fix this, look at the source for Ilink32 and have a guess at what might go wrong, don't just mark it as 'can't reproduce again'

Regards
Ian


Ian, thank you for your reply. I believe the linker needs to be re-written, but for whatever reason that hasn't happened yet. In any case, the most consistent way I've found to avoid this error is to open the IDE independently and then open a project from within the IDE. Do not EVER click on a project file in Explorer and open the IDE by extension association. Thus far that's worked for me since having this problem (crossing my fingers).

I currently get the problem around once every two weeks now. Opening the project file from within the IDE does not work for me. Ritual dances with removing temp files, changing page file size and reboot-reboot-rebooting sometimes help; at the moment it doesn't and now I'm close to sacrificing a black goat when the next full moon comes around.

Why, I am a bit frustrated, yes.
[...]

Oh well.. Created a Quality Central issue for it: RSP-13247 (https://quality.embarcadero.com/browse/RSP-13247).

Created a support case this morning and was helped almost immediately :)

According to the support desk this is a problem with fragmentation of the address space, caused by DLLs loaded in various places. The linker tries to reserve a large amount of contiguous memory for several heaps and fails due to this fragmentation. I was sent the ilink32.exe of C++ Builder 10 Update 1, that has an option to set the size of these heaps.
Linking now succeeds again with this new linker - even though I haven't used the new heap size option...
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 23, 2015 9:50 AM   in response to: Ian Chodera in response to: Ian Chodera
Ian wrote:

The LME288 error has been an issue with ILink32 since before the great
flood (at least XE3).

I get the error sometimes in XE2.

--
Remy Lebeau (TeamB)
Herve NOEL

Posts: 2
Registered: 9/11/08
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 27, 2015 2:57 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
Ian wrote:

The LME288 error has been an issue with ILink32 since before the great
flood (at least XE3).

I get the error sometimes in XE2.

--
Remy Lebeau (TeamB)

Hi,

For me, un-installing GIMP allowed me to make 2 successfull links, and then the problem came back. I have XE5 on Windows 8 and a pretty large project that I am working on as a hobby since 1998 (with older versions obviously). Maybe I should un-install something each time I want to make a link...

Frustrating to say the least.

Herve
Don DeWitt

Posts: 1
Registered: 11/14/05
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 2, 2016 12:13 PM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
Remy Lebeau (TeamB) wrote:
Ian wrote:

The LME288 error has been an issue with ILink32 since before the great
flood (at least XE3).

I get the error sometimes in XE2.

--
Remy Lebeau (TeamB)

I am getting the error today (again) in XE2. Over the years, I have gotten this error numerous times, only "hand-waving" seemed to fix it in the past. Today, NOTHING fixes it. The embarcadero site gets zero hits when you search for (LME286) or "unknown heap name". All the error reports are closed as "not reproducible". AAAARRRGGGGHHH. Your customers have been reproducing this error for YEARS! How about getting around to FIXING IT?
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 2, 2016 1:05 PM   in response to: Don DeWitt in response to: Don DeWitt
Don wrote:

Over the years, I have gotten this error numerous times, only
"hand-waving" seemed to fix it in the past. Today, NOTHING
fixes it.

What is really sad is that at my day job, I'm still working in BCB6, and
our main product (a 20MB exe) has been compiling fine for years, and only
just recently started experiencing similar linker errors. On my dev machine,
I can't link it AT ALL anymore :-( But on our build machine, it SOMETIMES
links OK, and when it does fail a full re-build USUALLY works, but not always.

--
Remy Lebeau (TeamB)
Vladimir Ulchenko

Posts: 248
Registered: 1/12/00
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 3, 2016 1:28 AM   in response to: Remy Lebeau (Te... in response to: Remy Lebeau (Te...
On Tue, 2 Feb 2016 13:05:13 -0800, Remy Lebeau (TeamB) <no dot spam at no dot spam dot com> wrote:

What is really sad is that at my day job, I'm still working in BCB6, and
our main product (a 20MB exe) has been compiling fine for years, and only
just recently started experiencing similar linker errors. On my dev machine,
I can't link it AT ALL anymore :-( But on our build machine, it SOMETIMES
links OK, and when it does fail a full re-build USUALLY works, but not always.

time to try ulink? ;)
I switched to it when encountered similar problems after migrating from bcb5 to bds2006, stopped using ilink ~10 years ago and never looked
back

--
Vladimir Ulchenko aka vavan
Sean Hoffman

Posts: 126
Registered: 3/28/99
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 3, 2016 4:39 AM   in response to: Vladimir Ulchenko in response to: Vladimir Ulchenko
Vladimir Ulchenko wrote:
On Tue, 2 Feb 2016 13:05:13 -0800, Remy Lebeau (TeamB) <no dot spam at no dot spam dot com> wrote:

What is really sad is that at my day job, I'm still working in BCB6, and
our main product (a 20MB exe) has been compiling fine for years, and only
just recently started experiencing similar linker errors. On my dev machine,
I can't link it AT ALL anymore :-( But on our build machine, it SOMETIMES
links OK, and when it does fail a full re-build USUALLY works, but not always.

time to try ulink? ;)
I switched to it when encountered similar problems after migrating from bcb5 to bds2006, stopped using ilink ~10 years ago and never looked
back

--
Vladimir Ulchenko aka vavan

Is ulink a commercial product? Do you happen to have a company site?
Vladimir Ulchenko

Posts: 248
Registered: 1/12/00
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 3, 2016 7:42 AM   in response to: Sean Hoffman in response to: Sean Hoffman
On Wed, 3 Feb 2016 04:39:11 -0800, Sean Hoffman <> wrote:

Is ulink a commercial product? Do you happen to have a company site?

it is one-man product freely distributed from his ftp mentioned here many times
no site currently available afaik

--
Vladimir Ulchenko aka vavan
Herve NOEL

Posts: 2
Registered: 9/11/08
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 27, 2015 2:55 PM   in response to: Sean Hoffman in response to: Sean Hoffman
Sean Hoffman wrote:
Greetings folks, can anyone reproduce the following:

1. Create a new blank 32 bit Windows FMX application, using the new compiler
2. Uncheck "use classic borland compiler"
3. Uncheck "link with dynamic runtime library"
4. Uncheck "build with runtime packages"
5. Drop on a TFDPhysSQLiteDriverLink component on the main form.
6. Try to build.

I get the following error:

ilink32 command line
d:\rs10\bin\ilink32.exe -G8 -L.\Win32\Debug;d:\rs10\lib\Win32\debug;d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;
d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP -j.\Win32\Debug;d:\rs10\lib\Win32\debug;
d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP
-l.\Win32\Debug -v -Gn -GA"C:\Users\sean\AppData\Local\Temp\vfsE49D.tmp"="E:\src\TestRS10\Main.fmx" -aa -V5.0 -Tpe c0fmx32w memmgr.lib sysinit.obj
.\Win32\Debug\TestRS10.obj .\Win32\Debug\Main.obj , .\Win32\Debug\TestRS10.exe , .\Win32\Debug\TestRS10.map , rtl.lib fmx.lib FireDACSqliteDriver.lib
FireDACCommonDriver.lib FireDACCommon.lib xmlrtl.lib dbrtl.lib import32.lib cp32mt.lib , , TestRS10.res
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilc: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ild: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilf: 0x00010000 / 0x0a000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ils: 0x0003b000 / 0x08000000
[ilink32 Warning] Warning: unknown heap name : 0x08000000 / 0x08000000
[ilink32 Warning] Warning: Error detected (LME288)
[ilink32 Error] Error: Unable to perform link
Failed
Elapsed time: 00:00:04.8


Hi,

For me, un-installing GIMP allowed me to make 2 successfull links, and then the problem came back. I have XE5 on Windows 8 and a pretty large project that I am working on as a hobby since 1998 (with older versions obviously). Maybe I should un-install something each time I want to make a link...

Frustrating to say the least.

Herve
Borja Serrano

Posts: 53
Registered: 1/10/13
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 5, 2016 10:57 AM   in response to: Sean Hoffman in response to: Sean Hoffman
Have you tried to make ilink32 LARGEADDRESSAWARE? You can use this tool: http://cc.embarcadero.com/Item/30459
Guest
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?
Click to report abuse...   Click to reply to this thread Reply
  Posted: Apr 13, 2016 10:51 PM   in response to: Borja Serrano in response to: Borja Serrano
Borja Serrano wrote:
Have you tried to make ilink32 LARGEADDRESSAWARE? You can use this tool: http://cc.embarcadero.com/Item/30459

I tried it and it worked like magic!
Adam Weles

Posts: 1
Registered: 2/24/17
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jan 24, 2017 2:16 PM   in response to: Guest in response to: Guest
Grzegorz Majcher wrote:
Borja Serrano wrote:
Have you tried to make ilink32 LARGEADDRESSAWARE? You can use this tool: http://cc.embarcadero.com/Item/30459

I tried it and it worked like magic!


LAMarker how to use? Plaease help me.

Wiktor Wandacho...

Posts: 2
Registered: 12/18/14
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: May 17, 2017 7:02 AM   in response to: Adam Weles in response to: Adam Weles
Adam Weles wrote:
Grzegorz Majcher wrote:
Borja Serrano wrote:
Have you tried to make ilink32 LARGEADDRESSAWARE? You can use this tool: http://cc.embarcadero.com/Item/30459

I tried it and it worked like magic!


LAMarker how to use? Plaease help me.


For RAD Studio 10.2 - as Administrator run in command prompt:

LAMarker.exe -M -F"C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\ilink32.exe"

Works like a charm in Windows 10 64-bit :)
Harry Bego

Posts: 22
Registered: 1/27/09
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 19, 2016 7:53 AM   in response to: Sean Hoffman in response to: Sean Hoffman
I have been getting the LME288 error on and off today; using XE7, bcc32 compiler, Win7.

However, I noticed that I only got it when free memory was below 1GB or so. Windows Update was running and using a lot of memory. After I adjusted that to never check for updates, and restarted, I didn't see the error again.

So as far as I see, the LME error is a case of an obscure and unhelpful error message. It could have said "insufficient memory" ...

Harry
Emanuel Falkena...

Posts: 3
Registered: 1/20/12
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Apr 11, 2017 3:16 PM   in response to: Sean Hoffman in response to: Sean Hoffman
Hi,

For reasons totally unknown, I just started to get the LME288 in both XE10.1 and XE5, even though both have been linking flawlessly for years??!

Anyway, here is the solution, which I found at http://stackoverflow.com/questions/23107535/c-builder-xe5-error-detected-lme288 :

Essentially, the linker runs out of heap - notice the "Warning: unknown heap name : 0x08000000 / 0x08000000" in your log, where the "unknown heap name" is actually "tds". What you need is to give the linker more of that heap, and there is fortunately a parameter for that: -GHtds=0x0A000000 . Specify that string in the "Additional options" section of the linker section and you're up and running again.

What I would like to know is what might have happened that the linker suddenly goes out of that heap? Is there a global setting in some file that would have changed? Thx for your ideas!

Sean Hoffman wrote:
Greetings folks, can anyone reproduce the following:

1. Create a new blank 32 bit Windows FMX application, using the new compiler
2. Uncheck "use classic borland compiler"
3. Uncheck "link with dynamic runtime library"
4. Uncheck "build with runtime packages"
5. Drop on a TFDPhysSQLiteDriverLink component on the main form.
6. Try to build.

I get the following error:

ilink32 command line
d:\rs10\bin\ilink32.exe -G8 -L.\Win32\Debug;d:\rs10\lib\Win32\debug;d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;
d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP -j.\Win32\Debug;d:\rs10\lib\Win32\debug;
d:\rs10\lib\win32c\release;d:\rs10\lib\win32\release;d:\rs10\lib\win32\release\psdk;C:\Users\Public\Documents\Embarcadero\Studio\17.0\DCP
-l.\Win32\Debug -v -Gn -GA"C:\Users\sean\AppData\Local\Temp\vfsE49D.tmp"="E:\src\TestRS10\Main.fmx" -aa -V5.0 -Tpe c0fmx32w memmgr.lib sysinit.obj
.\Win32\Debug\TestRS10.obj .\Win32\Debug\Main.obj , .\Win32\Debug\TestRS10.exe , .\Win32\Debug\TestRS10.map , rtl.lib fmx.lib FireDACSqliteDriver.lib
FireDACCommonDriver.lib FireDACCommon.lib xmlrtl.lib dbrtl.lib import32.lib cp32mt.lib , , TestRS10.res
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilc: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ild: 0x00010000 / 0x08000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ilf: 0x00010000 / 0x0a000000
[ilink32 Warning] Warning: E:/src/TestRS10/Win32/Debug/TestRS10.ils: 0x0003b000 / 0x08000000
[ilink32 Warning] Warning: unknown heap name : 0x08000000 / 0x08000000
[ilink32 Warning] Warning: Error detected (LME288)
[ilink32 Error] Error: Unable to perform link
Failed
Elapsed time: 00:00:04.8

Ted Lyngmo

Posts: 117
Registered: 10/3/06
Re: C++ Builder Seattle- Link error LME288. Can you reproduce?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Apr 12, 2017 8:57 AM   in response to: Emanuel Falkena... in response to: Emanuel Falkena...
Emanuel Falkenauer wrote:
Hi,

For reasons totally unknown, I just started to get the LME288 in both XE10.1 and XE5, even though both have been linking flawlessly for years??!

Anyway, here is the solution, which I found at http://stackoverflow.com/questions/23107535/c-builder-xe5-error-detected-lme288 :

Essentially, the linker runs out of heap - notice the "Warning: unknown heap name : 0x08000000 / 0x08000000" in your log, where the "unknown heap name" is actually "tds". What you need is to give the linker more of that heap, and there is fortunately a parameter for that: -GHtds=0x0A000000 . Specify that string in the "Additional options" section of the linker section and you're up and running again.

What I would like to know is what might have happened that the linker suddenly goes out of that heap? Is there a global setting in some file that would have changed? Thx for your ideas!

I don't have an explanation, but perhaps a simpler solution - it's been working 100% for me without having to specify additional linker options.

I got the same when using the new free C++ compiler (https://community.embarcadero.com/blogs/entry/a-new-edition-of-our-free-c-compiler) even when compiling a small "Hello world" type of program.
I don't get the problem in my 10.1 Berlin environment though.

The difference is that I run the free compiler via wine on a 64 bit linux machine and Berlin on my 32 bit Windows machine.

Remedy
ILINK32.EXE must be patched to be LARGEADDRESSAWARE (https://msdn.microsoft.com/en-us/library/wz223b1z.aspx)

Ways to do it yourself:
http://stackoverflow.com/questions/28929516/c-builder-xe7-lme288-error/34819111#34819111

If you trust the guy who wrote the answer above, you can download a patched version here:
RAD Studio 10 Seattle: https://s3.amazonaws.com/public-mfay/ilink32.exe
RAD Studio 10.1 Berlin: https://s3.amazonaws.com/public-mfay/ilink32-10.1.exe

I downloaded the patched version and it's working perfectly.

10.2 users probably need to patch themselves.

Best regards,
๐“ฃ๐“ฎ๐“ญ ๐“›๐”‚๐“ท๐“ฐ๐“ถ๐“ธ
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02