Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 716 - Modules don't build on Linux
Modules don't build on Linux
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Other
unspecified
PC Linux
: P4 Repeatable
Assigned To: Default Assignee for New Bugs
http://sourceforge.net/p/audacity/mai...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-31 18:53 UTC by Steve Daulton
Modified: 2018-08-20 11:51 UTC (History)
6 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
stevethefiddle: Regression+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Daulton 2014-03-31 18:53:50 UTC
Modules fail to build on Linux.

The problem is partly fixed for Nyquist Workbench (see URL link), though Nyquist Workbench still does not work.

The build failure for mod-script-pipe appears to be similar to the original issue in mod-nyq-bench.

Both mod-script-pipe and mod-nyq-bench work in r12860 but not in r12861.
Comment 1 Steve Daulton 2014-04-08 10:35:02 UTC
(In reply to comment #0)
Error in original post. The revision numbers are incorrect, I think it should have been r12960. Checking that now.
Comment 2 Steve Daulton 2014-04-08 11:22:25 UTC
(In reply to comment #1)
Both mod-script-pipe and mod-nyq-bench build on r12959.

I've only tested Nyquist Workbench and that works as expected.
Comment 3 Steve Daulton 2014-04-09 05:55:29 UTC
Update to test builds:

r12959
Audacity: build successful.
mod script pipe: build successful
Nyuist workbench: build successful and works as expected.


r12960
Audacity: build fails.
Modules not tested.


r12960
Audacity: build successful.
mod script pipe: build fails
Nyuist workbench: build fails


r13011
Audacity: build successful.
mod script pipe: build fails
Nyuist workbench: build successful but module fails to load 

(As discussed in the URL, the error reported in the log is:
Error: /home/steve/.audacity-files/modules/mod-nyq-bench.so: undefined symbol: gAudioIO)


r13090
Audacity: build successful.
mod script pipe: build fails
Nyuist workbench: build successful but module fails to load (same error message as for r13011).
Comment 4 Steve Daulton 2014-04-09 05:57:25 UTC
(In reply to comment #3)
Rats, why can't these posts be previewed :(


The second listing for r12960 should have been r12961

r12961
Audacity: build successful.
mod script pipe: build fails
Nyuist workbench: build fails
Comment 5 Leland Lucius 2014-04-30 20:24:56 UTC
Just committed r13093 and r13094.  They should correct the loading of mod_nyq_bench and building of mod_script_pipe.
Comment 6 Steve Daulton 2014-05-02 07:54:21 UTC
(In reply to comment #5)
Nyquist Workbench appears to be working correctly in r13094.
Comment 7 Steve Daulton 2014-05-03 08:06:40 UTC
(In reply to comment #6)
and mod-script-pipe builds OK.
Comment 8 Gale Andrews 2014-05-14 05:31:25 UTC
Not managed to build Nyquist Workbench in Ubuntu 13.10. 

In file included from /home/gale/audacity/src/Project.h:27:0,
                 from NyqBench.cpp:28:
/home/gale/audacity/src/AudioIO.h:16:23: fatal error: portaudio.h: No such file or directory
 #include "portaudio.h"
                       ^
compilation terminated.
make: *** [NyqBench.o] Error 1

What I did was: 
1 sudo make clean
2 svn up
3 autoreconf --no-recursive
4 ./configure
5 sudo make 
6 cd to and changed /lib-src/mod-nyq-bench/Makefile to:
  AUDACITY_DIR ?= /home/gale/audacity/
7 make 

Also tried restoring original /lib-src/mod-nyq-bench/Makefile with no changes i.e. AUDACITY_DIR = ../.. with same result.

Let me know if I am missing a step somewhere.
Comment 9 Steve Daulton 2014-05-14 18:40:52 UTC
(In reply to comment #8)
Try using a fresh svn checkout.
Comment 10 Leland Lucius 2014-05-14 20:38:53 UTC
It was because Gale doesn't have portaudio-devel installed.  Just committed a change to allow it to build in that case.
Comment 11 Steve Daulton 2014-05-14 21:07:31 UTC
(In reply to comment #10)
That seems a bit odd because when I built Audacity on Ubuntu (14.04) this evening, portaudio19-dev was pulled in when I ran: apt-get build-dep audacity
Comment 12 Leland Lucius 2014-05-14 22:42:34 UTC
There somehow had to be a portaudio/include directory in the search order for includes for it to be working without portaudio-dev installed.  The module build simply had no other way of finding them.

I just made them look at the lib-src portaudio version.  It's really just to satisfy the Audacity header dependencies and so the lib-src version will work just fine even if the system portaudio is being used for Audacity.
Comment 13 Gale Andrews 2014-05-15 20:09:24 UTC
(In reply to comment #12)
Hi Leland

When I checked "sudo apt-get build-dep audacity" I indeed did not have portaudio19-dev or a few other packages installed, but I have not changed this 
since I installed Ubuntu 13.10.   

Without running "sudo apt-get build-dep audacity", I updated to r13097, rebuilt Audacity and was able to build mod-nyq-bench. However Devices Preferences still said "Using: PortAudio V19-devel" and always has IIRC. 

I was still able to build mod-nyq-bench after running "sudo apt-get build-dep audacity" and rebuilding Audacity. So this seems OK.  

I also built mod-script-pipe. Then I installed Audacity (the executable is at /usr/local/bin) and ran it, and did cd to the /home/gale/audacity/scripts/ directory and ran ./pipe-test.pl. It runs but it spews out "cannot export to /home/gale/pipetest/" errors for all the export steps. Can I assume I am not doing this right, or was it always like this on Linux, or is something in https://code.google.com/p/audacity/source/detail?r=13094 causing this?
Comment 14 Steve Daulton 2014-05-15 20:59:10 UTC
(In reply to comment #13)
> It runs but it spews out "cannot export to
> /home/gale/pipetest/" errors for all the export steps. Can I assume I am not
> doing this right, or was it always like this on Linux

I think that is "normal" (if not, it's been doing that for a long time).
If you manually create ~/pipetest it should run OK.
Comment 15 Gale Andrews 2014-05-16 07:08:01 UTC
(In reply to comment #14)
>> It runs but it spews out "cannot export to
>> /home/gale/pipetest/" errors for all the export steps.
> I think that is "normal" (if not, it's been doing that for a long time).
> If you manually create ~/pipetest it should run OK.
OK, that works. RESOLVED - FIXED. Thanks, Leland & Steve.