Hi,
I'm using the C++Builder 5 under Windows XP Professional.

Very often I get the Linker-Error "[Linker Error] Unresolved external
'__linkproc__ intover' referenced from ...

Only closing the C++-Builder and deleting all the following files help me to
recompile it:
*.obj;*.tds;*.~*;*.tmp;*.bak;*.exe;*.bpl;*.cgl;*.lib;*.bpi;*.dsk;*.cgi

Therefore a rebuild-all of a big project costs much time, it would be good
to know the reason why this error-message comes and how I can eleminate it.

At the moment I can't update to C++Builder 6, because I'm in a hurry to end
a project.

Therefore:
Please can you help me avoid this error-message? What can I do?

Another unlovely thing with C++Builder 5 under WindowsXP is, that the
debugger very often hangs up.
Do you have ideas what to do against this.

If anybody knows solutions for one of this problems an can mail it to me, it
would be very nice.
Please help me !!!

Thanks in advance
Klaus Zaeper
mailto: Klaus@Zaeper.de

On Thu, 7 Aug 2003 14:49:46 +0200, "Klaus Zaeper" 
wrote:

>Hi,
>I'm using the C++Builder 5 under Windows XP Professional.
>
>Very often I get the Linker-Error "[Linker Error] Unresolved external
>'__linkproc__ intover' referenced from ...
>

http://makeashorterlink.com/?F28351111

where someone came up with the following solution ...



The way to make the code link anyway is to declare a @@intover
function, i.e. by including the following code in an *.asm file an add
it to your project:


--------intover.asm begin-------

; This file contains a dummy define of the intover function used to
prevent
; the linkproc _intover_ linker error in Borland builds
;


..586
..model flat
EXTERNDEF @@intover: FAR
..code

@@intover PROC FAR
db 0c3h
@@intover ENDP

end
--------intover.asm end-------


>
>Another unlovely thing with C++Builder 5 under WindowsXP is, that the
>debugger very often hangs up.
>Do you have ideas what to do against this.

search here
http://groups.google.com/advanced_group_search

"with all the words" set to
debugger hang

newsgroup *cppbuilder*

You might get some ideas.  The ide newsgroup is the best place to ask
about debugger problems.

Graeme

Torsten Franz (TeamBeer) wrote:

> > I'm using the C++Builder 5 under Windows XP Professional.
> >
> > Very often I get the Linker-Error "[Linker Error] Unresolved external
> > '__linkproc__ intover' referenced from ...

> We were once plagued by this error.
> The reason for us was too many/too long include paths.
> So try to reduce the number of include paths
>
> HTH
> Torsten

I'll second that...

Its not reproducible 100% of the time, but is definately somehow related to
the number of include paths. I think it may somehow actually be linked to
the length of the options source file, which is clearly altered by the
number of include paths.

I've had extremely basic projects that will suddenly start throwing this
error every 3rd or 4th compile immediately after i've just added a whole
stack of include dir's.

Vesty.

> I'm using the C++Builder 5 under Windows XP Professional.
>
> Very often I get the Linker-Error "[Linker Error] Unresolved external
> '__linkproc__ intover' referenced from ...
>
> Only closing the C++-Builder and deleting all the following files
> help me to recompile it:
> *.obj;*.tds;*.~*;*.tmp;*.bak;*.exe;*.bpl;*.cgl;*.lib;*.bpi;*.dsk;*.cgi

We were once plagued by this error.
The reason for us was too many/too long include paths.
So try to reduce the number of include paths

HTH
Torsten