- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using SCons to build a project with ICC on Windows, and I get a lot of xilink messages in the console that look like this:
xilink: executing 'link' Creating library path\to\file\file.lib and object path\to\file\file.exp
I believe these messages are output to stderr and are really polluting my console. I found no ICC option to suppress them. What's the proper way to do this, apart from the brute-force and sub-optimal forwarding of stderr output to NUL?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
lliyan, the message "Creating library path\to\file\file.lib and object path\to\file\file.exp" comes from LINK. I agree, although the message “"xilink: executing 'link'”” comes from xilink there’s no option available to disable it. BTW, there’s an issue filed on Xilink on a related issue sometime back to allow options to suppress messages. In general, it does honor related options supported by LINK though. Anyways, I’ll pass on the feedback to the developers and if need be file a feature request to disable such messages without a diagnostic number associated with it, thanks.
_Kittur
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lliyan,
You can disable diagnostics from xilink (which is the Intel pre-linker) using the diag-disable option. Refer to the table in the article on how to disable at: https://software.intel.com/en-us/node/512838 You can add the disable (/Qdiag-disable:<diag-number> to the linker command Line > Additional Options field as well if running from VS as well)
_Kittur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, you can disable the dianostics from a complete phase as well (and not just a single diagnostic) as noted in the table (article link noted earlier).
_Kittur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick reply and the link, much appreciated! But I'm having trouble disabling this specific xilink message I'm referring to above. What option exactly should I use?
Actually, playing around with the /Qdiag-file option, it seems that
xilink: executing 'link'
is a different message from
Creating library ...
And when I add /Qdiag-file:output.txt only the second kind of messages are dumped to the file. xilink: executing 'link' is still output on the console.... Any idea how to get rid of both?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI lliyan,
That's a good question. Unfortunately that error message is coming from MS Link and Intel compiler has no control on it at all. And I can't seem to find anyway you can control that output as well. May be, a good idea to give your feedback to MS to allow some option for disabling the same :-(
_Kittur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Kittur Ganesh (Intel) wrote:
Unfortunately that error message is coming from MS Link and Intel compiler has no control on it at all.
Which message are you referring to? The "xilink: executing 'link'" message at least should come from ICC. Any way to disable that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
lliyan, the message "Creating library path\to\file\file.lib and object path\to\file\file.exp" comes from LINK. I agree, although the message “"xilink: executing 'link'”” comes from xilink there’s no option available to disable it. BTW, there’s an issue filed on Xilink on a related issue sometime back to allow options to suppress messages. In general, it does honor related options supported by LINK though. Anyways, I’ll pass on the feedback to the developers and if need be file a feature request to disable such messages without a diagnostic number associated with it, thanks.
_Kittur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Kittur! Looking forward to having such an option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Of course, thanks for bringing this up and I'll file a feature request with the developers and keep you updated accordingly.
_Kittur

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page