- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorin:
Yes, a few functions which may be linked by ifc are taken from libraries supplied by your system. This would produce your failure, if your system has only x86-64 versions of those libraries. You may have to figure out which libraries those are, and keep versions e.g. from 32-bit SuSE in a directory against which ifc will link. In the past, I have seen ifc builds require libc.a, libg2c.a, or libgcc.a, or specific .o files from those libraries. Supplying additional diagnostic options to ifc for the link step should help you to determine which libraries are failing, e.g.
ifc -#
Yes, a few functions which may be linked by ifc are taken from libraries supplied by your system. This would produce your failure, if your system has only x86-64 versions of those libraries. You may have to figure out which libraries those are, and keep versions e.g. from 32-bit SuSE in a directory against which ifc will link. In the past, I have seen ifc builds require libc.a, libg2c.a, or libgcc.a, or specific .o files from those libraries. Supplying additional diagnostic options to ifc for the link step should help you to determine which libraries are failing, e.g.
ifc -#
Link Copied
0 Replies

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