Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29297 Discussions

Ifort producing libraries with TEXTREL

One_C_
Beginner
‎09-24-2013 07:39 AM
503 Views

Hi, I have a problem similar to the one reported here: http://software.intel.com/en-us/forums/topic/364080 I am using IFORT 13.1.2 with GCC 4.2.1 to compile my project but two of the .so files get TEXTREL. If I run ldd mylybrary.so and then scanelf -T all of the libraries which my library links to, none of them has TEXTREL so it should be comming from IFORT. I am linking with ifort -shared -fPIC -lifport -lifcoremt -limf flags (among others). Is there a way to get rid of TEXTREL?

Oh, by the way, running scanelf -T on my library returns:

 TYPE   TEXTRELS FILE
scanelf: scanelf_file_textrels(): ELF mylibrary.so has TEXTREL markings but doesnt appear to have any real TEXTREL's !?
ET_DYN  mylibrary.so

0 Kudos

Link Copied

1 Reply
Georg_Z_Intel
Employee
‎09-30-2013 05:06 AM
503 Views
Hello, could you please send me the SO in question, or at least the output of "readelf -a" indicating the TEXTREL entries? Would it be also possible to try first with the latest version (13.1.3). In the recent past we did some improvements in that area. Thank you and best regards, Georg Zitzlsberger
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.