/usr/local/libexec/Audacity: No such file or directory.

[unixland]

O/S: FreeBSD 8.1-STABLE amd64
Audacity version: 1.3.12

After compiling and installing audacity I get the following message when I start the program:

Code: Select all

[email protected]:/data/home/unix$ audacity
/usr/local/libexec/Audacity: No such file or directory.
Killed: 9
[email protected]:/data/home/unix$ LibGTop-Server: pid 1872 received eof.

[email protected]:/data/home/unix$ 

Anyone knows what is wrong ? (I do get it that it is missing a file, but why does it need this one? audacity is already there: /usr/local/bin/audacity)

Any help would be appreciated.

Rick

[Gale Andrews]

To begin with try make uninstall then run Audacity from the directory you built it in. Does it launch then?

Where did you install Audacity to? Did you specify something other than default?

Also please post to the correct Forum for the version of Audacity you are using. You posted in 1.2.x, moved to the 1.3.x Forum.


Gale

[unixland]

To begin with try make uninstall then run Audacity from the directory you built it in. Does it launch then?

Where did you install Audacity to? Did you specify something other than default?

Also please post to the correct Forum for the version of Audacity you are using. You posted in 1.2.x, moved to the 1.3.x Forum.


Gale

Hi Gale,

No, when I launch from within the source after deinstalling audacity, I do get the same error:

Code: Select all

[email protected]:/usr/ports/audio/audacity-devel/work/audacity-src-1.3.12-beta$ ./audacity 
/usr/local/libexec/Audacity: No such file or directory.
Killed: 9
[email protected]:/usr/ports/audio/audacity-devel/work/audacity-src-1.3.12-beta$

What I don't understand is that the main program seems to want to run another program which it thinks is located at /usr/local/libexec. Why is that ?

[bgravato]

Are there ppl still using FreeBSD? And using it for desktop? And running Audacity on it? I must confess I'm very surprised I wonder if anyone has tried before to run Audacity on FreeBSD

My knowledge of FreeBSD is very limited, but could it be related to the configure script? Some default paths in FreeBSD might not be quite
the same as in Linux... Could be some other *bsd related issue...

[unixland]

Are there ppl still using FreeBSD? And using it for desktop? And running Audacity on it? I must confess I'm very surprised I wonder if anyone has tried before to run Audacity on FreeBSD

My knowledge of FreeBSD is very limited, but could it be related to the configure script? Some default paths in FreeBSD might not be quite
the same as in Linux... Could be some other *bsd related issue...

hehe, there are many many FreeBSD users out there, and even if FreeBSD might not be ideal for using it as a Desktop (since you have to compile everything, and yes, there are always compatibility issues, etc.), it is known to be a very stable O/S. I suppose that's the reason Apple chose FreeBSD to base their OSX on in the first place...

In the past the older version of Audacity used to run perfectly on FreeBSD. The newer 1.2.x versions however do have a screen issue on FreeBSD which led me to try out the development version, 1.3.x. This is why I am here...

Yes, it could be something in the configure script.
However, looking at the sources, when it is compiled [not yet installed], there is no executable with the name "Audacity", only an executable with the name "audacity". When installed, I see no file appearing somewhere with the name "Audacity".
So, either we're missing something at compile time, or something is wrong in the code. Either way, if anyone has a clue how to resolve, it would be much appreciated.

Rick

[unixland]

I figured it out.

It seems I compiled with debug option on. I recompiled without the debug option on and now it works.

I have the same screen problem however. will open a new topic on that, since it is quite annoying.

Thanks,

Rick

[bgravato]

it is known to be a very stable O/S.

I remember That's what impressed me most in my brief freebsd experience... Even after running out of disk space and a lot of error messages on the console the system still running smoothly. The stability of the tcp/ip stack also impressed me... That was maybe 10 years ago

I'm getting a bit nostalgic I think I'll try to find a virtualbox image of a freebsd and try to compile audacity on it, just for the fun of it Not sure if I'll have any free time before next week though...

[bgravato]

I figured it out.

It seems I compiled with debug option on. I recompiled without the debug option on and now it works.

I have the same screen problem however. will open a new topic on that, since it is quite annoying.

Thanks,

Rick

Oops! Only reading this after my previous post... I guess I'll have to find another excuse to get me back into freebsd hehe

[Gale Andrews]

I figured it out. It seems I compiled with debug option on. I recompiled without the debug option on and now it works.

Does that directory /usr/local/libexec/ actually exist on BSD as the executables dir like /usr/local/bin does on Linux?

When you configured as (I presume) default Unicode Release instead of Debug, was the Audacity executable created still "audacity" lower case, and was it inside a "/usr/local/libexec/audacity" folder?

I have the same screen problem however. will open a new topic on that, since it is quite annoying.

I've given a possible answer here.



Gale