gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

Coding > Problems building DevKitARM

#23841 - Abscissa - Thu Jul 22, 2004 9:39 pm

I'm trying to build DevKitARM from source, but I'm getting some build errors far into the build. I'm using Cygwin (Had major problems with MSYS/MinGW), and it doesn't seem to let me copy text to the clipboard, so I've taken a screenshot:

http://www.twistedpairgaming.com/download/messedUpDKABuild.GIF

Anyone have any clues about what's going wrong?

#23863 - wintermute - Fri Jul 23, 2004 4:44 am

You're using Cygwin, it's not supported. The *entire* point of windows devkitARM is *not* to use Cygwin.

Building under windows is fraught with dificulty and is fairly pointless given that binaries are available so you don't have to and won't actually gain anything by doing so. The build scripts are mainly there for linux and OS X users.

The preferred method for devkitARM support requests is via the mailing list - while forum posts may get a reply eventually there's no particular guarantee that I'll see it.

#23865 - Abscissa - Fri Jul 23, 2004 5:07 am

wintermute wrote:
You're using Cygwin, it's not supported. The *entire* point of windows devkitARM is *not* to use Cygwin.


Yea, I have the win binaries. The only reason I was trying to get it compiling was because I want to see if I can get the D Frontend (http://home.earthlink.net/~dvdfrdmn/d/) working with it.

I did end up getting DevKitARM compiling under Cygwin ok just a few minutes ago, though (But not the D part).

Quote:
Building under windows is fraught with dificulty


Heheh, no kidding! :)

Quote:
The preferred method for devkitARM support requests is via the mailing list - while forum posts may get a reply eventually there's no particular guarantee that I'll see it.


Ahh, ok.

#23922 - wintermute - Sat Jul 24, 2004 7:11 am

aha, someone with a vailid reason for building from source :)

can you PM me with the build errors you were getting with mingw/msys and the adjustments you needed to make to get it built with Cygwin?

It might be interesting to compare the two environments. I've seen reports of some really bizarre differences - like code compiled with mingw being 2000% faster than the same code compiled with cygwin.

you can get a full build log by running the scripts like this :-

Code:

./build-devkit.sh | tee build.log

#23952 - tepples - Sun Jul 25, 2004 6:37 am

wintermute wrote:
I've seen reports of some really bizarre differences - like code compiled with mingw being 2000% faster than the same code compiled with cygwin.

What exactly was that code doing? If it was doing I/O or multithread work, it might have been Cygwin's stricter POSIX conformity getting in the way.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#23956 - wintermute - Sun Jul 25, 2004 9:47 am

tepples wrote:
wintermute wrote:
I've seen reports of some really bizarre differences - like code compiled with mingw being 2000% faster than the same code compiled with cygwin.

What exactly was that code doing? If it was doing I/O or multithread work, it might have been Cygwin's stricter POSIX conformity getting in the way.


number crunching apparently

http://sourceforge.net/mailarchive/message.php?msg_id=7961071

I/O is terrible with cygwin dependent code - quite a few people who switched to devkitARM/devkitPPC from one of the cygwin based equivalents have been quite shocked.

Linux is faster still - my PIII450 based Debian box can build devkitARM from scratch in around 40 minutes yet the mingw/msys build takes a shade over 3 hours on an 850 Athlon :/

I dread to think how long it takes on Cygwin (or the 25MHz 68030 based system I built my first gcc toolchain on many years ago :P)