View Issue Details

IDProjectCategoryView StatusLast Update
0004344ardourbugspublic2020-04-19 20:15
ReporterJMac Assigned Tocth103  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0-alpha10 
Target Version3.0-beta1 
Summary0004344: waf install not working: /usr/local/bin/ardour3 script created wrongly
DescriptionGot this result after configure, build install in terminal with command ardour3

"WARNING: Could not check your glib-2.0 for mutex locking atomic operations.

/usr/local/bin/ardour3: line 39: /usr/local//usr/local/lib/ardour3/ardour-3.0: No such file or directory
/usr/local/bin/ardour3: line 39: exec: /usr/local//usr/local/lib/ardour3/ardour-3.0: cannot execute: No such file or directory
Additional InformationMy system is a quad core Athlon running AVLinux. First time I have seen this. I thought the double enter of /usr/local//usr/local might be it but I do not know.
TagsNo tags attached.

Activities

JMac

2011-09-30 17:28

reporter   ~0011630

I fixed it by doing a gedit on the ardour3 file in the /usr/local/bin/ardour3 by removing the double entry of /usr/local/ wherever it appeared and then saving.

Now, it starts up just fine.

JMac

cth103

2011-10-02 23:18

administrator   ~0011633

Should be fixed in SVN 10183.

system

2020-04-19 20:15

developer   ~0022757

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-09-30 17:19 JMac New Issue
2011-09-30 17:28 JMac Note Added: 0011630
2011-10-02 21:50 cth103 cost => 0.00
2011-10-02 21:50 cth103 Target Version => 3.0-beta1
2011-10-02 21:50 cth103 Summary Ardour3 latest svn 10176 => waf install not working: /usr/local/bin/ardour3 script created wrongly
2011-10-02 23:18 cth103 Note Added: 0011633
2011-10-02 23:18 cth103 Status new => resolved
2011-10-02 23:18 cth103 Resolution open => fixed
2011-10-02 23:18 cth103 Assigned To => cth103
2020-04-19 20:15 system Note Added: 0022757
2020-04-19 20:15 system Status resolved => closed