Cygwin build issue

SDL Development
1

Tried to build SDL with Cygwin today and hit build problems:

SDL was from CVS, and Cygwin was a fresh install (whatever is considered
stable, not development, on the cygwin mirrors).

Building SDL was a matter of “./autogen.sh ; ./configure ; make” …
looks like it died at the linker stage:

Creating library file: .libs/libSDL.dll.a
/usr/lib/gcc-lib/i686-pc-mingw32/3.3.1/…/…/…/…/i686-pc-mingw32/bin/ld: hermes/.libs/libhermes.a(mmxp2_32.o): bad reloc address 0x87 in section `.text’
collect2: ld returned 1 exit status

Any cygwin gurus out there?

Thanks,
–ryan.

2

This is the nasm problem that has been discussed a few times.

I think there is an older version of nasm that works, but never tried it.
I think there is an SDL Windows FAQ out there somewhere that gives a
link to this.

The quick solution: ./configure --disable-nasm

~ Philip D.S. Thoren

Ryan C. Gordon wrote:>Tried to build SDL with Cygwin today and hit build problems:

SDL was from CVS, and Cygwin was a fresh install (whatever is considered
stable, not development, on the cygwin mirrors).

Building SDL was a matter of “./autogen.sh ; ./configure ; make” …
looks like it died at the linker stage:

Creating library file: .libs/libSDL.dll.a
/usr/lib/gcc-lib/i686-pc-mingw32/3.3.1/…/…/…/…/i686-pc-mingw32/bin/ld: hermes/.libs/libhermes.a(mmxp2_32.o): bad reloc address 0x87 in section `.text’
collect2: ld returned 1 exit status

Any cygwin gurus out there?

Thanks,
–ryan.

SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

E3-I: This message has been scanned for viruses and dangerous content by UML’s antivirus scanning services.

–
:vsplit vimrulez.txt i vimrulez :w :q

3

The quick solution: ./configure --disable-nasm

Bleh. We should really check the NASM version in the configure script
and explicitly disable it with a warning, then.

Thanks for the speedy answer!

–ryan.

4

Ryan C. Gordon wrote:

The quick solution: ./configure --disable-nasm

Bleh. We should really check the NASM version in the configure script
and explicitly disable it with a warning, then.

It’s not done because it’s not an nasm bug but a binutils bug, and
disabling nasm is just a workaround.

The end of the previous thread with relevant info is here :
http://www.libsdl.org/pipermail/sdl/2003-October/057523.html

Stephane

5
You might also run into some other problems (since, for most purposes, Cygwin and MinGW32 are nearly the same). Heres the link to my previous post: http://www.libsdl.org/pipermail/sdl/2003-December/058364.html
  • Silicon> ----- Original Message -----

From: stephane.marchesin@wanadoo.fr (Stephane Marchesin)
To:
Sent: Friday, January 02, 2004 6:57 PM
Subject: Re: [SDL] Cygwin build issue…

Ryan C. Gordon wrote:

The quick solution: ./configure --disable-nasm

Bleh. We should really check the NASM version in the configure script
and explicitly disable it with a warning, then.

It’s not done because it’s not an nasm bug but a binutils bug, and
disabling nasm is just a workaround.

The end of the previous thread with relevant info is here :
http://www.libsdl.org/pipermail/sdl/2003-October/057523.html

Stephane

SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.552 / Virus Database: 344 - Release Date: 12/15/2003