Allegro.cc - Online Community

Allegro.cc Forums » Installation, Setup & Configuration » help with installing allegro in linux

This thread is locked; no one can reply to it. rss feed Print
help with installing allegro in linux
flares
Member #3,463
April 2003
avatar

I been trying to install allegro on a linux machine and it just won't give its an old laptop with vector linux on it. i unpacked it with tar -xzvf and then run ./fix.sh unix --quick and then ./configure and the configure just keeps on going and going and going it ran for about 4hrs and I thought it had been compiling, when the configure script runs I saw something about --recheck --no-recursive does that have anything to do with it?. please help

[nonnus29]Plus the api is crap ... I'd rather chew broken glass then code with those.

razor
Member #2,256
April 2002
avatar

Version of allegro, and linux distro?

Whoooo Oregon State University

HoHo
Member #4,534
April 2004
avatar

You could try fix without quick but I doubt it's the problem. I've installed allegro on different versions of linux tens of times and only gcc 4.0.0beta in FC4 test2 gave some minor trouble.

__________
In theory, there is no difference between theory and practice. But, in practice, there is - Jan L.A. van de Snepscheut
MMORPG's...Many Men Online Role Playing Girls - Radagar
"Is Java REALLY slower? Does STL really bloat your exes? Find out with your friendly host, HoHo, and his benchmarking machine!" - Jakub Wasilewski

Evert
Member #794
November 2000
avatar

I think there used to be a bug where the configure script would get stuck in an infinite loop if some libraries are not available. Should have been fixed a while back though.

So yeah, what version of Allegro?

flares
Member #3,463
April 2003
avatar

i tried 4.1.18, 4.2 beta I have yet to tried the 4.0.3, and the problem is exactly what you said evert it seems like its stuck in an infinate loop, the distro is Vector linux, which is based on slackware.

[nonnus29]Plus the api is crap ... I'd rather chew broken glass then code with those.

Evert
Member #794
November 2000
avatar

Can you interrupt the configure run and post the output before the restart? I'm curious to know what causes this.

flares
Member #3,463
April 2003
avatar

sure here it is

checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking whether -fomit-frame-pointer is safe... yes
checking whether an include prefix is needed... yes
checking how to run the C preprocessor... gcc -E
checking whether a C++ compiler is installed... yes
checking whether linker works with -s option... yes
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for ldconfig... /sbin/ldconfig
checking for makeinfo... /usr/bin/makeinfo
checking for install-info... /usr/bin/install-info
checking for processor type... i386
checking whether -mtune is supported... no
checking for MMX support... yes
checking for SSE support... yes
checking for asm prefix before symbols... ""
checking whether byte ordering is bigendian... no
checking for MAP_FAILED... yes
checking for sched_yield in -lc... yes
checking for constructor attribute... yes
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking whether --export-dynamic linker flag is supported... yes
checking for dlopen in -ldl... yes
checking soundcard.h usability... no
checking soundcard.h presence... no
checking for soundcard.h... no
checking sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking machine/soundcard.h usability... no
checking machine/soundcard.h presence... no
checking for machine/soundcard.h... no
checking linux/soundcard.h usability... yes
checking linux/soundcard.h presence... yes
checking for linux/soundcard.h... yes
checking for supported ALSA version for digital sound... no
checking for supported ALSA version for MIDI... no
checking for esd-config... /usr/bin/esd-config
checking for esd_open_sound... yes
checking for artsc-config... no
checking for alOpenPort in -laudio... no
checking for soundcard.h... (cached) no
checking for sys/soundcard.h... (cached) yes
checking for machine/soundcard.h... (cached) no
checking for linux/soundcard.h... (cached) yes
checking linux/awe_voice.h usability... yes
checking linux/awe_voice.h presence... yes
checking for linux/awe_voice.h... yes
checking sys/procfs.h usability... yes
checking sys/procfs.h presence... yes
checking for sys/procfs.h... yes
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for XMissingExtension in -lXext... yes
checking X11/xpm.h usability... yes
checking X11/xpm.h presence... yes
checking for X11/xpm.h... yes
checking for XpmCreatePixmapFromData in -lXpm... yes
checking for XcursorImageCreate in -lXcursor... yes
checking for XShmQueryExtension in -lXext... yes
checking for XF86VidModeQueryExtension in -lXxf86vm... yes
checking for XDGAQueryExtension in -lXxf86dga... yes
checking for XOpenIM in -lX11... yes
checking sys/io.h usability... yes
checking sys/io.h presence... yes
checking for sys/io.h... yes
checking linux/joystick.h usability... yes
checking linux/joystick.h presence... yes
checking for linux/joystick.h... yes
checking linux/input.h usability... yes
checking linux/input.h presence... yes
checking for linux/input.h... yes
checking linux/fb.h usability... yes
checking linux/fb.h presence... yes
checking for linux/fb.h... yes
checking vga.h usability... yes
checking vga.h presence... yes
checking for vga.h... yes
checking for vga_init in -lvga... yes
checking for vga_version in vga.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking for pkg-config... /usr/bin/pkg-config
checking for jack_client_new... no
checking for ANSI C header files... (cached) yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking whether time.h and sys/time.h may both be included... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking return type of signal handlers... void
checking for mmap... yes
checking for memcmp... yes
checking for mkstemp... yes
checking for stricmp... no
checking for strlwr... no
checking for strupr... no
checking for vprintf... yes
configure: creating ./config.status
config.status: creating makefile
config.status: creating allegro-config
config.status: creating include/allegro/platform/alunixac.h
config.status: include/allegro/platform/alunixac.h is unchanged
config.status: executing default commands
/bin/sh ./config.status --recheck
running /bin/sh ./configure --no-create --no-recursion
in -lXext...

Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found

[nonnus29]Plus the api is crap ... I'd rather chew broken glass then code with those.

Evert
Member #794
November 2000
avatar

Hmm... it was jack the last time too, if I remember correctly. I thought it was fixed...
You should be able to disable it manually by passing a configure switch. Run ./configure --help to see a list of valid switches, I'm not sure which one it is (probably --disable-jack).

In the meantime, I'm forwarding this to the mailinglist. Thanks for reporting.

flares
Member #3,463
April 2003
avatar

no problem, i'll try what you said, I don't have the laptop with me at the moment. Also I guess I can start compiling allegro and reporting errors, I always wanted to help with the development of allegro, since I also have all sorts of machines to test on i got xp, linux, the only thing I need is a mac. :)

[nonnus29]Plus the api is crap ... I'd rather chew broken glass then code with those.

Evert
Member #794
November 2000
avatar

Elias, on the mailing list, said:

I remember it, and it happened to me as well - I don't think we ever
found the cause though. configure just would keep repeating itself (the
warning about "jack" doesn't have to do anything with it I think.. it
just happens to be the last one or something). I suspect a bug in
autoconf.. it really is messed up. I think I have 4 or 5 different
versions of some of the autotools installed, and in my experience
everytime I compile something I need to hide some versions until it
works :P

:-/

BAF
Member #2,981
December 2002
avatar

last time (probably back around 4.0.3 being new) i compiled it on linux (mandrake) it did a loop like that. It repeated itself 3 times then stopped, and then i could run make

flares
Member #3,463
April 2003
avatar

I tryied 4.0.3 and it work like a charm, the only problem I had was figuring out how to use allegro-config script but other than that it work fine. I'll keep on trying and see why it is that it loops and if I figured why i'll post it to the mailing list.

[nonnus29]Plus the api is crap ... I'd rather chew broken glass then code with those.

Evert
Member #794
November 2000
avatar

If you can, try to find out which WIP version first shows the problem. It will help in narrowing down the list of suspects.

EDIT: or, if the machine is connected to the internet and you feel comfortable with that, create a second user account and send me the information so I can login remotely on the machine and try to compile Allegro myself to figure out what the problem is.

Go to: