Bug 288 – failed to build against system sbsms

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 288 - failed to build against system sbsms


Summary:	failed to build against system sbsms

Status:	RESOLVED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	Other
Version:	1.3.14 alpha
Hardware:	PC Linux

Importance:	P4 Repeatable
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-02-15 20:19 UTC by Benjamin Drung
Modified:	2018-08-20 11:45 UTC (History)
CC List:	4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Benjamin Drung 2011-02-15 20:19:47 UTC

I am using "./configure --with-sbsms=system". Audacity 1.3.12 builds, but SVN trunk fails:

effects/SBSMSEffect.cpp: In member function ‘virtual bool EffectSBSMS::Process()’:
effects/SBSMSEffect.cpp:273: error: ‘struct sbsmsInfo’ has no member named ‘rate0’
effects/SBSMSEffect.cpp:274: error: ‘struct sbsmsInfo’ has no member named ‘rate1’
effects/SBSMSEffect.cpp:275: error: ‘struct sbsmsInfo’ has no member named ‘pitch0’
effects/SBSMSEffect.cpp:276: error: ‘struct sbsmsInfo’ has no member named ‘pitch1’
effects/SBSMSEffect.cpp:278: error: ‘sbsms_quality’ was not declared in this scope
effects/SBSMSEffect.cpp:278: error: expected ‘;’ before ‘quality’
effects/SBSMSEffect.cpp:279: error: ‘rateCBLinear’ was not declared in this scope
effects/SBSMSEffect.cpp:279: error: ‘pitchCBLinear’ was not declared in this scope
effects/SBSMSEffect.cpp:279: error: ‘quality’ was not declared in this scope
make[1]: *** [effects/SBSMSEffect.o] Fehler 1

Comment 1 Gale Andrews 2011-02-16 11:37:48 UTC

I've suggested this as a P4. If it's worse than that (e.g. stops you doing a new Audacity release for Ubuntu in the way you normally would) then I would ask on -devel about it.

Comment 2 Benjamin Drung 2012-06-09 14:05:45 UTC

This bug was fixed some time ago in trunk and therefore will be fixed in the upcoming 2.0.1 release.