Intel® C++ Compiler
Support and discussions for creating C++ code that runs on platforms based on Intel® processors.
Announcements
The Intel sign-in experience is changing in February to support enhanced security controls. If you sign in, click here for more information.

ipo: warning #11020 on os x.

perceive
Beginner
213 Views
Hello-

I'm getting this warning too when compiling with -fast on os x:

ipo: warning #11020: unresolved _GSS_C_NT_HOSTBASED_SERVICE
Referenced in /usr/lib/libcups.2.dylib

My code compiles and runs cleanly when compiled with -debug.

I'm on os x 10.5.6,

awagner@hesse(ttys001)->icc --version
icc (ICC) 11.0 20090131
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

Any ideas? This doesn't seem to be breaking my code, but I'd still like my code to compile cleanly, or at least have some assurance that this is benign. Auto-vectorization is working quite nicely for us, BTW.

This is similar to an older (partially resolved) thread:

Cheers,
Drew
0 Kudos
2 Replies
Om_S_Intel
Employee
213 Views
Quoting - perceive
Hello-

I'm getting this warning too when compiling with -fast on os x:

ipo: warning #11020: unresolved _GSS_C_NT_HOSTBASED_SERVICE
Referenced in /usr/lib/libcups.2.dylib

My code compiles and runs cleanly when compiled with -debug.

I'm on os x 10.5.6,

awagner@hesse(ttys001)->icc --version
icc (ICC) 11.0 20090131
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

Any ideas? This doesn't seem to be breaking my code, but I'd still like my code to compile cleanly, or at least have some assurance that this is benign. Auto-vectorization is working quite nicely for us, BTW.

This is similar to an older (partially resolved) thread:

Cheers,
Drew

The IPO is an optimzation phase in Intel compiler. The compiler is supposed to translate the code and should not issue undefined symbols warning. You may submit an issue on it to Intel support.

The Intel compiler calls gcc linker to generate the executable. The linker searches the undefined symbols in objects and libraries. If the undefined symbols are not resolved then linker must throw an error. This is not happening in your compilation. It looks good to me.

Om
Quoc-An_L_Intel
Moderator
213 Views
I don't see this problem with the latest compiler update. You might want to try it.

Xcode version 3.1.2

intels-mac-pro:u61236 intel$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.5.6
BuildVersion: 9G55
intels-mac-pro:u61236 intel$ cat vec.cpp
#include

#define N 1000

int main (void)
{
float A, B;

for (int i=0; i < N; i++)
{
A = i;
B = i+1;
}

return 0;

}
intels-mac-pro:u61236 intel$ icpc -V -fast vec.cpp
Intel C++ Compiler Professional for applications running on Intel 64, Version 11.0 Build 20090318 Package ID: m_cproc_p_11.0.064
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

Edison Design Group C/C++ Front End, version 3.10 (Mar 18 2009 18:58:26)
Copyright 1988-2007 Edison Design Group, Inc.

ipo: remark #11001: performing single-file optimizations
ipo: remark #11005: generating object file /tmp/ipo_icpcVm7w3p.o
vec.cpp(9): (col. 2) remark: LOOP WAS VECTORIZED.
@(#)PROGRAM:ld PROJECT:ld64-85.2.1
Library search paths:
/opt/intel/Compiler/11.0/064/lib
/usr/lib/i686-apple-darwin9/4.0.1/
/usr/lib/
/usr/lib/gcc/i686-apple-darwin9/4.0.1/x86_64
/usr/lib/gcc/i686-apple-darwin9/4.0.1/
/usr/lib/i686-apple-darwin9/4.0.1
/usr/lib
/usr/lib
/usr/local/lib
Framework search paths:
/Library/Frameworks/
/System/Library/Frameworks/
intels-mac-pro:u61236 intel$ ./a.out
intels-mac-pro:u61236 intel$

Reply