Open poliana-girl opened 4 months ago
Experiencing the same issue when running configure for libaaio with gcc (GCC) 14.1.1 20240507 on kernel 6.8.9-arch1-2.
For me, commenting lines 1107-1109 of the configure
script bypasses the check and seems to allow ./configure
to complete.
Probably the best fix is to add the missing int type declaration to the test C program in line 1083 (see also line 1195 etc). This isn't CDP code, so modifying the config file feels like somewthing we should consider carefully, though I have seen no evidence of it being maintained/updated by the author since 2005. RD.
On 27/05/2024 07:11, modula t. wrote:
For me, commenting lines 1107-1109 of the |configure| script bypasses the check and seems to allow |./configure| to complete.
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-2132713399, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4XCS7GMVCXQUWXGI33ZELFCDAVCNFSM6AAAAABIKBS7CSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSG4YTGMZZHE. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I did this in libaaio src dir: export CFLAGS='-std-c89' and then ./configure --prefix=/usr/local
It compiles fine - but still having problems with the portaudio (paplay etc.) when trying to compile cdp itself.
Hello, im having trouble with the same error message. After running
sudo ./configure --prefix=/usr/local
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
I have reinstalled base-devel and tried to comment out lines 1107-1109 per defaultxr's suggestion. However im still stuck. I tried to compile a simple .c program with GCC and it worked. I have aclocal-1.17 installed.
Is this not the same problem reported earlier - edit the configure file to add "int " before "main" (there are/were two instances where this was omitted by accident: around lines 1083 and 1195). I have just tested it again on my Ubuntu setup, and it all passes. Maybe I should simply rezip libaaio with the corrected configure file? I will need to know that that edit fixes things. RD.
On 06/10/2024 13:51, syltensylten wrote:
Hello, im having trouble with the same error message. After running
|sudo ./configure --prefix=/usr/local |
|creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal-1.4... missing checking for working autoconf... found checking for working automake-1.4... missing checking for working autoheader... found checking for working makeinfo... found checking for gcc... gcc checking whether the C compiler (gcc ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. |
I have reinstalled base-devel and tried to comment out lines 1107-1109 per defaultxr's suggestion. However im still stuck. I tried to compile a simple .c program with GCC and it worked. I have aclocal-1.17 installed.
— Reply to this email directly, view it on GitHub <https://github.com/ ComposersDesktop/CDP8/issues/6#issuecomment-2395429327>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ ABNHS4WFF3OTNIKSQMES3LDZ2EW6TAVCNFSM6AAAAABIKBS7CSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQZDSMZSG4>. You are receiving this because you commented.Message ID: @.***>
While trying to run the configure script I get a weird error on my system. I'm on Fedora 40.
Here is my config.log file as well:
Anyone have any idea why this might be happening? Thank you.