Package Details: yoshimi 1.3.9-1

Git Clone URL: https://aur.archlinux.org/yoshimi.git (read-only)
Package Base: yoshimi
Description: a fork of the ZynAddSubFX software systhesizer
Upstream URL: http://yoshimi.sourceforge.net/
Licenses: GPL
Submitter: lee
Maintainer: lee
Last Packager: lee
Votes: 60
Popularity: 0.208580
First Submitted: 2009-10-10 14:58
Last Updated: 2016-03-03 21:16

Latest Comments

Morn commented on 2015-02-04 10:02

Thanks, lee!

coderkun commented on 2015-02-04 08:42

Thank you for packaging, lee. Works fine now.

lee commented on 2015-02-04 00:18

Thank you Morn, for reporting; thank you coderkun, for the correct hint.

Now it should work, a -DCMAKE_INSTALL_LIBDIR is specified for cmake.
Ever since yosh started to be shipped with lv2 (prior to that it contained no libs), proper installation of libs on 64bit systems relied on a "mis-feature" in pacman that was removed on 2014-12-19 with the release of pacman-4.2.[1]

[1] section 'Directory Symlink Handling' in http://allanmcrae.com/2014/12/pacman-4-2-released/

coderkun commented on 2015-02-03 15:49

I get the same error message as Morn. I think the package should use /usr/lib instead of /usr/lib64 since the letter one is only a symlink.

lee commented on 2015-02-03 14:52

I cant reproduce, don't have a 64bit machine available and when building for 32bit there's no file/dir /usr/lib64 below pkg/. I'll look into it later today.

Morn commented on 2015-02-03 14:14

I'm getting an error message about conflicting files with 1.3.2:
]# LANG=en pacman -U yoshimi-1.3.2-1-x86_64.pkg.tar.xz
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) yoshimi-1.3.2-1

Total Installed Size: 6.52 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [##################################################################################################] 100%
(1/1) checking package integrity [##################################################################################################] 100%
(1/1) loading package files [##################################################################################################] 100%
(1/1) checking for file conflicts [##################################################################################################] 100%
error: failed to commit transaction (conflicting files)
yoshimi: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.

lee commented on 2014-09-21 14:30

@CrocoDuck
You discovered a bug, will be fixed in next point release.
http://sourceforge.net/p/yoshimi/mailman/message/32852437/
Thanks for reporting.

CrocoDuck commented on 2014-09-21 14:11

@lee

Thank you for your reply and update! I confirm that the package builds as expected now!

lee commented on 2014-09-20 22:40

@CrocoDuck
Excuse the late reply, I had missed out on the notification mail until now.

Added your fix to 1.2.3-2.

Strange enough, this didn't occur when I built yosh prior to uploading 1.2.3-1. Downgrading to gcc-4.9.1-1 (which was installed at the time) didn't change things. Can't figure out a reason ATM, will forward the issue to upstream.

CrocoDuck commented on 2014-09-14 22:57

Hi! Got this error while building:

/home/crocoduck/Downloads/yoshimi/yoshimi/src/yoshimi-1.2.3/src/main.cpp: In function ‘int main(int, char**)’:
/home/crocoduck/Downloads/yoshimi/yoshimi/src/yoshimi-1.2.3/src/main.cpp:75:5: error: ‘cout’ was not declared in this scope
cout << "Yay! We're up and running :-)\n";
^
CMakeFiles/yoshimi.dir/build.make:1881: recipe for target 'CMakeFiles/yoshimi.dir/main.cpp.o' failed
make[2]: *** [CMakeFiles/yoshimi.dir/main.cpp.o] Error 1
CMakeFiles/Makefile2:122: recipe for target 'CMakeFiles/yoshimi.dir/all' failed
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

I have been able to compile the source adding #include <iostream> into main.cpp. I was wondering whether this is a bug or a problem on my machine.

P.S. Thank you for packaging this!

CrocoDuck commented on 2014-09-14 22:56

Hi! Got this error while building:

/home/crocoduck/Downloads/yoshimi/yoshimi/src/yoshimi-1.2.3/src/main.cpp: In function ‘int main(int, char**)’:
/home/crocoduck/Downloads/yoshimi/yoshimi/src/yoshimi-1.2.3/src/main.cpp:75:5: error: ‘cout’ was not declared in this scope
cout << "Yay! We're up and running :-)\n";
^
CMakeFiles/yoshimi.dir/build.make:1881: recipe for target 'CMakeFiles/yoshimi.dir/main.cpp.o' failed
make[2]: *** [CMakeFiles/yoshimi.dir/main.cpp.o] Error 1
CMakeFiles/Makefile2:122: recipe for target 'CMakeFiles/yoshimi.dir/all' failed
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I have been able to compile the source adding #include <iostream> int main.cpp. I was wondering whether this is a bug or a problem on my machine.

P.S. Thank you for packaging this!

lee commented on 2014-06-25 23:36

Updated to v1.2.2

lee commented on 2014-05-30 12:07

Updated to v1.2.1

Anonymous comment on 2014-03-22 22:01

Thanks for the update !

lee commented on 2013-05-13 02:16

updated, thanks.

GuestOne commented on 2013-05-09 15:05

1.1.0 is out.

GuestOne commented on 2012-07-09 08:31

Thanks lee.
When i will be at home i will try to downgrade.
I hope this can help me to solve this issue.

lee commented on 2012-07-08 20:39

@galactic_cowboy
If you've not deleted the old package. Then a simple
$ pacman -U path/to/yoshimi-0.060.12-4-*.pkg.tar.gz
will suffice to downgrade.

lee commented on 2012-07-08 20:28

@galactic_cowboy
And the corresponding patch, of course (almost forgot that one):
http://sebsauvage.net/paste/?c91129dc0a39894e#voPi+XmZKq+08I2Mgii9iSjUIzF33ZJJqPY/0RT/888=

lee commented on 2012-07-08 20:23

Maybe downgrade to 0.060.12, for the time being.
Here's the old PKGBUILD:
http://sebsauvage.net/paste/?f0aed04bb6334029#wmnINcjvgrQGkUi9d1WOBqcw1ptlLE/85IZX8aokziQ=
HTH

GuestOne commented on 2012-07-08 20:06

No, i haven't non-standard CXXFLAGS in /etc/makepkg.conf.
This must be an upstream bug.
Very sad, because yoshimi has this bug and zynaddsubfx with the latest version has various issues with jack ( http://goo.gl/3mMtC ) so i can't continue my work.

lee commented on 2012-07-08 17:42

hm. The only change from 1.0.0-1 to 1.0.0-2 is an echo in
post_install(), so there shouldn't be a difference.

Do you have non-standard CXXFLAGS in /etc/makepkg.conf?
Just a shot in the dark, the error doesn't give me a hint
as I'm no way fluent in c++.

GuestOne commented on 2012-07-08 16:04

Version 0.060.12 was fine but i think also 1.0.0.-1.

Here is an example of error when i try to change instrument and the software freeze:

*** glibc detected *** yoshimi: malloc(): smallbin double linked list corrupted: 0x084d4c38 ***

lee commented on 2012-07-08 13:18

@galactic_cowboy Can't reproduce that one. Version 0.060.12 was fine?
Anyway, this might be an upstream issue (though I'm not sure, of course)
-- it'd probably be best to ask [yoshimi-user]-ML or file a bug on sourceforge.
Is anyone else experiencing this?

GuestOne commented on 2012-07-08 11:30

Version 1.0.0-2 freeze when i try to select an instrument from instrument bank.

lee commented on 2012-07-04 01:12

1.0.0-2
post_install() now echos a couple of lines,
informing the user about the need to do one
initial exit, in order to have a conf file
written.

Anonymous comment on 2012-04-28 09:39

A data backup and redo from the top, will iron out this and a few other minor gremlins.. Cheers.

Anonymous comment on 2012-04-28 09:19

[ Fatal Exception: Simple issue into a major exothermic event.. I'm beginning to wish I hadn't posted this. Teach me to shut up, huh? ;o) ]

/usr/bin/du -> /bin/du ( 32 bit ) - coreutils 8.15-1 ( I added the symlink because it simply wasn't there )
/bin/du -> /usr/bin/du ( 64 bit ) - coreutils 8.16-2

which seemed an oddity.

Both systems were net installed, yes, and only as good as pacman gives me! linux-lts-3.0.28-1 for x86-64, and
linux-lts-3.0.29-1 for i686. Output given was simply, /proc/version for reference.

For the record, no, I agree, this is/was not a specific Yoshimi issue, Just first noticed when installing Yoshimi.

karol_007 commented on 2012-04-27 22:26

Oh, and the symlink looks the same, not reversed.

karol_007 commented on 2012-04-27 22:23

I doesn't look like a yoshimi issue, so you may want to open a thread on the forums to figure out what's wrong.
On my system both 'du' files are owned by coreutils 8.16-2 - is it true for your systems?

I'm not sure what neither a "web installed 32 bit system" (do you mean netinstall?) nor "Arch 7 64_bit system" is. As for [what I'm guessing is] the 'dmesg' output, neither of the linux versions you posted are current:

[karol@black ~]$ dmesg | grep tobias
[ 0.000000] Linux version 3.3.3-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.0 20120414 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Apr 23 09:33:32 UTC 2012

linux-lts has been updated to version 3.0.29-1 on the 25th.

Anonymous comment on 2012-04-27 21:16

@Karol_007
>Are you sure?
>Is your system up to date?

ttbomk, yes. On both counts.

The blip occurred when installing Yoshimi on a web installed 32 bit system ( after having executed pacman -Syu ):

Linux version 3.2.8-1-ARCH (tobias@T-POWA-LX) (gcc version 4.6.2 20120120 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 27 22:13:59 UTC 2012

Also have a fully updated Arch 7 64_bit system:

Linux version 3.0.27-1-lts (tobias@T-POWA-LX) (gcc version 4.6.3 (GCC) ) #1 SMP PREEMPT Wed Apr 4 09:03:15 UTC 2012

In the latter case, the symbolic link ( not entered by myself ) is in place, but reversed,

/bin/du -> /usr/bin/du

karol_007 commented on 2012-04-26 19:30

> Arch Linux's 'du' command just happens to be in /bin

Are you sure?
[karol@black ~]$ which du
/usr/bin/du
[karol@black ~]$ ls -l /bin/du
lrwxrwxrwx 1 root root 11 03-27 04:16 /bin/du -> /usr/bin/du


Is your system up to date?

Anonymous comment on 2012-04-26 19:23

Yoshimi does bail on on the final .xz package creation, with a '/usr/bin/du' File not found!

Arch Linux's 'du' command just happens to be in /bin

Trivial fix, is of course,

ln -s /bin/du /usr/bin/du

lee commented on 2012-04-07 22:01

0.060.12-4 is out - a (probably dirty?) fix for
compile error about missing declaration of usleep

lee commented on 2012-01-30 02:04

thanks @speps, 0.060.12-3 is out.

speps commented on 2012-01-30 01:31

@lee Hey, some fixes http://paste.pocoo.org/raw/542797/ (mxml is a runtime dependency not a build one, fixed and improved desktop file sed line) Cheers

lee commented on 2011-08-24 15:27

added mesa to makedepends, thank you sergej.

sergej commented on 2011-08-24 10:45

You should add mesa to makedepends because of cmake fails to detect fltk otherwise

lee commented on 2011-07-15 13:15

Sorry for the delay, thanks to speps for the pastebins
(I hadn't even upgraded when they arrived, shame on me).
They're incorporated unaltered, except a minor change in
the source array, into 0.060.10-4.

@ foldedwings
pyfltk was not needed for me, I was not able to reproduce
the error. Probably the fltk upgrade+patch now do the trick.

speps commented on 2011-07-12 17:27

@lee Hey, with fltk 1.3 yoshimi needs to be patched in order to build again.
Here is a working patch "yoshimi-fltk13.patch" > http://paste.pocoo.org/raw/437093/
And relative updated PKGBUILD > http://paste.pocoo.org/raw/437096/ > (desktop-file-utils is redundant) > cheers

Anonymous comment on 2011-06-28 06:43

One more thing!! I solved the fltk problem just now!

I had to install pyfltk from aur, not fltk from extra.

Hope this helps, and thanks for your effort!

Anonymous comment on 2011-06-28 06:40

BTW, you were right about the fftw-threads satisfying aubio.

pacman was just complaining that it would not delete fftw because other packages depend on it.

I removed fftw and all the packages relevant to it, installed fftw-threads, and ardour was installed again flawlessly.

Thank you very much!

Anonymous comment on 2011-06-28 06:34

@ lee

Thank you very much!

But unfortunately I got another problem with comliling yoshimi:(

---------------------
CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE):
Could NOT find FLTK (missing: FLTK_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:252 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-2.8/Modules/FindFLTK.cmake:299 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:159 (find_package)
---------------------

But I already have fltk and fltk2 installed, so I don't know what to do. Do I have to install another package?

lee commented on 2011-06-24 19:57

I recall fftw-threads was once needed, presumably for reasons relating to
this now closed feature request:
https://bugs.archlinux.org/task/18541?project=1&string=fftw

fftw from extra seems to work just as well, thus 0.060.10-3 now depends on
fftw.

Thanks for the hint.

Though obsolete now, I am just wondering:
I had fftw-threads and aubio and ardour installed, without issues.
fftw-threads conflicts and provides fftw, thus aubio should be satisfied

Anonymous comment on 2011-06-24 16:03

trying to install this, but I get conflicted dependency error.

because yoshimi depends on fftw-threads, which conflicts with fftw, which is required by aubio and thus ardour, and I need to have ardour.

How can I resolve this dependencies?

lee commented on 2011-04-14 17:11

version 0.060.10-2
* added .desktop file and icon
* Removed the obsolete 'ccmake' command

@speps
(installation actually was non-interactive before, it didn't say 'ccmake .')

Thanks for the desktop integration stuff. For this I am dependent on people
like you, since I don't run any kind of DE and don't feel inclined to do so,
just for testing things I do not use.
What struck me a little is that it adds another dependency, desktop-file-utils.
I was not too sure whether all this is KISS-compliant, but it seems to be
common within the repos and I did not find anything to the contrary in the wiki
or elsewhere ;)
> cheers.

speps commented on 2011-04-12 15:17

@lee Hi david, i notice there is a desktop file in the source package that is not compiled and installed.
You can enable it like this > http://sprunge.us/OFcH
Also you may add a .install > http://sprunge.us/bFUX
Remember use of interactive installation is discouraged for build scripts, you may remove ccmake . > cheers ;)

lee commented on 2010-12-11 20:22

@markhadman
with the current development version I mean 0.062-pre7, which does not
require the fix 0.060.1 needs to detect 32bit arch, but I think this is
unrelated to your problem.

0.060.1-3 builds and runs here on Intel 32bit and Athlon 64bit
Is it still the 'Illegal instruction' error you get?
You could add a line 'ccmake .' before the cmake command, then have a look
at the options presented by ccmake, set BuildForDebug to ON, see if this
makes yosh fail any more verbose.
Being no programmer, I can just recommend to post this issue upstream to
yoshimi-user mailinglist, cal and the others there are very nice and hepful.

markhadman commented on 2010-12-11 17:10

@lee, what do you mean by 'the current development version'? I noticed that you updated the script shortly after posting that last comment, but the new version (0.060.1-3) still doesn't work on my AthlonXP.

lee commented on 2010-12-04 22:42

thans speps, that was quick.
I just realised that autodetection works properly
in the current development version.

speps commented on 2010-12-04 20:11

@lee thanks for the quick response.
Didn't know about this issue (i'm on x86_64 ;)
Btw here is a quick fix in order to make this
build on both archs:
==> http://aur.pastebin.com/V6pcSf2j <== C ya

lee commented on 2010-12-04 18:32

0.060.1-2
moved boost and mxml to makedepends,
split build function to build and package function.
thanks speps.

lee commented on 2010-12-04 18:23

@speps
I too dislike it, but ccmake . is needed because autodetection of 32bit architecture
does not work, "BuildForAMD_X86_64" is always set to to "ON".

Until I find time to figure out how to patch it or until this is fixed upstream I'll
leave it that way.

speps commented on 2010-12-04 16:11

@lee
Please remove "ccmake ." from PKGBUILD since interactive mode is discouraged.
Also boost and mxml are makedepends.

speps commented on 2010-12-04 16:09

@lee
Please remove "ccmake ." from PKGBUILD since interactive mode is discouraged.
Also boost and mxml are makedepends.

M0Rf30 commented on 2010-11-21 21:57

0.060.1 is out

lee commented on 2010-09-23 10:17

@funcmuscle @markhadman,
I have no prior experience with this.
After using google a little, I assume SIGILL is returned by yoshimi => The code contains illegal instructions that are not supported by the CPU architecture. This could be related to the compiler flags from ccmake or makepkg.conf.
a little helpless here.
Did prior versions run on your systems or is it a first time install?

markhadman commented on 2010-09-15 10:32



I keep getting this error:
Illegal instruction

Yes, I also have this problem. Yoshimi will give no more information. I have tried yoshimi -i (running without gui) and yoshimi -A (alsa instead of jack). AMD Athlon XP2400+, ice1712.

funkmuscle commented on 2010-09-11 20:53

just 'yoshimi'
could it be the fltk?? I have the current version but I notice that the non-mixer or non-daw fails to build and it complains about some FL which I think is FLUID from fltk but other fltk depending apps build and runs fine.
on this same box but running ArchBang, all works fine..

funkmuscle commented on 2010-09-11 20:50

just 'yoshimi'

lee commented on 2010-09-11 20:37

hm. works here.
how do you invoke it, just 'yoshimi' or with any options?

lee commented on 2010-09-11 20:19

hm. works here.
how do you invoke it, just 'yoshimi' or with any options?

funkmuscle commented on 2010-09-11 20:10

at running I get it... the app installs fine

lee commented on 2010-09-11 16:23

At what stage of installation/running do the illegal
instructions occur? I cannot reproduce this.

lee commented on 2010-09-11 16:14

At what stage of installation/running do the illegal
instructions occur? I cannot reproduce this.

funkmuscle commented on 2010-09-11 15:57

I keep getting this error:
Illegal instruction

lee commented on 2010-05-04 16:02

0.056-2
fixed broken download link