Thread: Re: [Audacity-devel] problem compiling on MacOS X
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Ben C. <cro...@li...> - 2002-09-09 02:45:05
|
>It would be useful to see line 163 and maybe 5 lines of context before >and after. Line 163 is this typedef: typedef loff_t sf_count_t ; The full source code of the file is here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/audacity/lib-src/libsndfile/src/sndfile.h?rev=1.2&content-type=text/vnd.viewcvs-markup If you look at the CVS comments, it says: libsndfile fixes so Audacity compiles on Windows. from a few weeks ago. I suspect these modifications broke it. If you look at the code right above where the error is, it has this: #ifdef WIN32 typedef off_t loff_t ; #endif typedef loff_t sf_count_t ; So apparently if you're not on Windows, you're going to get an error...? |
From: Ben C. <cro...@li...> - 2002-09-09 03:56:35
|
>[...] However, ./configure cannot be run (easily) on >Windows. I'm not sure what the best way to solve this is. Don't run Windows? Just kidding :-) Actually, I think it's very very cool to make free software that runs on non-free operating systems -- it's the only way to impress people who aren't already converts. >For now, re-running ./configure in the libsndfile directory will >hopefully give you a valid sndfile.h. Aha! Yep, that seems to be working. I'm speaking from ignorance here, but what about this as a solution: 1. Have a file in CVS called sndfile.h.win. That way nobody will mistake it for something that could be used on Unix. 2. Set up the Windows stuff so it just copies sndfile.h.win to sndfile.h. 3. Set up the Unix Makefile so that it goes into the libsndfile directory and does config, then comes back out and goes ahead with compiling. 4. Fix the CVS setup so it doesn't leave those three subdirectories of lib-src empty when you check out. |
From: Matt B. <mbr...@cs...> - 2002-09-09 17:37:43
|
On Sep 8, Ben Crowell wrote: > 1. Have a file in CVS called sndfile.h.win. That way nobody will mistake > it for something that could be used on Unix. > > 2. Set up the Windows stuff so it just copies sndfile.h.win to > sndfile.h. Yes, we should do this. Among other things, it would help prevent non-Windows developers from accidentally overwriting these files on checkin. > 3. Set up the Unix Makefile so that it goes into the libsndfile > directory and does config, then comes back out and goes ahead > with compiling. ./configure in the top-level directory should configure all of the lib-src directories. However, I think that missing files in your CVS checkout prevented it from detecting some of the subdirs. > 4. Fix the CVS setup so it doesn't leave those three subdirectories > of lib-src empty when you check out. Unfortunately I have no idea what caused that, and we haven't seen it before. If it's not too inconvenient, could you do a fresh cvs checkout into a new working directory, and see if you have the same problems? Check the output of the checkout command to see if it shows any errors. |
From: Ben C. <cro...@li...> - 2002-09-09 04:07:59
|
OK, now I get to the final linking step where it's creating the executable, and then I get this: /usr/bin/ld: can't locate file for: -lsndfile And indeed, I don't seem to have a sndfile.o anywhere. So I guess this means the Makefile at the top level didn't know enough to run the Makefile in the libsndfile directory. When I go down to libsndfile and do make, it runs configure again, creates the Makefile and some other stuff, and then this: ... make all-recursive Making all in GSM610 make[3]: *** No rule to make target `all'. Stop. ... |
From: Ben C. <cro...@li...> - 2002-09-10 04:18:05
|
>> 4. Fix the CVS setup so it doesn't leave those three subdirectories >> of lib-src empty when you check out. >Unfortunately I have no idea what caused that, and we haven't seen it >before. If it's not too inconvenient, could you do a fresh cvs checkout >into a new working directory, and see if you have the same problems? >Check the output of the checkout command to see if it shows any errors Hmm...I did a fresh checkout, and the subdirectories are not empty now! So the good news is that I think something changed in CVS that fixed the problem. The bad news is that something /else/ seems to have changed in CVS, and now I'm getting an error that I /didn't/ get before. When I run ./configure, I get this: checking for Ogg... no *** Could not run Ogg test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means Ogg was incorrectly installed *** or that you have moved Ogg since it was installed. In the latter case, you *** may want to edit the ogg-config script: configure: error: must have Ogg installed! configure: error: /bin/sh './configure' failed for lib-src/libvorbis |
From: Dominic M. <do...@mi...> - 2002-09-17 07:59:09
|
Ben Crowell wrote: > Hmm...I did a fresh checkout, and the subdirectories are not empty now! > So the good news is that I think something changed in CVS that fixed the > problem. The bad news is that something /else/ seems to have changed > in CVS, and now I'm getting an error that I /didn't/ get before. When I > run ./configure, I get this: > > checking for Ogg... no > *** Could not run Ogg test program, checking why... > *** The test program failed to compile or link. See the file config.log for the > *** exact error that occured. This usually means Ogg was incorrectly installed > *** or that you have moved Ogg since it was installed. In the latter case, you > *** may want to edit the ogg-config script: > configure: error: must have Ogg installed! > configure: error: /bin/sh './configure' failed for lib-src/libvorbis What version of Mac OS X are you running, and with which developer tools? I just upgraded to OS X 10.2 with the latest developer tools. Before then I was runnign 10.1.5 with the 10.1 developer tools (NOT the April beta release!). Do you have fink installed? Make sure you're not using the fink version of any packages like cvs or make - use the ones Apple provides... In the meantime you should be able to get around the Ogg problem using ./configure --without-vorbis. See ./configure --help for other options you may need to turn off. - Dominic |
From: Ben C. <cro...@li...> - 2002-09-18 03:12:12
|
Dominic, thanks for the suggestions. I don't have fink installed. >What version of Mac OS X are you running, and with which developer >tools? I just upgraded to OS X 10.2 with the latest developer tools. >Before then I was runnign 10.1.5 with the 10.1 developer tools (NOT the >April beta release!). . I'm running 10.1.5. I hope it doesn't make any difference whether I'm using 10.1.5 or 10.2. I guess that's the problem with trying to write free software on a non-free OS -- it would cost me another $130 to upgrade to 10.2, which I don't really want to spend. >In the meantime you should be able to get around the Ogg problem using >./configure --without-vorbis. See ./configure --help for other options >you may need to turn off. Hmm... well, the reason I'm trying to recompile is to fix the bug that makes it truncate ogg files, so I don't want to recompile with ogg support turned off. Since you have a MacOS X system yourself, do you think you could compile a version from CVS and let me serve it up from my own web site? That way it wouldn't be using up your server's resources, and it wouldn't be an official release, but people who need the bug fixes could get the new version from me. |
From: Dominic M. <do...@mi...> - 2002-09-18 06:55:32
|
Ben, I wish I knew what was going wrong with CVS. It sounds like many of your problems might be caused by broken directories. > Hmm... well, the reason I'm trying to recompile is to fix the bug that > makes > it truncate ogg files, so I don't want to recompile with ogg support > turned off. This was already fixed in CVS, right? So any new build should have this fix... > Since you have a MacOS X system yourself, do you think you could > compile > a version from CVS and let me serve it up from my own web site? That > way it > wouldn't be using up your server's resources, and it wouldn't be an > official > release, but people who need the bug fixes could get the new version > from me. OK, I just uploaded a snapshot: spaghetticode.org/audacity-macosx-1.1.0b.dmg.gz The main reason I don't release more often is that it takes a while. This release has some regressions from version 1.1.0, and I haven't rounded up all of the wxWindows locale files. The other problem is support: it's a pain to try to support lots of different versions. But there are some new features: the new directory searching code works and allows the Audacity directory to be organized better. The Preferences menu item is now in the right place. And all of the other new features and bug fixes should be there... I'm happy for you to try out this snapshot and make it available unofficially. Hopefully you can figure out the CVS problems before too long and then you can build snapshots yourself. BTW, I understand about the price being an issue, but I must say I love Jaguar - it's faster and quite an improvement all around. Lots of subtle new features. Hopefully you'll be able to upgrade before too long. - Dominic |
From: Ben C. <cro...@li...> - 2002-09-23 02:30:55
|
Hi Dominic, Thanks a lot for making the new snapshot available. Unfortunately, I can't get it to work -- the input gain on the mic is suddenly way too low. I'm going to try using Audacity on Linux instead. I didn't want to e-mail you just as punishment for your good deed :-), but I thought you might want to know about this gain problem for when you make the next release. Ben On Tue, 17 Sep 2002 23:55:12 -0700 Dominic Mazzoni <do...@mi...> wrote: > Ben, > > I wish I knew what was going wrong with CVS. It sounds like many of > your problems might be caused by broken directories. > > > Hmm... well, the reason I'm trying to recompile is to fix the bug that > > makes > > it truncate ogg files, so I don't want to recompile with ogg support > > turned off. > > This was already fixed in CVS, right? So any new build should have this > fix... > > > Since you have a MacOS X system yourself, do you think you could > > compile > > a version from CVS and let me serve it up from my own web site? That > > way it > > wouldn't be using up your server's resources, and it wouldn't be an > > official > > release, but people who need the bug fixes could get the new version > > from me. > > OK, I just uploaded a snapshot: > > spaghetticode.org/audacity-macosx-1.1.0b.dmg.gz > > The main reason I don't release more often is that it takes a while. > This release has some regressions from version 1.1.0, and I haven't > rounded up all of the wxWindows locale files. The other problem is > support: it's a pain to try to support lots of different versions. > > But there are some new features: the new directory searching code > works and allows the Audacity directory to be organized better. > The Preferences menu item is now in the right place. And all of > the other new features and bug fixes should be there... > > I'm happy for you to try out this snapshot and make it available > unofficially. Hopefully you can figure out the CVS problems before > too long and then you can build snapshots yourself. > > BTW, I understand about the price being an issue, but I must say > I love Jaguar - it's faster and quite an improvement all around. > Lots of subtle new features. Hopefully you'll be able to upgrade > before too long. > > - Dominic > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: AMD - Your access to the experts > on Hammer Technology! Open Source & Linux Developers, register now > for the AMD Developer Symposium. Code: EX8664 > http://www.developwithamd.com/developerlab > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Dominic M. <do...@mi...> - 2002-09-26 07:01:23
|
Ben Crowell wrote: > Hi Dominic, > > Thanks a lot for making the new snapshot available. Unfortunately, > I can't get it to work -- the input gain on the mic is suddenly way too low. > I'm going to try using Audacity on Linux instead. I didn't want to e-mail > you just as punishment for your good deed :-), but I thought you might > want to know about this gain problem for when you make the next > release. I didn't change anything...any chance you can adjust it using the Input tab in the Sound system preferences? - Dominic |
From: Ben C. <cro...@li...> - 2002-09-27 17:18:28
|
> Thanks a lot for making the new snapshot available. Unfortunately, > I can't get it to work -- the input gain on the mic is suddenly way too low. > I'm going to try using Audacity on Linux instead. I didn't want to e-mail > you just as punishment for your good deed :-), but I thought you might > want to know about this gain problem for when you make the next > release. >I didn't change anything...any chance you can adjust it using the >Input tab in the Sound system preferences? My Sound system prefs only has tabs for Alerts and Output. Is this a new thing in 10.2? I'm upgrading soon... Ben |
From: Dominic M. <do...@mi...> - 2002-09-28 03:16:25
|
Ben Crowell wrote: >>Thanks a lot for making the new snapshot available. Unfortunately, >>I can't get it to work -- the input gain on the mic is suddenly way too low. >>I'm going to try using Audacity on Linux instead. I didn't want to e-mail >>you just as punishment for your good deed :-), but I thought you might >>want to know about this gain problem for when you make the next >>release. > > >>I didn't change anything...any chance you can adjust it using the >>Input tab in the Sound system preferences? > > > My Sound system prefs only has tabs for Alerts and Output. Is this a new thing > in 10.2? I'm upgrading soon... Maybe so! Also, try checking in the "Speech" tab...I can't remember if there was something there... > Ben > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Joshua H. <jha...@up...> - 2002-09-09 03:36:25
|
* Ben Crowell (cro...@li...) wrote: > >It would be useful to see line 163 and maybe 5 lines of context before > >and after. > > Line 163 is this typedef: > > typedef loff_t sf_count_t ; > > The full source code of the file is here: > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/audacity/lib-src/libsndfile/src/sndfile.h?rev=1.2&content-type=text/vnd.viewcvs-markup This file should not be in CVS -- it is generated at configuration time from sndfile.h.in. However, ./configure cannot be run (easily) on Windows. I'm not sure what the best way to solve this is. For now, re-running ./configure in the libsndfile directory will hopefully give you a valid sndfile.h. Josh -- Joshua Haberman <jo...@ha...> |