[CSOUND-DEV:3861] csound 4.23
Date | 2004-01-01 10:28 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3861] csound 4.23 |
Who changed all the file lay out so I can no longer fix bugs? Cssound4 is supposed to be frozen except for bugs. That means that nothing should change except to fix bugs. A bug is a manifestation of broken code, not a manifestation of something you do not like. So what should I do? Not fix the bugs? ==John ffitch |
Date | 2004-01-02 16:18 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3865] Re: csound 4.23 |
jpff@codemist.co.uk writes: > Who changed all the file lay out so I can no longer fix bugs? The only change I made is the one you have already heard about, the files used to build the csound library and the csound executable have been moved into their own directory. If the change I made is preventing you from fixing bugs, please describe in what way it does so. John |
Date | 2004-01-02 17:40 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3872] Re: csound 4.23 |
I fixed some bugs, went "cvs update" and all my files disappeared -- deleted. So I have abandoned the csound4 cvs as I do not have the time to reconstruct the entire tree again. The fixed files are in the release, and I did attempt to add them back, but that failed. ==John ffitch |
Date | 2004-01-02 17:47 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3874] Re: csound 4.23 |
jpff@codemist.co.uk writes: > I fixed some bugs, went "cvs update" and all my files disappeared -- > deleted. You must do "cvs update -d". This will give you the new directories. You'll then be good to go. John |
Date | 2004-01-02 18:39 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3877] Re: csound 4.23 |
But my files were still deleted. I cannot live with that kind of uncertainty ==John ffitch |
Date | 2004-01-02 21:44 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3880] Re: csound 4.23 |
jpff@codemist.co.uk writes: > But my files were still deleted. I cannot live with that kind of > uncertainty. When I find myself with a stale CVS sandbox, I often simply rename or delete it, and use a fresh check out. Be sure to tag any specific collection of files you want to retrieve as a group. Then you can always get back that collection using the -r option. Finally, anyone on the mailing list saying something about changing or adding directories is implicitly asking you to do a "cvs up -d". John |
Date | 2004-01-02 22:40 |
From | jpff@codemist.co.uk |
Subject | [CSOUND-DEV:3881] Re: csound 4.23 |
>>>>> "John" == John D Ramsdell |
Date | 2004-01-03 06:05 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3882] Re: csound 4.23 |
jpff@codemist.co.uk writes: > >>>>> "John" == John D Ramsdell |
Date | 2004-01-04 21:57 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3894] Re: csound 4.23 |
John ffitch, When I reorganized the module containing the Csound 4.23 sources, my goal was to ensure the new organization supported both the traditional method of building the sources and the configure-based method I was constructing. I took great care to make sure the original makefiles continue to build the sources, however, our recent mail exchanges causes me to guess the directory structure is giving you problems. Therefore, I added the file jpff.mk into the top-level directory. If you type $ make -f jpff.mk the source files in the csound directory will be moved up one level. Please let me know if this solves any problems you have with the new directory organization. John |
Date | 2004-01-06 11:22 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3910] Re: csound 4.23 |
I exported the version of csound tagged as csound-4.23a2, the last tagged version in the csound module before top-level source files were moved into the csound directory. I the performed a diff with the contents of csound_4.23f08. Without compiling, I noticed some problems. 1. The file entry2.c includes chosc.h, but a find in the csound_4.23f08 directory does not print a path with this file name. 2. The ChangeLog includes: + * OSC-sock.c: + * metro.c: Add casts to avoid warnings but the diff detected no changes to that file. I also moved widget.cpp into the csound directory of an up-to-date csound sandbox, added "#include |
Date | 2004-01-06 12:52 |
From | jpff@cs.bath.ac.uk |
Subject | [CSOUND-DEV:3911] Re: csound 4.23 |
>>>>> "John" == John D Ramsdell |
Date | 2004-01-11 01:22 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3919] csound 4.23f09 |
I downloaded Csound_423f09.tar.gz to a Linux laptop, but could not unarchive the file. Here is the message I got: $ tar xzf ~/dist/Csound_423f09.tar.gz 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 $ file Csound_423f09.tar.gz Csound_423f09.tar.gz: gzip compressed data, from Unix $ gunzip Csound_423f09.tar.gz gunzip: Csound_423f09.tar.gz: invalid compressed data--format violated $ There seems to be something wrong the compression step. John |
Date | 2004-01-11 03:59 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [CSOUND-DEV:3921] Re: csound 4.23f09 |
I'll build and release a Csound 4.23f09 GNU Build System tagged as csound-4_23f09gbs_0 if provided with what is needed to incorporate 4.23f9 sources into the csound module. I've update some of the makef files, and I've updated flanger.c, insert.c, and ugrw1.c. I'm not sure what other changes are needed to build an "official" 4.230f09 system. Please enlighten me. John |