[CSOUND-DEV:3935] Re: How to configure
Date | 2004-01-17 16:35 |
From | stevenyi |
Subject | [CSOUND-DEV:3935] Re: How to configure |
Hi John, Just a thought, are you running autoreconf in the top directory? I just did a fresh checkout here (redhat 9.0) and got the following: [steven@localhost csound]$ autoreconf -i configure.ac: installing `./install-sh' configure.ac: installing `./mkinstalldirs' configure.ac: installing `./missing' Makefile.am: installing `./INSTALL' anal/adsyn/Makefile.am: installing `./depcomp' csound/Makefile.am: installing `./compile' doc/Makefile.am:1: installing `doc/mdate-sh' doc/Makefile.am:1: installing `doc/texinfo.tex' [steven@localhost csound]$ autoreconf -f [steven@localhost csound]$ ls aclocal.m4 config.sub CsoundVST jfpp.mk OSC-Kit anal configure CsoundVSTWin ltmain.sh pyrun AUTHORS configure.ac CVS Makefile.am README autom4te.cache COPYING depcomp Makefile.in soundfonts ChangeLog cscofils doc missing util1 compile csound INSTALL mkinstalldirs util2 config.guess csound.spec.in install-sh NEWS [steven@localhost csound]$ autoreconf -V autoreconf (GNU Autoconf) 2.57 Written by David J. MacKenzie and Akim Demaille. Copyright 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [steven@localhost csound]$ I recently had troubles using 2.59 of the GNU Autotools. Maybe the version of autoreconf/autoconf/etc. you're using might be a problem? steven On Sat, 2004-01-17 at 14:28, jpff@codemist.co.uk wrote: > I have just d/loaded csound(4) onto a fresh machine -- Debian. I see > from README that as there is no INSTALL file that I should go > autoreconf -i > autoreconf -f > and then ./configure > My problem is that there is no ./configure file to run. No comment > from the other two commands. What am I supposed to do next? > > ==John ffitch > Glad I kept my running sources on another machine > > |
Date | 2004-01-17 19:28 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3934] How to configure |
I have just d/loaded csound(4) onto a fresh machine -- Debian. I see from README that as there is no INSTALL file that I should go autoreconf -i autoreconf -f and then ./configure My problem is that there is no ./configure file to run. No comment from the other two commands. What am I supposed to do next? ==John ffitch Glad I kept my running sources on another machine |
Date | 2004-01-17 20:07 |
From | John ffitch |
Subject | [CSOUND-DEV:3937] Re: How to configure |
I was certainly in the csound directory. This is a just updated debian system and so it has whatever Debian stable gives. autoreconf -i and 0f gave no output at all. ==John ff |
Date | 2004-01-17 20:16 |
From | John ffitch |
Subject | [CSOUND-DEV:3939] Re: How to configure |
Version 2.13 On Sat, 17 Jan 2004, John ffitch wrote: > I was certainly in the csound directory. This is a just updated debian > system and so it has whatever Debian stable gives. autoreconf -i and 0f > gave no output at all. > ==John ff > > > > |
Date | 2004-01-17 21:41 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3942] Re: How to configure |
John, I so happy to hear you're trying the GBS version of Csound, but remember, if the GBS version of Csound fails you for any reason, you should be able to build with the original makefiles. Just cd into the csound directory and you should find Makefile.lnx. This should allow you to build a system as you have always done. If this is broken, let's fix it soon. One of the reasons I made sure the original makefiles continued to work is because of questions with Debian systems. But back to the GBS version. I have been led to believe that Debian provides a modern version of autoconf, but an old version of automake. Please send the version of autoconf, automake, and libtoolize that is available on your machine. On RH9, the versions are: $ autoconf --version -autoconf (GNU Autoconf) 2.57 Written by David J. MacKenzie and Akim Demaille. Copyright 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ automake --version automake (GNU automake) 1.6.3 Written by Tom Tromey |
Date | 2004-01-18 14:47 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3944] Re: How to configure |
> But back to the GBS version. I have been led to believe that Debian > provides a modern version of autoconf, but an old version of > automake. I've also been told that Debian systems have a program called appget for pulling down new packages, and updating old ones. You should be able to quickly update automake, or whatever, with that program. John |
Date | 2004-01-18 15:38 |
From | John ffitch |
Subject | [CSOUND-DEV:3945] Re: How to configure |
...but I updated everything immediately before I called cvs (including a new cvs)..... GBS? |
Date | 2004-01-18 17:09 |
From | John ffitch |
Subject | [CSOUND-DEV:3946] Re: How to configure |
Longer report. Debian Stable has autoconf 2.53 but the build says it needs 2.59 or later. I have fiddled to get a more recent version of autoconf from the testing/unstable world and after only 1 hr of reinstalling and uninstalling packages it is compiling, albeit with many warnings which used not to be there. Some of these come from the autoconf stuff, but some comes from C (like non declaration of strrchr in getstring.c which does not happen on my working system). I dislike this kind of departure from ANSI C. I will not take the CVS system seriously for csound4 in thsi state. ==John ff |
Date | 2004-01-18 17:35 |
From | Dave Phillips |
Subject | [CSOUND-DEV:3947] Re: How to configure |
John D. Ramsdell wrote: >I've also been told that Debian systems have a program called appget >for pulling down new packages, and updating old ones. You should be >able to quickly update automake, or whatever, with that program. > > Hi all: Just a quick note regarding the apt system. I use it for both my Planet CCRMA (Red Hat) and Demudi (Debian) systems, and I must admit I've come to love it. It is great for updating old packages and installing new ones, very easy to use and very effective, particularly with regards to maintaining system stability. Good stuff... Btw, the actual term is "apt-get"... Best, == dp |
Date | 2004-01-18 17:39 |
From | John ffitch |
Subject | [CSOUND-DEV:3948] Re: How to configure |
...and more. The make fails as winX11.o does not exist when it creates someting called libanalutils.a whatever that it for. Seems even more broken that I thought! I do hope that the Csound5 tree is not in this state. ==John ff |
Date | 2004-01-18 18:15 |
From | Dave Phillips |
Subject | [CSOUND-DEV:3949] Re: How to configure |
Greetings: Another short note. I retrieved CVS trees for both Csound4 and Csound5 two days ago. As stated in a previous note, I compiled both under GCC 3.2.2 from Planet CCRMA's Red Hat 9.0. I made almost no changes to the sources, only switching some -malign-loops and -malign-jumps compiler directives to -falign-loops and -falign-jumps to get rid of the warnings (as per the compiler messages). Following jpff's suggestion I installed PortAudio 18.1 and Csound5 also compiled without other errors. Alas, I have not had time to check either version for performance, but with John's metro plugin (Thank you, John!) I'll get back to work on ImproSculpt and can test it against both versions. I should have a report by Tuesday. Best regards, == dp John ffitch wrote: >...and more. The make fails as winX11.o does not exist when it creates >someting called libanalutils.a whatever that it for. Seems even more >broken that I thought! > >I do hope that the Csound5 tree is not in this state. > >==John ff > > > > |
Date | 2004-01-18 20:44 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3951] Re: How to configure |
John ffitch |
Date | 2004-01-18 20:55 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3952] Re: How to configure |
Dave Phillips |
Date | 2004-01-18 21:07 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3953] Re: How to configure |
>>>>> "John" == John D Ramsdell |
Date | 2004-01-18 21:30 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3954] Re: How to configure |
.... I did cd csound make winX11.o cd .. and then make is running. I am still seeing a distressing number of undeclared functions -- I have Csound so there were no such warnings -- but what does "-I ../[csound" mean as a option to gcc?] I am also rather at a loss as to whu configure asks if bzero (for example) exists as this not an ANSI C function and Csound should not care a d*mn whether it does or not. That suggests some fundamental errors in the configuration mechyanism to me. ==John ffitch |
Date | 2004-01-19 12:07 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3962] Re: How to configure |
jpff@codemist.co.uk writes: > I thought the whole point of the autoconf stuff was to write a > correct makefile. No I have not tried that as i was acting like a > user, nit a developer. Let me explain my take on the contents of the csound module. I think this is a situation in which I've made most of these points, but they have been scattered in various messages. I have been following the rule that the csound module is different than the csound5 module in that it must retain the capability of being built using the original makefiles. Furthermore, it must not contain the results of any of the GNU build system tools. In particular, the module should not have a copy of configure in its top-level directory. If you export the contents of the csound module, you will obtain a system with a README that starts with: If your distribution has a file named ./configure, build using the instructions in INSTALL, otherwise, find a Makefile that matches your system in the csound directory. Rename it to Makefile, and then edit it following the instructions in its comments. Since the exported version of csound does not contain a file named ./configure, the user is directed to build a system following the same procedure that was used when Csound did not have an open source license. Here is another important point to make: there is no reason the GNU build system tools must be available on every platform used to build csound. They only need to be available on the platforms used to build a distribution. To satisfy Micheal's request that a distribution be capable of building DLLs on Cygwin, I've been using the GNU build system tools on Cygwin. I've found that the current tools on Red Hat Linux do not write a libtool script that recognizes Windows DLLs. The csound5 module can include the results of running GNU build system tools. I imagine that the tools will be run on Cygwin, but testing will tell the best platform. In any event, it looks like they will not be run on Debian in the immediate future unless someone figures out how to update the tools on Debian. This is no problem because Debian users will simply get the results of running the tools when the sources are checked out of the csound5 module. John |
Date | 2004-01-19 12:23 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3963] Re: How to configure |
jpff@codemist.co.uk writes: > I am still seeing a distressing number of undeclared functions ... and there are other distressing messages too. I've seen this whenever I specify -Wall with GCC. I think you get them when using the original makefiles too, but I could be wrong. The ChangeLog records that I fixed the worst of the distressing messages in October. 2003-10-13 John D. Ramsdell |
Date | 2004-01-19 18:43 |
From | Dave Phillips |
Subject | [CSOUND-DEV:3966] Re: How to configure |
Greetings: I used the GNU build tools for both 4 and 5. I'll test Makefile.lnx under AGNULA Demudi this afternoon. Best, == dp John D. Ramsdell wrote: >Dave Phillips |
Date | 2004-01-19 21:23 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3970] Re: How to configure |
Dave Phillips |
Date | 2004-01-23 14:27 |
From | Dave Phillips |
Subject | [CSOUND-DEV:3990] Re: How to configure |
Greetings: I finally got around to upgrading my AGNULA system to Demudi 1.1.0. This system is based on a Debian 3.0 distribution, with fairly current ALSA and other components. Results were not so good. Trying to unpack 4-23f09gbs resulted in this failure : dlphilp@localhost:~$ tar xzvf Csound_423f09.tar.gz csound_4.23f09/ csound_4.23f09/3Dug.h tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--format violated tar: Child returned status 1 tar: Error exit delayed from previous errors I tried to build 4.23f08 instead and got this far : dlphilp@localhost:~/csound$ make cc -Wall -O2 -malign-loops=4 -malign-jumps=4 -ffast-math -fomit-frame-pointer -finline-functions -funroll-loops -DWITHx87 -DWINDOWS -DRTAUDIO -DSFIRCAM -DSYS5 -DLINUX -DPIPES -DMACROS -DTCLTK -DIV_SCHED -DHAVE_FLTK -c main.c -o main.o cc1: warning: -malign-loops is obsolete, use -falign-loops cc1: warning: -malign-jumps is obsolete, use -falign-jumps In file included from main.c:24: cs.h:31:24: autoheader.h: No such file or directory In file included from cs.h:36, from main.c:24: sysdep.h:24:24: autoheader.h: No such file or directory make: *** [main.o] Error 1 Which leads me to believe I'm missing a system component (very likely: I had some trouble with the upgrade). I don't know if any of this is helpful, but there you have it. Btw, the csound that comes with Demudi works fine. Best regards, Dave Phillips John D. Ramsdell wrote: >Dave Phillips |
Date | 2004-01-23 19:06 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3993] Re: How to configure |
Dave Phillips |
Date | 2004-01-23 20:51 |
From | Dave Phillips |
Subject | [CSOUND-DEV:3995] Re: How to configure |
Greetings: Sorry, I thought I'd done it right but it was late, I was tired, I was abducted by aliens... So I logged back into my Demudi partition, got the correct sources, and ran './configure --with-fltk'. Unfortunately Demudi seems to have an incomplete installation of FLTK (no fltk-config) so the configure script politely declined to compile in FLTK support. No problem, I ran 'make', things move along all right until here : gcc -I./../../csound -g -O2 -Wall -falign-loops=4 -falign-jumps=4 -ffast-math -fomit-frame-pointer -finline-functions -funroll-loops -o hetro main.o ../../csound/libanalutils.a -ldl -lm ../../csound/libanalutils.a(libanalutils_a-hetro.o)(.text+0x41f): In function `hetro': /home/dlphilp/csound-4.23f09gbs.1/csound/hetro.c:286: undefined reference to `POLL_EVENTS' ../../csound/libanalutils.a(libanalutils_a-hetro.o)(.text+0x531):/home/dlphilp/csound-4.23f09gbs.1/csound/hetro.c:301: undefined reference to `POLL_EVENTS' ../../csound/libanalutils.a(libanalutils_a-hetro.o)(.text+0xc7b): In function `hetdyn': /home/dlphilp/csound-4.23f09gbs.1/csound/hetro.c:359: undefined reference to `POLL_EVENTS' ../../csound/libanalutils.a(libanalutils_a-hetro.o)(.text+0xda9):/home/dlphilp/csound-4.23f09gbs.1/csound/hetro.c:383: undefined reference to `POLL_EVENTS' ../../csound/libanalutils.a(libanalutils_a-hetro.o)(.text+0xe83):/home/dlphilp/csound-4.23f09gbs.1/csound/hetro.c:403: undefined reference to `POLL_EVENTS' collect2: ld returned 1 exit status make[2]: *** [hetro] Error 1 make[2]: Leaving directory `/home/dlphilp/csound-4.23f09gbs.1/anal/adsyn' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/dlphilp/csound-4.23f09gbs.1/anal' make: *** [all-recursive] Error 1 dlphilp@localhost:~/csound-4.23f09gbs.1$ gcc --version gcc (GCC) 3.3.2 (Debian) There you have it. Best regards, ++ dp John D. Ramsdell wrote: >> Results were not so good. Trying to unpack 4-23f09gbs resulted in >>this failure : >> >>dlphilp@localhost:~$ tar xzvf Csound_423f09.tar.gz >> >> > >This suggests that you got the sources from the csound package of the >csound project on SourceForge. I would like you to try the sources >from the wxcsound package version 1.02. The Csound sources are in the >following file: > >csound-4.23f09gbs.1.tar.gz > >John > > > > |
Date | 2004-01-24 09:26 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3997] Re: How to configure |
I took the files from an anonymous cvs, but then hit the autoconf being the wrong version. I have been given a recipe for allowing mixing stable/testing/unstable but then apt-get crashs with insufficient memory in mmap. I still conclude that at the current moment, Debian users are lost. Yes I could get it going by copying from my working system, but that is not the point. ==John ffitch |
Date | 2004-01-24 11:41 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:4000] Re: How to configure |
Dave Phillips |
Date | 2004-01-24 11:44 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:4001] Re: How to configure |
jpff@codemist.co.uk writes: > I took the files from an anonymous cvs, but then hit the autoconf > being the wrong version. .... Yes, but could you build a system on Debian by folling the instructions in the README for the case in which no configure file is present? John |
Date | 2004-01-25 07:32 |
From | Antoine Lefebvre |
Subject | [CSOUND-DEV:4003] Re: How to configure |
Attachments | None |
Date | 2004-01-25 16:25 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:4004] Re: How to configure |
There is only one Makefile visible so I tried make as that will use Makefile. The result is apparently ok until trying to make .libs/libcsound.so.0.0.0 (whatever that is for) when it crashes with gcc: winX11.lo: No such file or directory Strange that it should link it without compiling it. No idea what a .lo file is so I am stuck again. ==John ffitch |
Date | 2004-01-25 16:38 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:4005] Re: How to configure |
Thanks; adding APT::Cache-Limit 12582912; ^___________NB certainly improves things. ==John ffitch |
Date | 2004-01-25 21:59 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:4008] Re: How to configure |
jpff@codemist.co.uk writes: > There is only one Makefile visible so I tried make as that will use > Makefile. John, please do this: $ find . -name Makefile.lnx -print Go to the directory in which that file lives and then do: $ cp Makefile.lnx Makefile << Edit Makefile to your liking >> $ make John |
Date | 2004-01-30 15:15 |
From | Dave Phillips |
Subject | [CSOUND-DEV:4018] Re: How to configure |
Hi John: I'm sorry I haven't been able to test your suggestions, I've simply been too busy with other projects. I must also confess that I'm quite confused regarding the recommended source archive for Csound for Linux. I've tried three source packages recently: the tarball at dream/newest at Bath, the public source tarball at SourceForge, and the CVS sources (for Csound4). Only the last package builds on my system. I have already reported the build failures here. I have also built the sources from your wxcsound package; however, I hesitate to recommend them because I'm trying to stay with the canonical track. Be assured, there's nothing wrong with your stuff. I'm preparing new materials for Rick Boulanger's site and for the Csound profile in my book. I'm currently recommending the CVS sources and have created a brief page of instructions for downloading and building those sources under Linux. I'll probably have stuff up at cSounds.com within a week or so. Btw, I've reworked Oeyvind Brandtsegg's ImproSculpt to run under Csound 4.23f08 (CVS). It runs very nicely, and I wanted to pass my thanks to the Csound developers. Best, dp John D. Ramsdell wrote: >Dave Phillips |
Date | 2004-02-01 14:30 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:4030] Csound 4.24f10gbs.0 released in wxcsound |
I patched insert.c as requested by jpff and released Csound 4.24f10gbs.0 in the wxcsound package on SourceForge. I notice that releasing the GNU Build System version of Csound in the wxcsound package destroys download statistics, because the version of the package is determined by wxCsound, and does not change to follow csoundgbs release numbers. Perhaps jpff should create a csoundgbs package for GNU Build System releases so they can reflect accurate version numbers and download statistics. Sound like a good idea? John divan$ sfcvs csound diff -u -r csound-4_23f09gbs_1 ramsdell@cvs.csound.sourceforge.net's password: cvs diff: Diffing . Index: ChangeLog =================================================================== RCS file: /cvsroot/csound/csound/ChangeLog,v retrieving revision 1.46 retrieving revision 1.49 diff -u -r1.46 -r1.49 --- ChangeLog 17 Jan 2004 16:36:46 -0000 1.46 +++ ChangeLog 31 Jan 2004 23:13:22 -0000 1.49 @@ -1,3 +1,18 @@ +2004-01-31 John D. Ramsdell |