sorry. the config.log was supposed to be in a Code tag. I will repost if the information needed is not seen.
the error at the end is 77
This is not how we work, and not usefull at all. You’ll understand; we need
the error log, yeah, but the really meaningfull error is the first one,
that comes with some describing text, etc… We do not carry an error table
her and there, mainly because computers could translate it automatically, $
explainconfigureerror 77 
and so programmers do it.by design. Opaque
errors like that, from experience, usually means some issue with the
compiler, IN GENERAL, say it is aliased to a command that can’t even
compile, say the platform environment flag is totally weird, … think
about why it’s not in an standard behaviour. Still, first error marks the
status, as any further error could be derived from it & hence fake or ghost
(programmers should start to think about handling that ;-)). If you still
consider an standard or valid compiler setting, seems like canadian cross
compiling, from one system to another with a wrong arch flag, we usually
can parse an actual screen log of the issued command with a background
about the purpose and the switches made to the defaults.
P.S.: I got this one mail as another thread, but i remember having a
extremely long configure output days ago posted. Remember, firsts error
mark the difference.
El 10/06/2014 13:44, “Jimothey” escribi?:> sorry. the config.log was supposed to be in a Code tag. I will repost if
the information needed is not seen.
the error at the end is 77
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
My apologies. I’m completely new to this, so don’t know what I’m looking for.
I have uploaded thecomplete config.log here (https://www.dropbox.com/s/rcnrz4gw504r62l/config.log).
Would it be worth uploading the configure script aswell?
Please, if there is anything else you require, I will be more than happy to supply it.
It looks like something added “-” to the configure flags. The best way to
track it down is to add:
set -x
to the top of the configure script, and then log the complete output.On Wed, Jun 11, 2014 at 2:18 PM, Jimothey wrote:
My apologies. [image: Smile] I’m completely new to this, so don’t know
what I’m looking for.
I have uploaded thecomplete config.log here
https://www.dropbox.com/s/rcnrz4gw504r62l/config.log.
Would it be worth uploading the configure script aswell?Please, if there is anything else you require, I will be more than happy
to supply it. [image: Smile]
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Thank you very much for your reply.
I added ‘set -x’ to the beginning of the configure script (before the #!)
I have uploaded the config.log for your perusal
I have no idea why you’re getting that stray ‘-’ in the compiler flags,
sorry. I’m guessing some quirk of your cygwin compile environment.On Mon, Jun 16, 2014 at 1:49 PM, Jimothey wrote:
Thank you very much for your reply.
I added ‘set -x’ to the beginning of the configure script (before the #!)
I have uploaded the config.log for your perusal
https://www.dropbox.com/s/rcnrz4gw504r62l/config.log
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org