I've solved the conflicting library problems, I believe. At least I got rid
of all the problems of library functions being multiple defined, by
controlling the order of linking libraries and forcing the linker to ignore
one specific library (libcmtd.lib).
Since you haven't heard of the __HUGE unresolved extern, maybe it's a
Windows library problem. Thanks. If I figure it out, I'll let you know.
Jim Scott
-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Ulf Lamping
Sent: Friday, September 24, 2004 11:22 AM
To: Ethereal development
Subject: Re: [Ethereal-dev] Unresolved extern __HUGE when linking to
anethereal library on Windows XP
jscott wrote:
> I have a version of the ethereal code which compiles to a static
> library undeer MSVC7. When I try to link this with an application, I
> get the error:
>
>
>
> ethereal_d.lib(ftype-double.obj) : error LNK2001: unresolved external
> symbol __HUGE
>
>
>
> Looking at the file ftype-double.c, the only reference to HUGE is in
> the line:
>
>
>
> else if (fv->value.floating == HUGE_VAL) {
>
> logfunc("\"%s\" causes floating-point overflow.", s);
>
>
>
> Jim Scott
>
I don't know about the specific HUGE problem.
But it's known that Ethereal won't compile on MSVC7 for conflicting
MSVCRT.DLL reasons.
Regards, ULFL
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
