Cannot finish configure script while trying to compile libaaio
While trying to run the configure script I get a weird error on my system. I'm on Fedora 40.
$ ./configure --prefix=/usr/local
loading 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.
Here is my config.log file as well:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:731: checking for a BSD compatible install
configure:784: checking whether build environment is sane
configure:841: checking whether make sets ${MAKE}
configure:887: checking for working aclocal-1.4
configure:900: checking for working autoconf
configure:913: checking for working automake-1.4
configure:926: checking for working autoheader
configure:939: checking for working makeinfo
configure:957: checking for gcc
configure:1070: checking whether the C compiler (gcc ) works
configure:1086: gcc -o conftest conftest.c 1>&5
configure:1083:1: error: return type defaults to 'int' [-Wimplicit-int]
1083 | main(){return(0);}
| ^~~~
configure: failed program was:
#line 1081 "configure"
#include "confdefs.h"
main(){return(0);}
Anyone have any idea why this might be happening? Thank you.
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: @.***>
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#6#issuecomment-2395429327>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ ABNHS4WFF3OTNIKSQMES3LDZ2EW6TAVCNFSM6AAAAABIKBS7CSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGQZDSMZSG4>. You are receiving this because you commented.Message ID: @.***>
I'm sorry, i tried it but it did not make any difference. Until just now. It's now correctly installed thanks to adding "int" before main on line 1083. I probably messed something else up in my previous attempts.
Thanks
configure: error: installation or configuration problem: C compiler cannot create executables.
my method has an example of a fix which avoids this. you can check it out here
https://github.com/ComposersDesktop/CDP8/issues/18#issuecomment-3243121212
specific command in my example related to this: autoreconf-2.72 -fi
Yes, needed the int main correction in that line. All other instances in configure are good.
I have replaced the original zip (0.3.1) of libaaio in git with libaaio-0.3.2.
Expect further changes in due course - it is time libaaio was folded into the CMake system.
RD
On 26/05/2024 20:48, poliana coder wrote:
While trying to run the configure script I get a weird error on my system. I'm on Fedora 40.
|$ ./configure --prefix=/usr/local loading 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. | |.. #line 1081 "configure" #include "confdefs.h" main(){return(0);} |
Anyone have any idea why this might be happening? Thank you.
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4X2WDISD3P37ECITCDZEI4BHAVCNFSM6AAAAABIKBS7CSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTOOJQG4ZTAOI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
That sounds to me like a good plan, and your maintenance of the project is greatly appreciated.
libaaio no longer exists in any existing repository of system-installed packages for UNIX-like operating systems except for one unofficial repository for Slackware, where it has no reverse dependencies and has not received any updates since 2005,
https://repology.org/project/libaaio/versions
therefore, it seems like a perfect example of a project that would be most conveniently built and maintained as a "vendored" subfolder within the still-maintained software projects that still depend on it, like CDP8.
Thank you Mr Dobson for replacing the libaaio file which worked like a charm ( after weeks of sleepless nights). But the problem I'm having now is on compiling CDP it's asking for Libaaio 0.3.1.
CMake Error: The source "/home/thomas/Downloads/CDP8-main/CDP8-main/CMakeLists.txt" does not match the source "/home/thomas/SDPBuild/libaaio-0.3.1/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
Why is it asking for this.
Thank you Mr Dobson for replacing the libaaio file which worked like a charm ( after weeks of sleepless nights). But the problem I'm having now is on compiling CDP it's asking for Libaaio 0.3.1.
CMake Error: The source "/home/thomas/Downloads/CDP8-main/CDP8-main/CMakeLists.txt" does not match the source "/home/thomas/SDPBuild/libaaio-0.3.1/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
Why is it asking for this.
IIRC, I re-compiled from the start after doing a "git pull" and it compiled.
Any change of this nature generally requires deleting Cmake cache files and rerunning cmake. Simplest is just to delete your current "build" directory and make a fresh one, then run cmake again. Sometimes simply deleting the CMakeCache.txt file is enough - worth trying, anyway.
RD.
I see you have (or had) a CMakeLists.txt file inside the libaaio folder
On 04/09/2025 14:35, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3253761006
Thank you Mr Dobson for replacing the libaaio file which worked like a charm ( after weeks of sleepless nights). But the problem I'm having now is on compiling CDP it's asking for Libaaio 0.3.1.
CMake Error: The source "/home/thomas/Downloads/CDP8-main/CDP8-main/CMakeLists.txt" does not match the source "/home/thomas/SDPBuild/libaaio-0.3.1/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory.
Why is it asking for this.
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3253761006, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4TQER6TYGRFAHNRNIL3RA5ZDAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJTG43DCMBQGY. You are receiving this because you commented.Message ID: @.***>
Sorry to pester you but although I successfully compiled libaaio, i can't for the life of me compile CDP program. It either can't find a source or can't find CMakeList.txt. The build instructions are very vague for Linux. I did as you said but it's not cooperating using Terminal or the CMake gui.
I have updated the repository; the aaio library is now absorbed into the CMake system (new folder dev/aaio), so the external build step is no longer required. The original tgz archive is retained, for anyone interested. "building.txt" has been revised and expanded a little, mostly discussing portaudio.
RD
On 05/09/2025 11:49, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3257924035
Sorry to pester you but although I successfully compiled libaaio, i can't for the life of me compile CDP program. It either can't find a source or can't find CMakeList.txt. The build instructions are very vague for Linux. I did as you said but it's not cooperating using Terminal or the CMake gui.
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3257924035, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4RT6UDUIDXBLTUG7T33RFTCLAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJXHEZDIMBTGU. You are receiving this because you commented.Message ID: @.***>
Awesome, thanks for the update!
On Thu, Sep 11, 2025 at 5:26 PM Richard W Dobson @.***> wrote:
richarddobson left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3281739139 I have updated the repository; the aaio library is now absorbed into the CMake system (new folder dev/aaio), so the external build step is no longer required. The original tgz archive is retained, for anyone interested. "building.txt" has been revised and expanded a little, mostly discussing portaudio.
RD
On 05/09/2025 11:49, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) < https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3257924035>
Sorry to pester you but although I successfully compiled libaaio, i can't for the life of me compile CDP program. It either can't find a source or can't find CMakeList.txt. The build instructions are very vague for Linux. I did as you said but it's not cooperating using Terminal or the CMake gui.
— Reply to this email directly, view it on GitHub < https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3257924035>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABNHS4RT6UDUIDXBLTUG7T33RFTCLAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJXHEZDIMBTGU . You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3281739139, or unsubscribe https://github.com/notifications/unsubscribe-auth/AULPN2MRUXNW3V7CF72JWID3SGPDDAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBRG4ZTSMJTHE . You are receiving this because you commented.Message ID: @.***>
What does this mean. cd build cmake ..
(this creates Makefiles for each program and group of programs)
I still get errors asking for various things. Do I have to add something to this code as it isn't going anywhere. Thanks
These are standard command line commands, commin to Linux and the Mac (using Terminal). 'cd' means 'change directory'. 'cmake' is the program which you will (if necessary) previously have installed, and which builds the correct makefiles (list of commands to the compiler); and the command 'make' calls the program of that name which builds everything. The double-dot ".." is shorthand for "the parent directory", or, if you like, "the directory containing the one I am in". Using the command line you are always "in" some directory or other.
Many so-to-speak hardcore Linux developers barely use a GUI at all; everything is controlled from the command line. or indeed from the famous text editor "emacs" (looong story!).
This repository is not really the place for a tutorial on the use of the command line, but as part of the CDP documentation I wrote this article, which I hope will help with all this:
https://www.composersdesktop.com/docs/htmltuts/terminal/usingterminal.htm
Now that CDP has moved compilation to CMake, I get that maybe an update to that tutorial is in order, but that will of course take time.
For better or worse, there is something of a "learning curve" getting used to working at the command line, especially if one has never departed from the OS GUI environment before. Took me a while to climb that curve (long ago now, in the days of the Atari ST); fortunately the commands and procedures outlined in that paper are sufficient for 99% of the things you will want/need to do. RD.
On 12/09/2025 12:59, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285002546
What does this mean. cd build cmake ..
(this creates Makefiles for each program and group of programs)
I still get errors asking for various things. Do I have to add something to this code as it isn't going anywhere. Thanks
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285002546, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4UYC6WT4VFFP3TDT333SKYTDAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBVGAYDENJUGY. You are receiving this because you commented.Message ID: @.***>
Thanks for the tip! I was just puzzled by some of the code, especially the two dots as I have compiled before without incident or any of the other 'remarks' that CMake made. It just kept telling me that it couldn't find the makefiles or that they were the incorrect ones for it and other such nonsense. I just compiled a PipeWire install with meson and it flew along without complaint. I'm very wary of this CMake now but I am quite pleased by the efficiency of Terminal. All the best
On Fri, Sep 12, 2025 at 3:59 PM Richard W Dobson @.***> wrote:
richarddobson left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285624515 These are standard command line commands, commin to Linux and the Mac (using Terminal). 'cd' means 'change directory'. 'cmake' is the program which you will (if necessary) previously have installed, and which builds the correct makefiles (list of commands to the compiler); and the command 'make' calls the program of that name which builds everything. The double-dot ".." is shorthand for "the parent directory", or, if you like, "the directory containing the one I am in". Using the command line you are always "in" some directory or other.
Many so-to-speak hardcore Linux developers barely use a GUI at all; everything is controlled from the command line. or indeed from the famous text editor "emacs" (looong story!).
This repository is not really the place for a tutorial on the use of the command line, but as part of the CDP documentation I wrote this article, which I hope will help with all this:
https://www.composersdesktop.com/docs/htmltuts/terminal/usingterminal.htm
Now that CDP has moved compilation to CMake, I get that maybe an update to that tutorial is in order, but that will of course take time.
For better or worse, there is something of a "learning curve" getting used to working at the command line, especially if one has never departed from the OS GUI environment before. Took me a while to climb that curve (long ago now, in the days of the Atari ST); fortunately the commands and procedures outlined in that paper are sufficient for 99% of the things you will want/need to do. RD.
On 12/09/2025 12:59, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) < https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285002546>
What does this mean. cd build cmake ..
(this creates Makefiles for each program and group of programs)
I still get errors asking for various things. Do I have to add something to this code as it isn't going anywhere. Thanks
— Reply to this email directly, view it on GitHub < https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285002546>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABNHS4UYC6WT4VFFP3TDT333SKYTDAVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBVGAYDENJUGY . You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3285624515, or unsubscribe https://github.com/notifications/unsubscribe-auth/AULPN2JZSAJFBRU2ZY5CLQT3SLNU3AVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBVGYZDINJRGU . You are receiving this because you commented.Message ID: @.***>
Must be my day, The compiler ran like a rocket then this.
/home/thomas/Downloads/CDP8/CDP8-main/dev/externals/paprogs/paplay/paplay.c:75:10: fatal error: pa_ringbuffer.h: No such file or directory 75 | #include "pa_ringbuffer.h" | ^~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/build.make:79: dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/paplay.c.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:9534: dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/all] Error 2 make: *** [Makefile:156: all] Error 2
What the F**k is this. Has it compiled or not.
Hope I'm not giving you too many problems.
fatal error: pa_ringbuffer.h: No such file or directory
@convinced-prog if you continue to encounter difficulties and would like to try a possible workaround, I have just posted an updated version of my CDP8 build script for generic GNU/Linux in the other thread, in which there is a functioning workaround for that error. I updated my script to work with the current commit in the main branch at time of writing, https://github.com/ComposersDesktop/CDP8/commit/8f427970d30896196f64ed44635a4bcbc87b48fb
- https://github.com/ComposersDesktop/CDP8/issues/18#issuecomment-3288163162
However, the steps I prefer to use might be a little different in some places from what the upstream developers of CDP8 might recommend for building on GNU/Linux, so you should keep in mind that my steps are unofficial.
Where have you put the sources of portaudio? We have always specified that it must be in the directory dev/externals/paprogs. That is where Cmake is told to find that file. The audio programs are put right at the end of the list of programs to build, so to answer your question, no, paplay has not built. But all the non-audio programs (some 200 of them now) will have been successfully built, and you will find them all in the top-level directory "NewRelease". RD.
On 13/09/2025 12:02, convinced-prog wrote:
convinced-prog left a comment (ComposersDesktop/CDP8#6) https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3288100042
Must be my day, The compiler ran like a rocket then this.
/home/thomas/Downloads/CDP8/CDP8-main/dev/externals/paprogs/paplay/paplay.c:75:10: fatal error: pa_ringbuffer.h: No such file or directory 75 | #include "pa_ringbuffer.h" | ^~~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/build.make:79: dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/paplay.c.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:9534: dev/externals/paprogs/paplay/CMakeFiles/paplay.dir/all] Error 2 make: *** [Makefile:156: all] Error 2
What the F**k is this. Has it compiled or not.
Hope I'm not giving you too many problems.
— Reply to this email directly, view it on GitHub https://github.com/ComposersDesktop/CDP8/issues/6#issuecomment-3288100042, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHS4QGXFHOUS4EVQ3FQTD3SP2U7AVCNFSM6AAAAACFLGNIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEOBYGEYDAMBUGI. You are receiving this because you commented.Message ID: @.***>