FLTK make include with MinGW help

[Shingetsu Kurai]

Hello all! I'm trying to install FLTK as a static library (after the headaches win32 API gave me I see RAD as a very good thing).
I got FLTK v2.0 alpha r8800 and I am trying to build it using a basic 'make install'

This is the output:

...>make install
makefile:28: makeinclude: No such file or directory
if test -f config.status; then \
./config.status --recheck; \
./config.status; \
else \
./configure; \
fi
checking or gcc... gcc
checking for C compiler default output file name..
configure: error: C compiler cannot create executables
See 'config.log' for more details.
make: *** [makeinclude] Error 77

I am not new to programming, but I admit this is my first time doing manual compiling (I usually use code::blocks that auto-configures MinGW)

I am quite stumped, as Google stated Error 77 to be the absence of a compiler (which I have, and the EV PATH included)

Please help with this compilation (maybe also give me a way to have it built in a custom location)

[tabstop]

Does config.log contain more details?

[Shingetsu Kurai]

Does config.log contain more details?

Just a long description of what it's doing. Here it is, in case it can help.

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.61.  Invocation command line was

  $ ./configure 

## --------- ##
## Platform. ##
## --------- ##

hostname = Shingetsu
uname -m = i686
uname -r = 1.0.17(0.48/3/2)
uname -s = MINGW32_NT-6.1
uname -v = 2011-04-24 23:39

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /c/GTKmm/bin
PATH: /c/Program Files (x86)/GtkSharp/2.12/bin
PATH: /c/Program Files (x86)/NVIDIA Corporation/PhysX/Common
PATH: /c/Windows/system32
PATH: /c/Windows
PATH: /c/Windows/System32/Wbem
PATH: /c/Windows/System32/WindowsPowerShell/v1.0/
PATH: /c/Program Files/WIDCOMM/Bluetooth Software/
PATH: /c/Program Files/WIDCOMM/Bluetooth Software/syswow64
PATH: /c/Program Files (x86)/ATI Technologies/ATI.ACE/Core-Static
PATH: /c/Program Files (x86)/Common Files/Roxio Shared/10.0/DLLShared/
PATH: /c/Program Files (x86)/Common Files/Roxio Shared/DLLShared/
PATH: /c/Program Files (x86)/QuickTime/QTSystem/
PATH: /c/FPC/2.4.2/bin/i386-Win32
PATH: /mingw/bin
PATH: /usr/bin
PATH: /c/GTK/bin
PATH: /c/Program Files (x86)/GtkSharp/2.12/bin
PATH: /c/QtSDK/QtSources/4.7.3/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2046: checking for gcc
configure:2062: found /c/FPC/2.4.2/bin/i386-Win32/gcc
configure:2073: result: gcc
configure:2311: checking for C compiler version
configure:2318: gcc --version >&5
configure:2321: $? = 0
configure:2328: gcc -v >&5
configure:2331: $? = 0
configure:2338: gcc -V >&5
configure:2341: $? = 1
configure:2364: checking for C compiler default output file name
configure:2391: gcc    conftest.c  >&5
configure:2394: $? = 1
configure:2432: result: 
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:2439: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_prog_ac_ct_CC=gcc

## ----------------- ##
## Output variables. ##
## ----------------- ##

ac_ct_CC='gcc'
ac_ct_CXX=''
AR=''
bindir='${exec_prefix}/bin'
build_alias=''
BUILDTARGETS='programs'
CAT1EXT=''
CAT3EXT=''
CC='gcc'
CFLAGS=''
CPP=''
CPPFLAGS=''
CXX=''
CXXFLAGS=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
DEFS=''
docdir='${datarootdir}/doc/${PACKAGE}'
DSOCOMMAND='echo'
DSOLINK=''
DSOPREFIX=''
DSOSUFFIX=''
DSOSYMLINK=''
DSOTARGET=''
dvidir='${docdir}'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
exec_prefix='NONE'
EXEEXT=''
FL_API_VERSION='2.0'
FL_MAJOR_VERSION='2'
FL_MINOR_VERSION='0'
FL_PATCH_VERSION='0'
FL_RELEASE_VERSION='a0'
FLUID='fluid2'
FTCONFIG=''
GLDEMOS='gldemos'
GLLIB=''
GREP=''
GROFF=''
HLINKS=''
host_alias=''
htmldir='${docdir}'
HTMLDOC=''
IMAGELIBS=''
includedir='${prefix}/include'
infodir='${datarootdir}/info'
INSTALLTARGETS='install_programs'
LDFLAGS=''
LIBCOMMAND=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
LIBOBJS=''
LIBPREFIX='lib'
LIBS=''
LIBSUFFIX='.a'
LIBTARGET='static'
LINKFLTK='-lfltk2'
LINKFLTKGL='-lfltk2_gl'
LINKFLTKIMG='-lfltk2_images'
LINKSHARED='-L../lib -lfltk2_images -lfltk2'
LOCAL_IMAGELIBS=''
LOCAL_IMAGETARGETS=''
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
LTLIBOBJS=''
MAKEDEPEND=''
mandir='${datarootdir}/man'
NROFF=''
OBJEXT=''
oldincludedir='/usr/include'
OPTIM=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
pdfdir='${docdir}'
POSTBUILD=''
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
RANLIB=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
SHAREDSUFFIX=''
SHELL='/bin/sh'
sysconfdir='${prefix}/etc'
target_alias=''
THEMECOMMAND=''
THREADS=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
XMKMF=''
ZLIBINC=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""

configure: exit 77

[tabstop]

I take it this is cygwin? In any event, these lines:

configure:2391: gcc    conftest.c  >&5
configure:2394: $? = 1

tell you that the command "gcc conftest.c" failed. Are you able to run gcc from the command line? If you use that particular conftest.c, do you have any problems?

[Shingetsu Kurai]

I use gcc (with Msys) regularly, although not from the command line.
I have no idea if I use confest.c though, it may be the problem then.

[tabstop]

Well, the conftest.c they used is there in the log, so you can look at it, but it's not really that exciting. But yes, you should make sure that gcc is working properly -- it was found, since gcc -v worked fine; but for some reason it gave an error when actually compiling something.

[kermit]

Hello all! I'm trying to install FLTK as a static library (after the headaches win32 API gave me I see RAD as a very good thing).
I got FLTK v2.0 alpha r8800 and I am trying to build it using a basic 'make install'

Is FLTK 2.x a requirement? If not, you may want to consider 1.3, as 2.x is pretty much a dead issue (except for the odd bug fix) whereas 1.3 is the current active release.

[Shingetsu Kurai]

2.x.x is not a requirement, but it is the same story with 1.3.x

Right now I'm using a pre-compiled static version of it (from Quincy), so this could be a temporary fix. And I know that gcc is working because I compile all my projects with it, though not from cmd.

[kermit]

2.x.x is not a requirement, but it is the same story with 1.3.x

Right now I'm using a pre-compiled static version of it (from Quincy), so this could be a temporary fix. And I know that gcc is working because I compile all my projects with it, though not from cmd.

Right - I should have been more specific and stated that my question was an aside as relating to your problem. I mentioned it only because the FLTK main page lists the 2.x branch, but does not clearly identify it as 'generally dormant' (as they state in the FAQ) and since 2.x is higher, one might tend to think it is the release to use.