Software Archive
Read-only legacy content
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.
17060 Discussions

linking errors during ABAQUS analysis

Intel_C_Intel
Employee
‎05-01-2001 04:57 AM
520 Views
In ABAQUS analysis, I hope to analysis creep problem.

I have some errors during ABAQUS analysis with linking Fortran programmed subroutine.

.log file, which is generated during ABAQUS analysis, is shown below

.......
.......

Compiling... surface_mount.for
surface_mount.for
Linking... IMPLICIT
Microsoft Incremental Linker Version 6.00.8168
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.

surface_mount.obj : error LNK2005: _CREEP@104 already defined in surface.obj
surface_mount.obj : error LNK2005: _CREEP already defined in surface.obj
surface_mount.exe : fatal error LNK1169: one or more multiply defined symbols found
Error while linking IMPLICIT. This is sometimes caused
by a mismatch in subroutine arguments. Undefined externals
may occur if the C library is not the first library listed
in the LIB system variable
Monday April 30 19101 15:30:10
ABAQUS JOB surface_mount COMPLETED

I have tried to resolve above errors with reference to your message board and FAQ, but I can't fix them.
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎05-01-2001 02:01 PM
520 Views
This error means that you have two different object modules defining the routine CREEP. Please check your code and make sure that there is only one definition of this routine.

Steve
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.