http://buildsys.fedoraproject.org/logs/fedora-5-epel/1672-mingw32-pango-1.23...
Why on earth does it decide to start naming the stub files *.lib?
Rich.
Richard W.M. Jones wrote:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1672-mingw32-pango-1.23...
Why on earth does it decide to start naming the stub files *.lib?
It looks like these are not import libs at all, but symlinks to the DLL (which MinGW can link directly). This is a very strange convention. No idea why it isn't using standard import libs.
Kevin Kofler
On Wed, Mar 11, 2009 at 12:38:34AM +0100, Kevin Kofler wrote:
Richard W.M. Jones wrote:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1672-mingw32-pango-1.23...
Why on earth does it decide to start naming the stub files *.lib?
It looks like these are not import libs at all, but symlinks to the DLL (which MinGW can link directly). This is a very strange convention. No idea why it isn't using standard import libs.
Even stranger. I wonder why it decided to do that on EL-5, but not on any of the other platforms we build on?
BTW I had to disable the static subpackage (just for EL-5) because rerunning autoreconf failed. Here was that earlier error:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1671-mingw32-pango-1.23...
Rich.
Op woensdag 11-03-2009 om 09:00 uur [tijdzone +0000], schreef Richard W.M. Jones:
On Wed, Mar 11, 2009 at 12:38:34AM +0100, Kevin Kofler wrote:
Richard W.M. Jones wrote:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1672-mingw32-pango-1.23...
Why on earth does it decide to start naming the stub files *.lib?
It looks like these are not import libs at all, but symlinks to the DLL (which MinGW can link directly). This is a very strange convention. No idea why it isn't using standard import libs.
Even stranger. I wonder why it decided to do that on EL-5, but not on any of the other platforms we build on?
BTW I had to disable the static subpackage (just for EL-5) because rerunning autoreconf failed. Here was that earlier error:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1671-mingw32-pango-1.23...
Rich.
Hi,
I guess the 'autoreconf' call needs to be changed to 'autoreconf --force --install'
Regards,
Erik van Pienbroek
On Wed, Mar 11, 2009 at 10:33:44AM +0100, Erik van Pienbroek wrote:
Op woensdag 11-03-2009 om 09:00 uur [tijdzone +0000], schreef Richard W.M. Jones:
On Wed, Mar 11, 2009 at 12:38:34AM +0100, Kevin Kofler wrote:
Richard W.M. Jones wrote:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1672-mingw32-pango-1.23...
Why on earth does it decide to start naming the stub files *.lib?
It looks like these are not import libs at all, but symlinks to the DLL (which MinGW can link directly). This is a very strange convention. No idea why it isn't using standard import libs.
Even stranger. I wonder why it decided to do that on EL-5, but not on any of the other platforms we build on?
BTW I had to disable the static subpackage (just for EL-5) because rerunning autoreconf failed. Here was that earlier error:
http://buildsys.fedoraproject.org/logs/fedora-5-epel/1671-mingw32-pango-1.23...
Rich.
Hi,
I guess the 'autoreconf' call needs to be changed to 'autoreconf --force --install'
Thanks Erik, that actually solved both problems.
Rich.