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.
29280 Discussions

error

sandal__bilel
Beginner
‎03-07-2019 07:09 AM
1,035 Views

plz can anyone tel  me ho to solve the error in linking abaqus to fortran 

ifort: command line warning #10161: unrecognized source type 'user'; object file assumed

fpp: fatal: can't fopen file: subroutine.for
Abaqus Error: Problem during compilation -

plz answer me 

0 Kudos

Link Copied

2 Replies
Steve_Lionel
Honored Contributor III
‎03-07-2019 03:58 PM
1,035 Views

You're asking a Fortran compiler to compile something with a .user file type. It doesn't understand that. For more help you'll need to ask Abaqus support.

0 Kudos
Copy link
Greg_T_
Valued Contributor I
‎03-12-2019 08:59 AM
1,035 Views

Hi Bilel,

Do you have access to the SIMULIA knowledge base web site?  I believe the URL is: https://www.3ds.com/support/knowledge-base/  

The search on topic key words works pretty well to get more specific Abaqus information, and I've found useful information in the Abaqus knowledge base.

 

Perhaps one of these other Intel Fortran forum articles might help diagnose the problem with linking the user subroutine to Abaqus:

https://software.intel.com/comment/1932230

https://software.intel.com/comment/1929855

Regards, Greg

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.