Forum Jump

Select Group :
Select Forum :
Sorted By :
Sort Order :
From The :
 
Thread Tools  Search this thread 
Groundsel
Total Points:
260
Status Points:
0
Green Belt
November 19, 2008 12:35 PM PST
Locally Defined Symbol Imported

I imagine this has come up before in various guises.  I would like to get rid of WARNING messages by means other than simply switching them off (too much like shooting the messenger).  Our application features a number of dll's some of which make use of a COMMON block within a module.  (This was to get around the problem of exporting module EQUIVALENCE variables - we export a COMMON block in stead.)  On the other hand the routines within the dll also make use of the exported COMMON block and hence the warning messages "Locally defined symbol xxxxx imported in yyyyy."

Does anyone have a way of getting around this and avoiding the warnings.  I have to add that no harm seems to be done so far as I have been able to tell.

 

Tom

Steve Lionel (Intel)
Total Points:
112,121
Status Points:
112,121
Black Belt
November 20, 2008 3:43 AM PST
Rate
 
#1

The warning is harmless.  The only way to get rid of it is to add it to the list of messages to "ignore" in the linker properties.  You get this when a DLLIMPORT is seen for a symbol defined in the linked image.  That will happen if you DLLEXPORT something in a module and then USE that module.
Groundsel
Total Points:
260
Status Points:
0
Green Belt
November 24, 2008 1:18 PM PST
Rate
 
#2 Reply to #1

Thanks, Steve,

That is what I expected you would say.

Tom


Intel Software Network Forums Statistics

8290 users have contributed to 31236 threads and 99111 posts to date.
In the past 24 hours, we have 7 new thread(s) 20 new posts(s), and 30 new user(s).

In the past 3 days, the most popular thread for everyone has been comparison cilk++, openmp, pthreads first results The most posts were made to comparison cilk++, openmp, pthreads first results The post with the most views is Very amusing...  Escalated as

Please welcome our newest member zq.x