PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Autres forums > Forum Programmation & Conception > comp.lang.cplus > with Linker errors
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
with Linker errors

Réponse
 
LinkBack Outils de la discussion
Vieux 16/07/2008, 00h03   #1
kleen
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut with Linker errors

Hi ~

I'm getting these linker errors (seem to be run-time library related).
I'm not sure how to approach it. Any ideas please? the project is C/C+
+ code. And nowhere do we have a call to fflush, at least as far as I
have searched.


ERROR 18: EXTERNAL SYMBOL UNRESOLVED
UNRESOLVED EXTERNAL SYMBOL(S):
_fflush in C:\VC60\libc.lib(closeall.c)
Cannot find replacement: ssi_not_supported
_fflush in C:\VC60\libc.lib(fflush.c)
Cannot find replacement: ssi_not_supported
__imp__SetHandleCount@4 in C:\VC60\libc.lib(ioinit.c)
__imp__GetStdHandle@4 in C:\VC60\libc.lib(ioinit.c)
__imp__GetFileType@4 in C:\VC60\libc.lib(ioinit.c)
__imp__GetStartupInfoA@4 in C:\VC60\libc.lib(ioinit.c)
__imp__GetLastError@0 in C:\VC60\libc.lib(commit.c)
__imp__FlushFileBuffers@4 in C:\VC60\libc.lib(commit.c)
__imp__GetLastError@0 in C:\VC60\libc.lib(write.c)
__imp__WriteFile@20 in C:\VC60\libc.lib(write.c)
__imp__SetStdHandle@8 in C:\VC60\libc.lib(osfinfo.c)
__imp__GetLastError@0 in C:\VC60\libc.lib(osfinfo.c)
__imp__GetFileType@4 in C:\VC60\libc.lib(osfinfo.c)
__imp__GetLastError@0 in C:\VC60\libc.lib(lseek.c)
__imp__SetFilePointer@16 in C:\VC60\libc.lib(lseek.c)
__imp__GetCommandLineA@0 in C:\VC60\libc.lib(crt0.c)
__imp__GetVersion@0 in C:\VC60\libc.lib(crt0.c)
__imp__WriteFile@20 in C:\VC60\libc.lib(crt0msg.c)
__imp__GetStdHandle@4 in C:\VC60\libc.lib(crt0msg.c)
__imp__GetModuleFileNameA@12 in C:
\VC60\libc.lib(crt0msg.c)
__imp__HeapDestroy@4 in C:\VC60\libc.lib(heapinit.c)
__imp__HeapCreate@12 in C:\VC60\libc.lib(heapinit.c)
__imp__VirtualFree@12 in C:\VC60\libc.lib(heapinit.c)
__imp__HeapFree@12 in C:\VC60\libc.lib(heapinit.c)
__imp__FreeEnvironmentStringsA@4 in C:
\VC60\libc.lib(a_env.c)
__imp__FreeEnvironmentStringsW@4 in C:
\VC60\libc.lib(a_env.c)
__imp__WideCharToMultiByte@32 in C:\VC60\libc.lib(a_env.c)
__imp__GetEnvironmentStrings@0 in C:\VC60\libc.lib(a_env.c)
__imp__GetEnvironmentStringsW@0 in C:\VC60\libc.lib(a_env.c)
__imp__GetModuleFileNameA@12 in C:
\VC60\libc.lib(stdargv.c)
__imp__UnhandledExceptionFilter@4 in C:
\VC60\libc.lib(winxfltr.c)
__imp__GetProcAddress@8 in C:\VC60\libc.lib(crtmbox.c)
__imp__LoadLibraryA@4 in C:\VC60\libc.lib(crtmbox.c)
__imp__GetCPInfo@8 in C:\VC60\libc.lib(mbctype.c)
__imp__GetACP@0 in C:\VC60\libc.lib(mbctype.c)
__imp__GetOEMCP@0 in C:\VC60\libc.lib(mbctype.c)
__imp__HeapAlloc@12 in C:\VC60\libc.lib(sbheap.c)
__imp__HeapFree@12 in C:\VC60\libc.lib(sbheap.c)
__imp__VirtualFree@12 in C:\VC60\libc.lib(sbheap.c)
__imp__VirtualAlloc@16 in C:\VC60\libc.lib(sbheap.c)
__imp__HeapReAlloc@16 in C:\VC60\libc.lib(sbheap.c)
__imp__IsBadWritePtr@8 in C:\VC60\libc.lib(sbheap.c)
__imp__MultiByteToWideChar@24 in C:\VC60\libc.lib(a_str.c)
__imp__GetStringTypeA@20 in C:\VC60\libc.lib(a_str.c)
__imp__GetStringTypeW@16 in C:\VC60\libc.lib(a_str.c)
__imp__WideCharToMultiByte@32 in C:\VC60\libc.lib(a_map.c)
__imp__MultiByteToWideChar@24 in C:\VC60\libc.lib(a_map.c)
__imp__LCMapStringA@24 in C:\VC60\libc.lib(a_map.c)
__imp__LCMapStringW@24 in C:\VC60\libc.lib(a_map.c)

1 ERROR(S) 75 WARNING(S).
*** Error code 1
  Réponse avec citation
Vieux 16/07/2008, 00h18   #2
Alf P. Steinbach
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: with Linker errors

* kleen:
> Hi ~
>
> I'm getting these linker errors (seem to be run-time library related).
> I'm not sure how to approach it.


See the FAQ item on how to post a question about Code That Does Not Work.


> Any ideas please?


See above.


> the project is C/C++ code.


Is it C, C++ or a mixture? Anyway, reduce the problem to a smallest possible
program, then if still necessary do as noted above.


> And nowhere do we have a call to fflush, at least as far as I
> have searched.


You can be reasonably sure that the runtime library calls fflush.

>
>
> ERROR 18: EXTERNAL SYMBOL UNRESOLVED
> UNRESOLVED EXTERNAL SYMBOL(S):
> _fflush in C:\VC60\libc.lib(closeall.c)



Cheers, & hth.,

- Alf

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
  Réponse avec citation
Vieux 16/07/2008, 00h51   #3
kleen
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: with Linker errors

On Jul 15, 6:18 pm, "Alf P. Steinbach" <al...@start.no> wrote:
> * kleen:
>
> > Hi ~

>
> > I'm getting these linker errors (seem to be run-time library related).
> > I'm not sure how to approach it.

>
> See the FAQ item on how to post a question about Code That Does Not Work.
>
> > Any ideas please?

>
> See above.
>
> > the project is C/C++ code.

>
> Is it C, C++ or a mixture? Anyway, reduce the problem to a smallest possible
> program, then if still necessary do as noted above.
>
> > And nowhere do we have a call to fflush, at least as far as I
> > have searched.

>
> You can be reasonably sure that the runtime library calls fflush.
>
>
>
> > ERROR 18: EXTERNAL SYMBOL UNRESOLVED
> > UNRESOLVED EXTERNAL SYMBOL(S):
> > _fflush in C:\VC60\libc.lib(closeall.c)

>
> Cheers, & hth.,
>
> - Alf
>
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is it such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?


It's mixed code. btw, where can I read the FAQ? couldn't find it.
  Réponse avec citation
Vieux 16/07/2008, 04h45   #4
Ian Collins
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: with Linker errors

kleen wrote:
>
> It's mixed code. btw, where can I read the FAQ? couldn't find it.


Did you have to quote the entire message to ask this?

The link is is posted regularly: http://www.parashift.com/c++-faq-lite/

Make sure you link mixed C and C++ applications this the C++ compiler.

--
Ian Collins.
  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 16h51.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,10816 seconds with 12 queries