bug#30127: Re[2]: bug#30127: ICC: 'entry point must be defined' error for shared builds on Windows

2022-02-08 Thread Mike Frysinger
closing this issue out. the original report has been settled, we've merged support for ignoring -nologo, but the -xilib suggestion looks like it needs more work. feel free to post a patch to automake-patc...@gnu.org if you have something you think we can merge. -mike signature.asc Description:

bug#30127: Re[2]: bug#30127: ICC: 'entry point must be defined' error for shared builds on Windows

2018-01-23 Thread Peyton, Jonathan L
I think the –xilib option is invalid when using: $ xilink –xilib … This just gives me an “unrecognized option '/xilib'; ignored” warning, but if I use $ xilink –lib … Then it calls xilib similar to how $ link.exe –lib … calls lib.exe Or in short: $ xilink.exe –lib = xilib.exe $ link.exe –lib =

bug#30127: Re[2]: bug#30127: ICC: 'entry point must be defined' error for shared builds on Windows

2018-01-23 Thread Mathieu Lirzin
sav...@ukr.net writes: > In case you're interested, there is a patch to 'lib/ar-lib', which I use for > libiconv builds using Windows ICC: > === > diff --git a/build-aux/ar-lib b/build-aux/ar-lib > index 463b9ec..3cfddbc 100644 > ---

bug#30127: ICC: 'entry point must be defined' error for shared builds on Windows

2018-01-17 Thread Mathieu Lirzin
Hello, sav...@ukr.net writes: > For libiconv builds using Windows ICC got error: > === > builddir="`pwd`"; cd libcharset && make all && make install-lib > libdir="$builddir/lib" includedir="$builddir/lib" > make[1]: Entering directory

bug#30127: ICC: 'entry point must be defined' error for shared builds on Windows

2018-01-15 Thread sav_ix
Hello everyone, For libiconv builds using Windows ICC got error: === builddir="`pwd`"; cd libcharset && make all && make install-lib libdir="$builddir/lib" includedir="$builddir/lib" make[1]: Entering directory