The OpenSees Community

As for error:
libm.lib(libm_error.obj) : error LNK2019: unresolved external symbol _errno referenced in function ___libm_error_support

My solution is to add the file "VC2005errno.cpp" into the project failed.
The file "VC2005errno.cpp" locates in OpenSees/Win32.

Great solution!
Thanks a lot!

I have a deeper understanding of the library files "LIBIFCORE.lib" and "LIBIFCOREMT.lib".
I guess they are the calculation module for OpenSees and are written in Fortran.
In fact they should be generated by the same codes (IVF, Intel Visual Fortran) with different project setting. "LIBIFCOREMT.lib" is the multithread library.

If the C++ project is set to use multithread libraries, then the Fortran project must also be set for that.
I checked the OpenSees project setting (propertes-->C/C++-->code generation-->Runtime Library) is Multi-threaded Debug (/MTd), thus the LIBIFCOREMT.lib should be called.
To learn more about the Runtime Library options in visual studio, see https://msdn.microsoft.com/en-us/library/2kzt1wy3.aspx.

Thanks Dr. Frank McKenna.
I saw this solutions two days ago, and then I tried but failed.
Today I tried this method once and succeed.
This error
libifcore.lib(for_init.obj) : error LNK2019: unresolved external symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ
is caused by the library file LIBIFCORE.lib and LIBIFCOREMT.lib.

symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ should exist in LIBIFCOREMT.lib rather than the LIBIFCORE.lib in my programming environment.

Now I summarize my solution once again as follows (based on update the source code via tortoiseSVN):
1. go to the directory: ...\OpenSees\Win32\lib, then you could find two files named as "LIBIFCORE.lib" and "LIBIFCOREMT.lib"
2. delete the file "LIBIFCORE.lib"
3. rename "LIBIFCOREMT.lib" as "LIBIFCORE.lib"
Succeed!
wish my experience could be helpful for you.

Basic description:
OS: win7
SDK: vs 2012
ActiveTcl: 8.5.16.0 (32bit)
tortoiseSVN (repository url) svn://opensees.berkeley.edu/usr/local/svn/OpenSees

1. empty the file Win32, then update to revision: rev 5855, update depth: working copy (make depth sticky: checked)
2. open the solution "OpenSees.sln" in vs 2012
3. all the 27 projects are invalid, then delete and add all the 27 projects by "*.vcproj" to update the project to "*.vcxproj" in vs2012
4. build the 27 project one by one, add the lost lib, include files and some lost source files to the projects to solve most of the errors.
5. Finally, only one type of LNK2019 error could not be solved when build the OpenSees, OpenSeesTK, quickmain

Problem:
libifcore.lib(for_init.obj) : error LNK2019: unresolved external symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ

The libifcore.lib is loaded via the SVN software.

What I could do to solve the aforementioned problem?

output log:

1>------ Build started: Project: damage, Configuration: Debug Win32 ------
1>Build started 1/29/2015 12:45:57 PM.
1>InitializeBuildStatus:
1> Creating ".\..\..\obj\damage\debug\damage.unsuccessfulbuild" because "AlwaysCreate" was specified.
1>ClCompile:
1> All outputs are up-to-date.
1>Lib:
1> All outputs are up-to-date.
1> damage.vcxproj -> D:\Research business\Programms\OpenSees\Win32\proj\damage\.\..\..\lib\debug\damage.lib
1>FinalizeBuildStatus:
1> Deleting file ".\..\..\obj\damage\debug\damage.unsuccessfulbuild".
1> Touching ".\..\..\obj\damage\debug\damage.lastbuildstate".
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:00.60
2>------ Build started: Project: openSees, Configuration: Debug Win32 ------
2>Build started 1/29/2015 12:46:00 PM.
2>InitializeBuildStatus:
2> Touching ".\..\..\obj\openSees\debug\openSees.unsuccessfulbuild".
2>ClCompile:
2> All outputs are up-to-date.
3>------ Build started: Project: openSeesTk, Configuration: Debug Win32 ------
4>------ Build started: Project: optimization, Configuration: Debug Win32 ------
5>------ Build started: Project: quickMain, Configuration: Debug Win32 ------
2>LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/FORCE' specification
2>tclAppInit.obj : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/OPT:LBR' specification
3>Build started 1/29/2015 12:46:02 PM.
4>Build started 1/29/2015 12:46:02 PM.
5>Build started 1/29/2015 12:46:02 PM.
4>InitializeBuildStatus:
3>InitializeBuildStatus:
3> Touching ".\..\..\obj\openSeesTk\debug\openSeesTk.unsuccessfulbuild".
4> Creating "Debug\optimization.unsuccessfulbuild" because "AlwaysCreate" was specified.
5>InitializeBuildStatus:
5> Touching ".\..\..\obj\quickMain\debug\quickMain.unsuccessfulbuild".
4>ClCompile:
4> All outputs are up-to-date.
3>ClCompile:
3> All outputs are up-to-date.
5>ClCompile:
5> All outputs are up-to-date.
4>Lib:
4> All outputs are up-to-date.
4> optimization.vcxproj -> D:\Research business\Programms\OpenSees\Win32\proj\optimization\.\..\..\lib\debug\optimization.lib
4>FinalizeBuildStatus:
4> Deleting file "Debug\optimization.unsuccessfulbuild".
4> Touching "Debug\optimization.lastbuildstate".
4>
4>Build succeeded.
4>
4>Time Elapsed 00:00:00.66
3>LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/FORCE' specification
3>tkMain.obj : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/OPT:LBR' specification
5>libifcore.lib(for_init.obj) : error LNK2019: unresolved external symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ
5>.\..\..\bin/quickMain.exe : fatal error LNK1120: 1 unresolved externals
5>
5>Build FAILED.
5>
5>Time Elapsed 00:00:08.86
3> Creating library .\..\..\bin\openSeesTk.lib and object .\..\..\bin\openSeesTk.exp
2> Creating library .\..\..\bin\openSees.lib and object .\..\..\bin\openSees.exp
3>libifcore.lib(for_init.obj) : error LNK2019: unresolved external symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ
3>.\..\..\bin/openSeesTk.exe : fatal error LNK1120: 1 unresolved externals
2>libifcore.lib(for_init.obj) : error LNK2019: unresolved external symbol __pxcptinfoptrs referenced in function _GETEXCEPTIONPTRSQQ
2>.\..\..\bin/OpenSees.exe : fatal error LNK1120: 1 unresolved externals
3>
3>Build FAILED.
3>
3>Time Elapsed 00:00:20.99
2>
2>Build FAILED.
2>
2>Time Elapsed 00:00:22.42
========== Build: 2 succeeded, 3 failed, 22 up-to-date, 0 skipped ==========

Thanks for your advice, fmk.
I have written email to the developer Jon Mohle last Friday.
I will write to Prof. Kunnath directly this time.

The explanation about the reinforcing steel material is shown as follows:
http://opensees.berkeley.edu/wiki/index ... l_Material
Where in Figure 3, the modified formula from Gomes and Appleton(1997) is given.
Who can give the detailed explanation about the modification of the Gomes and Appleton model? I want to learn how the modified formula is obtained.

Best regards

In OpenSees, can force-based element(forces are the variables, the equations are based on flexibility matrix ) adopt explicit material model (to describe the stress-strain relationship, strain is variable, stress is the function of strain)?
For example, define one material using steel02, then define one element using "nonlinearbeamcolumn". The script are shown as follows:

##model builder
model BasicBuilder -ndm 2 -ndf 3;

##node
node 1 0.0 0.0;
node 2 100.0 0.0;

## Mass
mass 3 1.0 0.0 0.0;

#Boundary Conditions
fix 1 1 1 1;
fix 2 0 1 1;

## Materials
#uniaxialMaterial Steel02 $matTag $Fy $E $b $R0 $cR1 $cR2 <$a1 $a2 $a3 $a4 $sigInit>
uniaxialMaterial Steel02 1 40.2 29800.0 0.003 20 0.925 0.15 0.0005 0.01 0.0005 0.01;

# reinforcing steel Material
#uniaxialMaterial ReinforcingSteel 1 68.2 102.3 29007 870.2 0.00235 0.0415 -GABuck 11 1.0 0.4 0.5

## Pipe Section (4" diameter, ?" wall thickness)
section Fiber 1 {
patch circ 1 20 4 0.0 0.0 1.5 2.0 0.0 360.0;
}

## Transformation
geomTransf Corotational 1;

## Define Model
#element nonlinearBeamColumn $eleTag $iNode $jNode $numIntgrPts $secTag $transfTag
element nonlinearBeamColumn 1 1 2 3 1 1 ;# Brace

## Recorder
recorder Node -file Rst/LoadDisp.out -time -node 3 -dof 1 disp;

## Apply the nodal Load
pattern Plain 1 Linear { load 2 1.0 0.0 0.0; }

## Static Analysis parameters-force based element
constraints Plain;
numberer RCM;
system UmfPack;
test EnergyIncr 1.0e-8 300 0;
algorithm KrylovNewton;

set peaks [ list 0.25 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 ];
for {set i 1 } { $i <= 9 } {incr i } {
set dU [expr -1.0*pow((-1.0),$i)*[lindex $peaks [expr $i-1] ]/50.0 ];
integrator DisplacementControl 2 1 $dU 1 $dU $dU;
analysis Static;
analyze 50;
}

analysis Static;
analyze 50;

puts "Analysis Completed!"

wipe all;

I found this material could consider the nonlinear buckling, so I would like to try this material.

Not yet. Thanks for your reply. I will contact the programmer of this code. I will add the answer of my question after I get reply.

Is there somebody who knows how to apply the uniaxial material steel03 in the material library, in order to simulate the behavior of reinforced steel bar in presence of buckling?

There is one uniaxial material steel03 in the OpenSees, however there is no introduction about how to use this material.
By browsing the OpenSees API (http://opensees.berkeley.edu/OpenSees/a ... eel03.html), I learnt how to define the parameters in the command line( initialize parameters of the API) while using material steel03 in absence of buckling.
But I don't know how to define the values of the parameters in the command line in order to simulate the steel bar in presence of buckling. In other word, I don't know the meaning of the parameters a1, a2, a3, a4 in the material steel03 API, nor understand the relationship with buckling.

Look forwards your kind reply and thanks a lot!

Zhihao

Hi,
I built one new material.dll and attached the solution to OpenSees.exe to debug. However the breakpoint in my solution cannot be hit.
I developed one new material for OpenSees and succeed in generating it as dll (for example named it as myMaterial.dll). Also the OpenSees can load myMaterial.dll file by testing in test.tcl script.
However, I found the material doesn't work properly. So I want to debug my dll solution (myMaterial.sln) in vs2010.
I put opensee.exe, the myMaterial.dll and the test.tcl in one directory and set the directory in the work directory.
After my solution was attached to (attached to: automatic, local machine) the progress OpenSees.exe, I run the test.tcl in the OpenSees prompt, but the breakpoint could not be hit.

Then I carried out the following options: go to the menu Debug->window->module, I found in the module window that the myMaterial.dll was not loaded.
I guessed the OpenSees.exe load the myMaterial.dll when the openSees.exe run the command related to the myMaterial. Thus at the beginning when the solution myMaterial was attached to OpenSees.exe, the myMaterial.dll was not loaded.

In order to debug the myMaterial.dll, I need to hit the breakpoint in the myMaterial solution. Do you have some solutions to hit the breakpoint in the material.dll solution?

Zhihao

Hi, Alberto
I developed one new material for OpenSees and succeed in generating it as dll (for example named it as myMaterial.dll). Also the OpenSees can load myMaterial.dll file by testing in test.tcl script.
However, I found the material doesn't work properly. So I want to debug my dll solution (myMaterial.sln) in vs2010.
I put opensee.exe, the myMaterial.dll and the test.tcl in one directory and set the directory in the work directory.
After my solution was attached to the progress OpenSees.exe, I run the test.tcl in the OpenSees prompt, but the breakpoint could not be hit.

Then I carried out the following options: go to the menu Debug->window->module, I found in the module window that the myMaterial.dll was not loaded.
Do you have some solution to hit the breakpoint in the material.dll solution?

Zhihao