Linker error LNK1218 on XP checked build

Has anybody seen this linker error before.

I am trying to compile my NDIS50 protocol driver.

I end up getting this arcane linker error LNK1218.
here is the snippet of the error message.
Building library - …
lib(): error LNK1218: warning treated as error.

This very same driver links fine on Win2K DDK checked
and free builds. My directories are not write protected or
anything of that sort and I do have a LOT of space on the
drive.

I am pretty sure that my environment settings are correct.

I have tried looking up LNK1218 and there seems to be no documentation
whatsoever anywhere.

If anybody has seen this or has a solution for my problem please let
me know.

I have spent the better half of thelast 4 hours trying to figure
this one out.

Are you building with the -w flag to build to see warnings?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@nai.com
Sent: Friday, September 27, 2002 4:47 PM
To: NT Developers Interest List
Subject: [ntdev] Linker error LNK1218 on XP checked build

Has anybody seen this linker error before.

I am trying to compile my NDIS50 protocol driver.

I end up getting this arcane linker error LNK1218.
here is the snippet of the error message.
Building library - …
lib(): error LNK1218: warning treated as error.

This very same driver links fine on Win2K DDK checked
and free builds. My directories are not write protected or
anything of that sort and I do have a LOT of space on the
drive.

I am pretty sure that my environment settings are correct.

I have tried looking up LNK1218 and there seems to be no documentation
whatsoever anywhere.

If anybody has seen this or has a solution for my problem please let
me know.

I have spent the better half of thelast 4 hours trying to figure
this one out.


You are currently subscribed to ntdev as: xxxxx@tenpennies.com
To unsubscribe send a blank email to %%email.unsub%%

I did not do that. However, I have set the warning levels to WX
to force the error as warnings.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Friday, September 27, 2002 4:54 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Linker error LNK1218 on XP checked build

Are you building with the -w flag to build to see warnings?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@nai.com
Sent: Friday, September 27, 2002 4:47 PM
To: NT Developers Interest List
Subject: [ntdev] Linker error LNK1218 on XP checked build

Has anybody seen this linker error before.

I am trying to compile my NDIS50 protocol driver.

I end up getting this arcane linker error LNK1218.
here is the snippet of the error message.
Building library - …
lib(): error LNK1218: warning treated as error.

This very same driver links fine on Win2K DDK checked
and free builds. My directories are not write protected or
anything of that sort and I do have a LOT of space on the
drive.

I am pretty sure that my environment settings are correct.

I have tried looking up LNK1218 and there seems to be no documentation
whatsoever anywhere.

If anybody has seen this or has a solution for my problem please let
me know.

I have spent the better half of thelast 4 hours trying to figure
this one out.


You are currently subscribed to ntdev as: xxxxx@tenpennies.com
To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%

I would look it up on the latest MSDN for Visual Studio .NET. I can’t find
it under the old MSDN that works with Visual Studio 6. I do know that the
XP DDK requires all compiles to work without errors and all warnings are
treated as errors in the XP DDK.

Real interesting change, but you can get used to it.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, September 27, 2002 7:46 PM
Subject: [ntdev] Linker error LNK1218 on XP checked build

> Has anybody seen this linker error before.
>
> I am trying to compile my NDIS50 protocol driver.
>
> I end up getting this arcane linker error LNK1218.
> here is the snippet of the error message.
> Building library - …
> lib(): error LNK1218: warning treated as error.
>
> This very same driver links fine on Win2K DDK checked
> and free builds. My directories are not write protected or
> anything of that sort and I do have a LOT of space on the
> drive.
>
> I am pretty sure that my environment settings are correct.
>
> I have tried looking up LNK1218 and there seems to be no documentation
> whatsoever anywhere.
>
> If anybody has seen this or has a solution for my problem please let
> me know.
>
> I have spent the better half of thelast 4 hours trying to figure
> this one out.
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%

>>XP DDK requires all compiles to work without errors and all warnings are

>treated as errors in the XP DDK.

Yes.
The compiler defaults to /W3, I have no problems with that.
Just that when the linker throws up an error I would sure like to see
some documentation on that.

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Friday, September 27, 2002 6:13 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

I would look it up on the latest MSDN for Visual Studio .NET. I can’t
find
it under the old MSDN that works with Visual Studio 6. I do know that the
XP DDK requires all compiles to work without errors and all warnings are
treated as errors in the XP DDK.

Real interesting change, but you can get used to it.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, September 27, 2002 7:46 PM
Subject: [ntdev] Linker error LNK1218 on XP checked build

> Has anybody seen this linker error before.
>
> I am trying to compile my NDIS50 protocol driver.
>
> I end up getting this arcane linker error LNK1218.
> here is the snippet of the error message.
> Building library - …
> lib(): error LNK1218: warning treated as error.
>
> This very same driver links fine on Win2K DDK checked
> and free builds. My directories are not write protected or
> anything of that sort and I do have a LOT of space on the
> drive.
>
> I am pretty sure that my environment settings are correct.
>
> I have tried looking up LNK1218 and there seems to be no documentation
> whatsoever anywhere.
>
> If anybody has seen this or has a solution for my problem please let
> me know.
>
> I have spent the better half of thelast 4 hours trying to figure
> this one out.
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%

I do not have the XP DDK installed on my development system at this time,
but I did notice that if I didn’t explicitly set the warning level when
specifying MX, I didn’t see the errors even though I used “build -w”. But,
I’ve been unable to produce a link error that wasn’t related to a compile
error.

I used “set MSC_WARNING_LEVEL=/W3 /WX” to see the errors…but
still…these just seem to be compile errors…setting “LINKER_FLAGS”
environment didn’t seem to produce the warning I was hoping for…

Hmmm…

I would still recommend using “build -w” to make sure you are seeing all
the compile errors. Perhaps one of these is the source of your link error,
and only the linker is using warnings as errors.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@nai.com
Sent: Friday, September 27, 2002 6:47 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

>XP DDK requires all compiles to work without errors and all warnings are
>treated as errors in the XP DDK.

Yes.
The compiler defaults to /W3, I have no problems with that.
Just that when the linker throws up an error I would sure like to see
some documentation on that.

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Friday, September 27, 2002 6:13 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

I would look it up on the latest MSDN for Visual Studio .NET. I can’t
find
it under the old MSDN that works with Visual Studio 6. I do know that the
XP DDK requires all compiles to work without errors and all warnings are
treated as errors in the XP DDK.

Real interesting change, but you can get used to it.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, September 27, 2002 7:46 PM
Subject: [ntdev] Linker error LNK1218 on XP checked build

> Has anybody seen this linker error before.
>
> I am trying to compile my NDIS50 protocol driver.
>
> I end up getting this arcane linker error LNK1218.
> here is the snippet of the error message.
> Building library - …
> lib(): error LNK1218: warning treated as error.
>
> This very same driver links fine on Win2K DDK checked
> and free builds. My directories are not write protected or
> anything of that sort and I do have a LOT of space on the
> drive.
>
> I am pretty sure that my environment settings are correct.
>
> I have tried looking up LNK1218 and there seems to be no documentation
> whatsoever anywhere.
>
> If anybody has seen this or has a solution for my problem please let
> me know.
>
> I have spent the better half of thelast 4 hours trying to figure
> this one out.
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@tenpennies.com
To unsubscribe send a blank email to %%email.unsub%%

Have you examined build*.log file (and also .wrn and .err)? Build filters
some error messages and doesn’t display them on the screen. Log file
contains everything and it could be possible to see what is wrong there.

BTW, LNK1218 isn’t in the April 2002 MSDN (maybe there is newer). There is
1215 and then 1219. Funny docs.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]


From: xxxxx@nai.com[SMTP:xxxxx@nai.com]
Reply To: xxxxx@lists.osr.com
Sent: Saturday, September 28, 2002 3:47 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

>>XP DDK requires all compiles to work without errors and all warnings are
>>treated as errors in the XP DDK.

Yes.
The compiler defaults to /W3, I have no problems with that.
Just that when the linker throws up an error I would sure like to see
some documentation on that.

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Friday, September 27, 2002 6:13 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

I would look it up on the latest MSDN for Visual Studio .NET. I can’t
find
it under the old MSDN that works with Visual Studio 6. I do know that the
XP DDK requires all compiles to work without errors and all warnings are
treated as errors in the XP DDK.

Real interesting change, but you can get used to it.

----- Original Message -----
From:
> To: “NT Developers Interest List”
> Sent: Friday, September 27, 2002 7:46 PM
> Subject: [ntdev] Linker error LNK1218 on XP checked build
>
>
> > Has anybody seen this linker error before.
> >
> > I am trying to compile my NDIS50 protocol driver.
> >
> > I end up getting this arcane linker error LNK1218.
> > here is the snippet of the error message.
> > Building library - …
> > lib(): error LNK1218: warning treated as error.
> >
> > This very same driver links fine on Win2K DDK checked
> > and free builds. My directories are not write protected or
> > anything of that sort and I do have a LOT of space on the
> > drive.
> >
> > I am pretty sure that my environment settings are correct.
> >
> > I have tried looking up LNK1218 and there seems to be no documentation
> > whatsoever anywhere.
> >
> > If anybody has seen this or has a solution for my problem please let
> > me know.
> >
> > I have spent the better half of thelast 4 hours trying to figure
> > this one out.
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> > To unsubscribe send a blank email to %%email.unsub%%
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@nai.com
> To unsubscribe send a blank email to %%email.unsub%%
>
> —
> You are currently subscribed to ntdev as: michal.vodicka@st.com
> To unsubscribe send a blank email to %%email.unsub%%
>

Using the -w option did help.
It was a redefinition linkage error.

-----Original Message-----
From: Shaun Ruffell [mailto:xxxxx@tenpennies.com]
Sent: Friday, September 27, 2002 6:53 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

I do not have the XP DDK installed on my development system at this time,
but I did notice that if I didn’t explicitly set the warning level when
specifying MX, I didn’t see the errors even though I used “build -w”.
But,
I’ve been unable to produce a link error that wasn’t related to a compile
error.

I used “set MSC_WARNING_LEVEL=/W3 /WX” to see the errors…but
still…these just seem to be compile errors…setting “LINKER_FLAGS”
environment didn’t seem to produce the warning I was hoping for…

Hmmm…

I would still recommend using “build -w” to make sure you are seeing all
the compile errors. Perhaps one of these is the source of your link
error,
and only the linker is using warnings as errors.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@nai.com
Sent: Friday, September 27, 2002 6:47 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

>XP DDK requires all compiles to work without errors and all warnings are
>treated as errors in the XP DDK.

Yes.
The compiler defaults to /W3, I have no problems with that.
Just that when the linker throws up an error I would sure like to see
some documentation on that.

-----Original Message-----
From: David J. Craig [mailto:xxxxx@yoshimuni.com]
Sent: Friday, September 27, 2002 6:13 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Linker error LNK1218 on XP checked build

I would look it up on the latest MSDN for Visual Studio .NET. I can’t
find
it under the old MSDN that works with Visual Studio 6. I do know that the
XP DDK requires all compiles to work without errors and all warnings are
treated as errors in the XP DDK.

Real interesting change, but you can get used to it.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, September 27, 2002 7:46 PM
Subject: [ntdev] Linker error LNK1218 on XP checked build

> Has anybody seen this linker error before.
>
> I am trying to compile my NDIS50 protocol driver.
>
> I end up getting this arcane linker error LNK1218.
> here is the snippet of the error message.
> Building library - …
> lib(): error LNK1218: warning treated as error.
>
> This very same driver links fine on Win2K DDK checked
> and free builds. My directories are not write protected or
> anything of that sort and I do have a LOT of space on the
> drive.
>
> I am pretty sure that my environment settings are correct.
>
> I have tried looking up LNK1218 and there seems to be no documentation
> whatsoever anywhere.
>
> If anybody has seen this or has a solution for my problem please let
> me know.
>
> I have spent the better half of thelast 4 hours trying to figure
> this one out.
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@tenpennies.com
To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to %%email.unsub%%