|
|
|
| Allegro 4.2.1 compiler test |
|
kazzmir
Member #1,786
December 2001
 |
Evert, your last patch fixes the problem for me. |
|
juvinious
Member #5,145
October 2004
 |
I still had to make install-fixbundle before make install to get it to work. $ sudo make install Password: misc/mdhelper.sh /usr/local/lib /usr/local/include /usr/local/include/allegro /usr/local/include/allegro/platform /usr/local/include/allegro/internal /usr/local/include/allegro/inline /usr/local/bin install lib/macosx/liballeg-4.2.1.dylib /usr/local/lib (cd /usr/local/lib; ln -s -f liballeg-4.2.1.dylib liballeg-4.2.dylib) (cd /usr/local/lib; ln -s -f liballeg-4.2.1.dylib liballeg-4.dylib) (cd /usr/local/lib; ln -s -f liballeg-4.2.1.dylib liballeg.dylib) install -d /usr/local/lib install lib/macosx/liballeg-main.a /usr/local/lib ranlib /usr/local/lib/liballeg-main.a install -d /usr/local/bin allegro-config script created in /usr/local/bin make: *** No rule to make target `/usr/local/bin/fixbundle', needed by `generic-install'. Stop.
__________________________________________ |
|
kazzmir
Member #1,786
December 2001
|
You didnt apply the patch. |
|
juvinious
Member #5,145
October 2004
|
Obviously, I misunderstood and I thought it was applied to the repository. [edit] __________________________________________ |
|
Evert
Member #794
November 2000
 |
Great; I'll commit it later today when I'm back home. EDIT: Commited. |
|
Jakub Wasilewski
Member #3,653
June 2003
 |
GCC 3.4.2 (MinGW) under Windows XP Professional. Everything OK with the compilation stage. I tested binary compatibility using some of my games and the compiled examples from 4.2.0, no problems whatsoever. --------------------------- |
|
Evert
Member #794
November 2000
|
Ok, good to know. I should finally have some time to do a third RC tomorrow or the day after. |
|
Andrei Ellman
Member #3,434
April 2003
|
Evert said: I should finally have some time to do a third RC tomorrow or the day after. I've just posted a patch to the [AD] list that fixes two issues with pack_fopen_chunk(). Could you make sure it is included? AE. -- |
|
drwook
Member #7,800
September 2006
|
Well, I get this during 'make' on linux (x86_64) with gcc 4.1.1 - just me?; |
|
kazzmir
Member #1,786
December 2001
|
Did you pass any options to ./configure ? I have an amd64 too and I have no problems, but I pass --disable-asm to configure. |
|
drwook
Member #7,800
September 2006
|
I get that passing no options, just testing --disable-asm... ... Same I'm running glibc 2.4, I'm assuming there's no dependancy on linuxthreads or other problem related to that? Here's the output I get from './configure' in case it's useful (looks sane to me, but as something's wrong it might be here! ) checking for gcc... gcc |
|
Thomas Fjellstrom
Member #476
June 2000
 |
Try doing a "make clean", then start over. and if that still errors, do a make distclean. and make sure config.cache isn't around before you ./configure -- |
|
drwook
Member #7,800
September 2006
|
Same after 'make distclean'... I'll start randomly disabling things to try to work out what's breaking here |
|
Evert
Member #794
November 2000
|
Quote: I have an amd64 too and I have no problems, but I pass --disable-asm to configure.
You don't need to pass --disable-asm, it's implied (well, there is one asm routine in there: it wraps the CPUID instruction). I have an AMD64 as well and can confirm that it works for me. |
|
Milan Mimica
Member #3,877
September 2003
 |
"make depend" should do, though I think it's implicated by "make distclean"
-- |
|
drwook
Member #7,800
September 2006
|
Hmm... Can confirm same behaviour with gcc 3.4.6 and a 4.2.0 development build I have hanging around. Must be something to do with my system as nobody else seems to have seen this... Dependancy issue perhaps... |
|
Evert
Member #794
November 2000
|
Hmm... just to have asked, your system is running in 64 bit mode, right? |
|
drwook
Member #7,800
September 2006
|
Well I've rebuilt dependancies, and can now compile happily if I pass --disable-asm to configure - is this expected behaviour? How's it implying this if I shouldn't have to pass it, as it appears not to in my case? |
|
Evert
Member #794
November 2000
|
Quote: Well I've rebuilt dependancies, and can now compile happily if I pass --disable-asm to configure - is this expected behaviour?
It most definately is not. ./fix.sh unix ./configure make That's it. Anything more than that indicates a problem with the build process. Using an Allegro release (note: not a snapshot) you should never need to run make depend and you should never need to pass options to configure to compile Allegro. You most certainly should never need to pass --disable-asm. Quote: How's it implying this if I shouldn't have to pass it, as it appears not to in my case? Compiling on AMD64 automatically implies --disable-asm, since all the asm code is 32 bit assembler and incompatible with a 64 bit library. Anyway, you didn't answer my question: I said: just to have asked, your system is running in 64 bit mode, right?
|
|
drwook
Member #7,800
September 2006
|
Yes I'm running native 64 bit. I realise the asm is 32 bit, and so necessarily can't be built into a 64 bit binary. What I meant was, how does configure determine it's running on a 64 bit platform? As it appears to be failing that detection on my system. I took a look at the configure script, but was pretty tired last night and got a little lost |
|
Evert
Member #794
November 2000
|
Quote: What I meant was, how does configure determine it's running on a 64 bit platform? At the top of aclocal.m4:
Now... if they've changed the asm syntax (*again*) then maybe that can fail. Can you try it manually and see if it compiles? Quote: checking for processor type... amd64 EDIT: remember to re-run autoconf if you make changes to aclocal.m4 or configure.in |
|
drwook
Member #7,800
September 2006
|
No, that certainly compiles and seems to give the expected output... Very odd... Haven't managed to find anything obvious causing the problem, but will try to take a proper look later as I have to dash off for a few hours. (have found a few other people with this issue on amd64, but still appears to be a very small minority) |
|
Evert
Member #794
November 2000
|
Can you post the linker line that links the library? |
|
Milan Mimica
Member #3,877
September 2003
|
Just wanted to point out that makefile for MSVC (and possibly other makefiles, I didn't check) are incompatible with make-3.81. Version 3.80 works. `make' says : "makefile.vc:258: *** target pattern contains no `%'. Stop." I think it needs to be fixed before 4.2.1 is released because everyone will start using 3.81 soon. Makefile for unix is fine.
-- |
|
Evert
Member #794
November 2000
|
Sure. Do you have a fix? |
|
|
|
