[Mingw-users] Re: __EH_FRAME_BEGIN__

[Sisyphus <kal...@ii...>]

Luke Dunstan wrote:

>
> What is the command line that failed?
>


We have:
dlltool --def Slatec.def --output-exp dll.exp

Followed by (and this is the command that fails):

g++ -o ..\..\blib\arch\auto\PDL\Slatec\Slatec.dll -Wl,--base-file -Wl,dll.base -mdll -s -L"D:\perl58_M\5.8.6\lib\CORE" -L"D:\MinGW\lib" Slatec.o slatec/d1mach.o  slatec/chfcm.o  slatec/chfdv.o  slatec/chfev.o  slatec/chfie.o  slatec/dchfcm.o  slatec/dasum.o  slatec/daxpy.o slatec/dchfdv.o  slatec/dchfev.o  slatec/dchfie.o  slatec/ddot.o slatec/dgeco.o  slatec/dgedi.o  slatec/dgefa.o  slatec/dgesl.o slatec/dp1vlu.o  slatec/dpchbs.o  slatec/dpchce.o  slatec/dpchci.o slatec/dpchcm.o  slatec/dpchcs.o  slatec/dpchdf.o  slatec/dpchfd.o slatec/dpchfe.o  slatec/dpchia.o  slatec/dpchic.o  slatec/dpchid.o slatec/dpchim.o  slatec/dpchkt.o  slatec/dpchsp.o  slatec/dpchst.o slatec/dpchsw.o  slatec/dpcoef.o  slatec/dpoco.o  slatec/dpodi.o slatec/dpofa.o  slatec/dpolft.o  slatec/dscal.o  slatec/dswap.o slatec/ezfft1.o  slatec/ezfftb.o  slatec/ezfftf.o  slatec/ezffti.o slatec/fdump.o  slatec/i1mach.o  slatec/idamax.o  slatec/isamax.o slatec/j4save.o  slatec/pchbs.o  slatec/pchce.o  slatec/pchci.o slatec/pchcm.o  slatec/pchcs.o  slatec/pchdf.o  slatec/pchfd.o slatec/pchfe.o  slatec/pchia.o  slatec/pchic.o  slatec/pchid.o slatec/pchim.o  slatec/pchkt.o  slatec/pchsp.o  slatec/pchst.o slatec/pchsw.o  slatec/pcoef.o  slatec/polfit.o  slatec/pvalue.o slatec/pythag.o  slatec/r1mach.o  slatec/radb2.o  slatec/radb3.o slatec/radb4.o  slatec/radb5.o  slatec/radbg.o  slatec/radf2.o slatec/radf3.o  slatec/radf4.o  slatec/radf5.o  slatec/radfg.o slatec/rfftb.o  slatec/rfftb1.o  slatec/rfftf.o  slatec/rfftf1.o slatec/rs.o  slatec/sasum.o  slatec/saxpy.o  slatec/sdot.o slatec/sgeco.o  slatec/sgedi.o  slatec/sgefa.o  slatec/sgesl.o slatec/snrm2.o  slatec/spoco.o  slatec/spodi.o  slatec/spofa.o slatec/srot.o  slatec/srotg.o  slatec/sscal.o  slatec/ssvdc.o slatec/sswap.o  slatec/tql2.o  slatec/tqlrat.o  slatec/tred1.o slatec/tred2.o  slatec/xerbla.o  slatec/xercnt.o  slatec/xerhlt.o slatec/xermsg.o  slatec/xerprn.o  slatec/xersve.o  slatec/xgetua.o -Wl,--image-base,0x360f0000  D:\perl58_M\5.8.6\lib\CORE\libperl58.a \mingw\lib\libg2c.a \mingw\lib\libm.a D:\MinGW\bin\..\lib\gcc\mingw32\3.4.2\libgcc.a \mingw\lib\libmsvcrt.a \mingw\lib\libmoldname.a \mingw\lib\libkernel32.a \mingw\lib\libuser32.a \mingw\lib\libgdi32.a \mingw\lib\libwinspool.a \mingw\lib\libcomdlg32.a \mingw\lib\libadvapi32.a \mingw\lib\libshell32.a \mingw\lib\libole32.a \mingw\lib\liboleaut32.a \mingw\lib\libnetapi32.a \mingw\lib\libuuid.a \mingw\lib\libws2_32.a \mingw\lib\libmpr.a \mingw\lib\libwinmm.a \mingw\lib\libversion.a \mingw\lib\libodbc32.a dll.exp

That's followed immediately by the output I posted yesterday.

All of those slatec/*.o files mentioned in the command above have been produced by g77. For example, d1mach.o (the first slatec/*.o file mentioned) was built by the following command:

g77.exe -c -o slatec/d1mach.o -O slatec/d1mach.f

And the other slatec/*.o files were built in essentially the same way - ie same command, just different filenames.

Cheers,
Rob