Are you anxiously awaiting the upcoming release of Ubuntu Studio but crave a taste of the bleeding edge, today? We were inspired to create this tutorial after reading several complaints about the current state of Audacity 1.2.6
We will admit, in comparison to its closest proprietary counterpart, the classic Cool Edit Pro, the currently released version of Audacity doesn’t quite make the grade. Strangely, a vastly improved version has been in development for well over a year. To make a long story short, Audacity 1.3.2 greatly decreases the gap between Audacity and Cool Edit Pro.
Need some more convincing? Take a quick peek at the generous list of new features. Don’t worry, unlike many “new feature” lists in the Linux community, there are plenty of screenshots!
Getting down to the nitty gritty
You do not need to uninstall your current installation of Audacity. First things first, go ahead and download the Audacity 1.3.2 source code to your Desktop (right click > save as will not work) :
/beta/audacity-src/audacity-src-1.3.2.tar.gz
From the desktop, right click the file (its called a tarball, similar to a zip) and select ‘Extract Here’. This will place a new folder on your desktop by the same name. Inside are all the necessary files needed to compile.
Let’s get this party started! Open the Terminal and change into the directory you just extracted :
cd Desktop/audacity-src-1.3.2
Before we start we need to install a few packages that are required to compile. It’s possible you already have one or more of the following dependencies on your machine. Either way, It wont hurt to run the next line just to be sure :
sudo apt-get install build-essential libwxgtk2.6-0 libmad0 libsndfile1 libwxgtk2.6-dev gettext
Now that all your dependencies are met, you are ready to begin compiling Audacity 1.3.2. The next commands will ‘configure’ a ‘make file’ which will be used afterwards to install the actual program. Kind of like the setup.exe of the olden days.
In the next step, –program-suffix=beta tells ./configure to add a suffix of ‘beta’ to all the program file names, as to not interfere with any previous Audacity installs. The next step could take 5-10 minutes to finish. Don’t watch water boil, go surf the web and check back. (If you do decide to watch the water boil, don’t be alarmed if you see ‘warning’ messages. Ignore them. It’s errors you need to watch out for)
./configure --program-suffix=beta && make
If you made it this far without any errors you have just successfully configured a make file! Now its time install the program :
sudo make install
Still there? Congratulations! You have just compiled and installed Audacity 1.3.2 onto your machine! Now its time run it :
audacitybeta
Alternatively, you can make a shortcut. Right click on the desktop and go to ‘Create Launcher’. Name it Audacity 1.3.2 Beta. In the ‘Command’ field browse to /usr/local/bin/ and select audacitybeta. Use the ‘Comments’ field to write a short description of how you use Audacity.
You’re all set! One final note, the folder on your desktop is not where Audacity is installed. But don’t delete it! Move it somewhere safe like your Home folder. You’ll find out why in bit.
What!? No fancy icon?
We thought you might notice that! Luckily we found a stunning Audacity icon over at the always entertaining, Acts of Volition. Luckily for our eyes, the icon was created with the Tango icon guidelines in mind. You can add the icon by editing the properties of your audacitybeta Launcher
How do I uninstall?
Open the Terminal and change directories to the folder we told you not to delete :
cd audacity-src-1.3.2
This will only work If you moved said folder to Home for safe keeping. If you moved it elsewhere, or if it’s still on your Desktop, you will need point to the appropriate location. Now, issue the uninstall command:
sudo make uninstall
Piece of cake. Audacity 1.3.2 beta has been completely removed from your computer.
How can I learn more about compiling?
We’re glad you asked. Here’s the first step of your journey :
./configure --help
What results is a list of options that can be set into the program. Let’s say you wanted to include built-in Ogg Vorbis support :
./configure --with-vorbis && make
Which would then of course be followed by sudo make install. We hope you take advantage of the suffix modifier you learned earler. This enables you to test several different compiles : audacityvorbis, audacitybeta2, etc.
Bugger! After being on Audacity for two years on Win XP when I switched to Ubuntu I was tearing my few hairs out over its installation on Dapper/Edgy and then Feisty.But at 2am this morning — April 22, the same day as your post here — I succeeded! by doing some funny things with Lame files and my “export as” file names. (I could find no solution from the forums either Ubuntu or Audacity housed)Now you suggest I should uninstall my sweated over effort and install the new version!… Which is still in beta!
OK. Tell me this: how is the the lame issue covered in this version because it sure suffered big time on Ubuntu before as far as I can make out where Audacity demanded Lame files that could not be found. So does this release INCLUDE LAME or do I have to go through all the same rigmarole? Your installation procedure offered here does not refer to that issue at all.
Hi Dave Riley! Do not uninstall your previous version of Audacity.
We did originally tell you to do so, but we realized that was kinda silly, so within 15 minutes we updated the tutorial so that you do not have to uninstall the “stable” version of Audacity. You just happened to catch the article in that 15min window!
Please re-read the tutorial as you can now compile as many test versions of Audacity as you like without any conflicts
Here’s how to install LAME (this works for the stable and beta versions) First download the source :
1) http://internap.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz
2) Right click and Extract the folder to your Desktop
3) Open the Terminal and type :
4)
./configure --prefix=$HOME/local && make && make installYou should be set for life. I know its seems strange that you have to do so much (well, one download and one line of code) just to get Mp3 encoding/decoding. But, as you know, Audacity and Ubuntu are opensource and therefore cannot (and probably will never) include support for any propreitary formats (such as Mp3) out of the box. Luckily computers have users to groom them into perfection
Well that’s fine. After so much searching I get the good oil.. and will do the install for the new version of Audacity and maybe — maybe! — I get to deal with my chronic Lame issues.
To install and use Lame on Audacity (stable) before I had to rename the closest in function Lame folder and then because of “export as” issues, had to export files without full names — I had to use names with out descriptions –such as ” .mp3″ and ” .wav”.– to export and then rewrite the name after they were exported as/saved as. “Project” save worked fine though.
I was also disappointed in how small the dB window window was on Audacity on Ubuntu– so I guess I should, if that remains an issue for me, use another dB monitor.
But thanks so much for the post here — it is most valuable,
No problem, we are here to help!
We should mention that this installation method will place libmp3lame.so inside /home/yourusername/local/lib
Or (for anyone else who’s reading), your “Home Folder” then click on /local, then click on /lib
As per the level meters : In Audacity 1.3.2 (beta) you can detach the levels meter and resize it as big as the screen itself if you want! You can also keep it docked in the toolbar and resize it horizontally all the way across the screen. I’m telling you, the beta is 100% badassery.
Well, actually you can detach and resize in the current version but you cannot resize while docked… Also all of the toolbars in the new beta are completely reconfigurable.. you can place the transport at the bottom, etc etc… GTK2 my friend!
We also want to comment right quick on the improved audio support of this beta release. We have an M-Audio Delta 44 sound card on one of our older computers that we just could not get Audacity 1.2.6 to record from. In fact, we couldnt even select our card from the “list” of audio devices.
This all changes in 1.32. Not only could we select the M-audio sound card, there is also a new toolbar which allows you to switch between ALL your installed sound capture/sound playback devices on the fly!
Very impressive!
Sorry about this folks. But you write:
(1)Download Audacity to the Desktop
That’s fine. Even I can do that!
Then you write:
(2)”right click the file”
But when I right click I get offered a few “open with” options & none of them take up the .tar tarball zip unpack and I’m not offered an “Extract Here” option.
So where’s the muck up?
I guess you mean open with Archive Manager. But I get:
A error occurred whil loading the archive.
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors
So I can’t proceed, at least via that route.
You didn’t by chance rename it from .tar.gz to .tar? Very strange. What build of Ubuntu are you running? Perhaps your download hiccup’d? Maybe try to redownload (We’re sure you have already)
This error is kinda twilight zone-ish, Dave
FWIW, the “Extract Here” option is just a quick way of opening the Archive Manager and extracting, so yes, Archive Manager is the tool you need.
I hate to be a pain but I downloaded again, Opened the file on desktop with Archive Manager. I then get another file: audacity-src-1.3.2.tar.gz.tar.gz.
but if I click on that I am offered an “Extract Here” option which only gives the original file name plus (2)
But when I try any number of “CD” and file location combinations in Teminal I get
bash: cd/ratbagradio/Desktop/audacity-src-1.3.2: No such file or directory
or for your line:
cd /Desktop/audacity-src-1.3.2
bash: cd: /Desktop/audacity-src-1.3.2: No such file or directory
So I’m doing something very wrong or am missing something. Is there another way to do this?
Aha! We figured it out! SourceForge (where the source is located) does some weird file redirecting, so if you tried to right click > save as the link from our article… you actually ended up downloading a SourceForge webpage rather than the actual file. So left click on the link and let SourceForge do its insta-downloading magic.
http://superb-west.dl.sourceforge.net/sourceforge/audacity/audacity-src-1.3.2.tar.gz
Unfortunately, despite following the new directions, in Terminal I am still getting : cd: /Desktop/audacity-src-1.3.2: No such file or directory despite the various combinations I try.Terminal refuses to recognise the file.
Aha! You are keeping us honest Dave! This one is our fault again. Remove the first ‘/‘ before Desktop… that was the problem. (updated in tutorial)
Here’s a terminal secret :
if you type cd then Des and then press the TAB key, the Terminal will autofill the rest of ‘Desktop’ then press / and type aud and press the TAB key… it will autofill in ‘audacity-src-1.3.2′
Thanks for the guide! I’m glad it seems to have helped so many people. However, I’m experiencing failure early in the compiling process. When I run “./configure –program-suffix=beta && make,” I see a message that ends with “configure: error: C++ preprocessor “/lib/cpp” fails sanity check.” I checked, and found that cpp is indeed installed on my computer. Any ideas?
Joe Silver:
Yikes! Ok, for now on we’ll test all of our tutorials on a base install of Feisty! We promise!
The first thing youll need to do is download the build-essential package… this package comes with lots of stuff that makes compiling certain programs possible. Just type :
sudo apt-get install build-essential
We personally installed build-essential back during the Dapper Drake days and have since updated with each new release …. so, there’s lots of stuff on our box that isnt installed by default!
So, yes, we’ll double check everything on clean installs (well this was always the plan, but since ubuntu studio hasnt come out yet…) for now on. Thanks everyone! (tutorial updated)
Hi. Thanks ubustu!
Followed that howto exactly. Found I also had to apt-get install libwxgtk2.6-dev to get it to configure properly.
Also, the version I’m left with has no support for ALSA, or my USB soundcard (tascam US 122). How would u configure it for that support?
Thank you for your prompt response, and for the tip about build-essential. I installed it, and got a little farther this time. However, now I see an error that reads “Could not find wx-config: is wxWindows installed? is wx-config in your path?”
I looked in Synaptic for both wx-config and wxWindows, without success. I also tried “sudo apt-get install wx-config” and “sudo apt-get install wxWindows,” but no luck.
i believe you need the package that Mr Dewin mentioned in the comment above :
sudo apt get install libwxgtk2.6-dev
Sorry for all the confusion! The problem was that we had already installed these dependencies for other compiles a long time ago! Once Ubuntu Studio releases we’ll have a clean default install to make sure this never happens again
(tutorial updated)
Hi Joe,
You need to install libwxgtk2.6-dev as well. This includes all the config file and header files required to compile.
Cheers.
I’ve had to also install gettext. My base installation of Feisty had gettext-base but not gettext.
Cheers.
I truly appreciate all the help. However, I have a real challenge for you this time: Now that I apparently have all the required dependencies, I’ve tried repeatedly to compile Audacity, but my computer freezes in mid-compile every time. This reminded me that I had a similar problem a while ago while trying to compile another program, but just decided (grudgingly) that I could live without that particular app.
Although I am willing to make compromises in order to work with Linux (and have done so in numerous instances), I’m afraid that if I can’t get Audacity 1.3.2 compiled and running on my machine, it might be time for me to abandon the Linux experiment and return to [a certain widely-reviled commercial OS, the very mention of the name of which frequently raises the ire of Linux advocates]!
By the way, I’m using the AMD64 version of Ubuntu, on a computer with a AMD Athlon 64 X2 4400+ processor, and 2GB RAM. I would think that my hardware should be more than sufficient. Is there some other command I need to run in order to accommodate the 64-bit OS and processor? Should I perhaps switch to 32-bit Ubuntu?
Again, thanks!
I get this error when trying to add a second track. It does not happen in stable version. Any idea on what to do?
Error while opening sound device. Please check the input device settings and the project sample rate.
Joe Silver : We’re not 100% sure but we think it probably has something to do with the fact that you’re actually running the i686 version of Ubuntu.
We have an AMD64 as well, but prefer to run i386 until 64-bit Ubuntu (or 64 bit any-OS) has more widespread support
We’ve got a feeling the Audacity team is worried about getting the i386 version nice and polished before they get to work on the i686 bit version
Ubuntu Studio will only be released as i386 at first, tho during the quesiton/answer session yesterday they did say a i686 version is planned… Don’t give up and go back to WinBlows just because of this! NOBODY has very good 64-bit support at this time
So yes, when Ubuntu Studio releases, I would suggest switching to the i386 version of Ubuntu. Anyone running anything 64-bit at the moment is sorta testing the waters for the future of computing!
tb: its hard to say without actually sitting down at your computer, but from the sounds of it, you may need to go to preferences and make sure your video card is selected and the proper settings are setup…
The audio devices prefences window has been majorly updated and overhauled in 1.3.2
So either go to Edit > Prefences, or press Ctrl-P, and see if you can figure out whats going on (or simply just trial and error until you get it right)
Of course, it is a beta… you may just happen to have a device (not necessarily your sound card, it could be any component of your computer) that doesn’t play well with 1.3.2
But we’re confident the Prefences window will help you on your way.
What kind of sound card do you have? You can set the sample rate at the bottom left hand corner of the screen. Most generic cards default to 41000, but even cheap cards like certain old SoundBlaster cards defaulted to 48000, and high end cards can go as high as 96000 (probably even higher these days)
Read up on your card via google and see whats what
Let us know what you find out of course!
Also, what exactly do you do to cause this error? Simply going to Tracks > Add New > Audio Track? Or are you importing a soundfile into the session or what?
>Also, what exactly do you do to cause this error?
>Simply going to Tracks > Add New > Audio Track?
>Or are you importing a soundfile into the session or
>what?
It happens while the program is being compiled - while all the verbiage is appearing in the terminal window. It seems to occur at random points, rather than at a specific step in the compiling process. There’s no way to escape except to press the reset button on my computer.
Anyway…I was excited that you confirmed my suspicion that Ubuntu AMD64 is not exactly a finished product. I backed up the important files in my Home directory, formatted my Root partition, and proceeded to install Ubuntu i386. I then started running through your steps again, hopeful that it was going to work this time…and again my computer froze while the program was compiling. ARRRGHHH!!
While I’m a bit frustrated that a) I just reinstalled my OS apparently for nothing, and b) I might never be able to use Audacity 1.3.2 in Ubuntu, I want to make it clear that I really do appreciate your sympathy and prompt attention to my situation, as well as your use of clear, standard English in your responses (not all that common in the Linux world, in my experience!).
One note, though: While I can fully understand why people prefer the “community” approach of Ubuntu and other Linux distros to the “corporate” approach of software corporations like Microsoft, I really don’t like it when people gratuitously call Windows “Winblows.” Windows 2000 worked nearly flawlessly for me.
Yes, that’s right: I said “Windows 2000 worked nearly flawlessly for me.”
Unfortunately, so far I can’t say the same for Ubuntu. It has a lot of potential, and I’m sure it’ll be great when it’s finished, but for now I just want to get some work done, and I think I need to choose the path of least resistance in order to do so.
Joe Silver: We do not want to insult your intelligence, but we want to make extra sure that your computer is stone-cold freezing and not just hanging for a while at certain compile points. We do recall that there are a few long pauses during the process (but there is a visual notification that the ‘terminal’ is thinking via the rectangle cursor blinking on and off)
We also meant no harm with our slanderous Windows comments. We’ve been PC users since ‘nibbles.bas’ was the most entertaining thing you could do. 2K was amazingly stable. XP is impressively stable! We must admit our dedication to Ubuntu and Open Source is less for “cool free software” and more for the philosophical underpinning of an Open Society.
That being said, we do sympathize with your struggles, and asbolutely cringed after we read it didn’t work after a complete OS reinstall. We do wish we could drop by for a beer and sit down at your box and see for ourselves.
We do have a final suggestion however
You may not be aware, but there are several different workspaces under Ubuntu.
Ctrl + Alt + F7 is the graphical interface workspace (where you are reading this now if you havent thrown your Ubuntu install off a cliff)
However, by pressing Ctrl + Alt + F2 (or F1, F3, etc… lets just stick with F2) you can switch to what looks like an old DOS prompt.
Try it now : press Ctrl + Alt + F2, look around at the DOS-like envrioment, then press Ctrl + Alt + F7 to come back to the Gnome GUI… pretty slick eh?
We suggest you try compiling the program from one of these textual workspaces. Write down the last few commands you need (make sure you re-try to download the dependecies as we’ve had to update them several times) and give it a go. Just switch to F2, login, and you’re basically at the terminal screen.
After you type in the ./compile… commands, go do something thats gonna take 30 minutes. Promise us not to watch the screen! Even if you computer is potentially frozen for the entire time, just promise! after you press enter walk away for 20-30 minutes
Many times when things do not work in the GUI workspace, they will work in the textual workspace. Maybe its still worth a try for you? It is very very unusual for linux to just freeze without simply writing an error.log of some sort and shutting down the offending process. Good luck either way our friend
I didn’t previously know about Ctrl + Alt + F2. Great tip; thanks! Prior to this I had tried compiling Audacity from GNOME Terminal, and from a failsafe terminal login. In both scenarios my computer was truly frozen - no blinking cursor, nothing.
This time, with Ctrl + Alt + F2, things looked good for a while. The verbiage did pause, but the cursor continued to blink. I left my computer alone for more than 35 minutes. When I returned, the text on the screen looked exactly the same, although the cursor was still blinking. Ctrl + Alt + Del didn’t do anythng; nor did Ctrl + Alt + F7. Again, all I could do was push the reset button.
In my previous attempts to find a solution to this problem, I did run across a Debian package for Audacity 1.3.2, but it wouldn’t install in Ubuntu AMD64. Now that I’m running the i386 version, I’m going to try to find and install the Audacity Debian package again. I’ll leave further attempts at compiling for another time.
I must say again that you folks have been extremely helpful and friendly. When I encounter this sort of attitude, it helps renew my faith in the open source community and give me the patience to keep trying and not to give up on Linux altogether. Sorry if my previous message seemed a little testy, or if I overreacted a bit to the “WinBlows” comment.
No problem, Joe. Remember too that Audacity 1.3.x has been in development for almost 18 months. The stable release has to be just around the corner! Then you’ll be able to sanely and safely install it from Synaptic. Dual-booting is your friend. Don’t give up on us just yet
We know it doesn’t exactly help you much, but we also want to emphasize that a stone-cold freeze is a very unsual thing to happen in Ubuntu. We’ve been using it since Dapper Drake, and tho we’ve definitely had individual programs freeze up, we’ve never had to resort to a forced reboot. Those fancy features in W2K and XP that allowed the OS to continue working even tho a certain program had failed have long been staples in the Linux world.
We suggest you get a 5gb partition ready for Ubuntu Studio and do a truely clean i386 install (you can always browse your old partitions for bookmarks etc)… if not for full-time consistent use at least for tinkerings sake!
When I try to open a FLAC file, I get a message that says, “This version of Audacity was not compiled with FLAC support.” Is there a way to fix this?
Also, I followed the directions to install LAME support, and it didn’t work.
To get full support for OGG, FLAC, and MP3 (with id3 tag support), you also need to install the following development libraries:
sudo apt-get install libmad0-dev libvorbis-dev libogg-dev libflac-dev libflac++-dev libid3tag0-dev zlib1g-dev
which will also install any necessary dependencies. Also, you really don’t need to mess with command line options with ./configure, as support for these features will be enabled by default if the necessary libraries are present.
I just compiled Audacity 1.3.3(Fiesty i386) from source .Here is the complete listing of all the required packages :
{ libwxbase2.6-dev libwxgtk2.6-dev wx2.6-headers libmad0-dev libvorbis-dev libogg-dev libflac-dev libflac++-dev libid3tag0-dev zlib1g-dev libtwolame0 libtwolame-dev libgtk-dev libwxgtk-dev twolame libasound2-dev libjack0.100.0-dev portaudio19-dev libgtk2.0-dev }
I configured it with the following :
{ ./configure –program-suffix=beta –with-vorbis –with-libmad –with-flac –with-id3tag }
the compiling went smooth as silk and I now have v1.3.3-beta up and running here. Great! .This was just FYI.
For those who do not wish to compile lame can download it from the repository(multiverse)
and then select /usr/lib/libmp3lame.so.0.0.0 from edit>preferences>File Formats.
ubustu:Instead of pointing directly to files in sourceforge.net ,point them to the download
page and let sf.net choose the mirror since some mirrors do not accept direct links to download.
just compiled Audacity 1.3.2 following your instructions. Thank you have now got functioning program with full selection of input.
First prog I have compiled for linux (ubuntu fiesty)
thanks also Zeus77 did it your way
thanks again
philj
This is such a fantastically useful thread.
Thanks so much for your patient explanations everyone. I can’t undurstand howeve, what to do when ./configure says:
configure: Vorbis libraries are available as system libraries
configure: Vorbis libraries are NOT available in this source tree
even though I did sudo apt-get install libvorbis-dev etc as ubuwiki did above.
Is there some conflict between Synaptic and conmmand-line apt-get perhaps?
I now notice several other libraries are seemingly available as system libraries and not in the source tree. For example:
configure: Expat libraries are available as system libraries
checking for ./lib-src/expat/xmlparse/xmlparse.h… yes
configure: Expat libraries are available in the local tree
checking for ./lib-src/twolame/libtwolame/twolame.h… no
configure: libtwolame library is NOT available in the local tree
configure: Figuring out what libraries to enable
configure: error: I didn’t understand the argument yes for LIBVORBIS
What do I need to do to resolve these as I have all the libraries on my box by now.
Do I need to make a symboliclink perhaps … if so from where to where … do others get these configure failuers too?
I installed audacity-src-1.3.3-beta on Ubuntu Feisty 7.04 i686, and the installation process worked well.
Audacity homepage http://audacity.sourceforge.net/download/beta_source states that if you should install optional libraries using a package management system like Apt or RPM, make sure to install the “dev” (development) packages for each library.
So, I installed dev packages as well as the newer versions of some packages, such as libwxgtk2.8-dev, suggested in the previous instructions. (Some of the packages might be redundant.)
This installation process worked for me:
1) download audacity-src-1.3.3-beta at http://audacity.sourceforge.net/beta/audacity-src/audacity-src-1.3.3.tar.gz on your desktop
2) extract the tarball on your Desktop
3) cd Desktop/audacity-src-1.3.3-beta
4) sudo apt-get install build-essential libwxgtk2.8-0 libwxgtk2.8-dev libmad0 libmad0-dev libsndfile1 libsndfile1-dev gettext libwxbase2.6-dev libwxgtk2.6-dev wx2.6-headers libmad0-dev libvorbis-dev libogg-dev libflac-dev libflac++-dev libid3tag0-dev zlib1g-dev libtwolame0 libtwolame-dev libgtk-dev libwxgtk-dev twolame libasound2-dev libjack0.100.0-dev portaudio19-dev libgtk2.0-dev
5)./configure –program-suffix=beta && make
6) sudo make install
7) audacitybeta
I’m not sure if this is related, nor am I sure if you can help me. I’m desperate and you seem wise so I am reaching for you…
I’m an absolute newbie at Ubuntu. I switched specifically BECAUSE Windows XP had given up on cooperating, and I needed to use it specifically for audacity. I followed your directions and successfully got the beta version running. However, I did it so that I could use my samson mic to record multiple tracks of audio. In the audacity wiki it gives directions to use portaudio to achieve ALSA support in Audacity 1.3.2 Beta. I followed their directions after yours; but to no avail. It does not give me the option in Preferences of using an ASLA device. I experimented with many commands and directories. I think most of the problem is that I do not really understand the problem, the instructions, or the solution. Can you help me get through?
It is recording using the mic, but it is not calling it an ALSA device, and it won’t record multiple tracks while playing others.
hello
i just tried to install audacity 1.3.3 beta, following janM´s method, and got the following error messages during compile:
cc1plus: error: unrecognized command line option “-msse”
make[4]: *** [AAFilter.lo] Error 1
make[4]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch/source/SoundTouch’
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch/source’
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src/soundtouch’
make[1]: *** [soundtouch-recursive] Error 2
make[1]: Leaving directory `/home/jason/Desktop/audacity-src-1.3.3-beta/lib-src’
make: *** [audacity] Error 2
does anyone know what could be wrong here?
thanks in advance for any help!