Package Details: bristol 0.60.11-3

Git Clone URL: https://aur.archlinux.org/bristol.git (read-only, click to copy)
Package Base: bristol
Description: Vintage synthesizers emulator
Upstream URL: http://bristol.sourceforge.net
Licenses: GPL
Submitter: None
Maintainer: UmamiAppearance
Last Packager: UmamiAppearance
Votes: 70
Popularity: 0.000002
First Submitted: 2007-07-04 20:55 (UTC)
Last Updated: 2023-01-18 12:20 (UTC)

Latest Comments

1 2 3 Next › Last »

nimius commented on 2024-10-24 20:28 (UTC)

I made a working PKGBUILD:

https://gist.github.com/nimius-dev/3994dc8dddae3a9e3aa093932ecb9cdb

OctopusET commented on 2024-07-19 09:16 (UTC)

https://sources.debian.org/data/main/b/bristol/0.60.11-5/debian/patches/05-implicit-function-declaration.patch

Can you add this patch also?

UmamiAppearance commented on 2023-03-22 10:22 (UTC)

As no one adopted the package, I took it back. If anyone likes to take over the maintenance, just let me know.

UmamiAppearance commented on 2023-01-18 10:53 (UTC) (edited on 2023-01-18 12:25 (UTC) by UmamiAppearance)

Hi there.

I used to be the maintainer of this package, but unfortunately I was no longer able to take care of it. I don't have access to my old account, and also the email address is no longer active.

Since I now want to use bristol again, I have created a working PGKBUILD by applying the Debian patch. You can find the code in this gist: https://gist.github.com/UmamiAppearance/ce5ee1f0f10036fa2e3edeab125c00f9.

I don't have the time to maintain this package anymore. So as a next step, I will try to get access to my old account/disown this package. I hope someone volunteers to take over the maintenance.

Best regards.

edit: I managed to regain access. Package is orphaned now
edit2: Also the package should compile again (for now)

arkades commented on 2022-01-13 13:23 (UTC) (edited on 2022-01-13 13:47 (UTC) by arkades)

tried to compile it with pacaur amd also got:

/bin/ld: brightonCLI.o:/home/arkade/build/bristol/src/bristol-0.60.11/brighton/brightonCLI.c:139: multiple definition of `event'; brightonMixerMenu.o:/home/arkade/build/bristol/src/bristol-0.60.11/brighton/brightonMixerMenu.c:1182: first defined here

I quickly added CC="gcc -Wl,--allow-multiple-definition" to ./configure arguments in PKGBUILD's build() function to make it build. Thats probably a temporary solution.

vistefan commented on 2021-09-23 15:03 (UTC) (edited on 2021-09-23 15:05 (UTC) by vistefan)

tried to compile it with yay on manjaro and got:

/usr/bin/ld: brightonCLI.o:/home/user/.cache/yay/bristol/src/bristol-0.60.11/brighton/brightonCLI.c:139: multiple definition of `event'; brightonMixerMenu.o:/home/user/.cache/yay/bristol/src/bristol-0.60.11/brighton/brightonMixerMenu.c:1182: first defined here
collect2: error: ld returned 1 exit status

lafleur commented on 2021-02-09 12:34 (UTC)

I can confirm the aur-av-bin repo is still operative.

I also managed to compile bristol by applying the gcc patch found at debian patches. The url of the patch is there.

So basically :

makepkg -o
(cd src/bristol-0.60.11 && curl https://sources.debian.org/data/main/b/bristol/0.60.11-3.1/debian/patches/04-gcc_10.patch | patch -p 1)
makepkg -e

<deleted-account> commented on 2020-07-23 09:29 (UTC)

i followed the instructions here https://github.com/mxmilkiib/aur-av-bin they have already built the packages including bristol. you just add to your repository. i think after installing bristol remember to remove the repository so it don't create conflicts

GuestOne commented on 2020-06-22 18:01 (UTC)

I was unable to compile. Here the log: https://ybin.me/p/3e5462fbc5212e55#JrcUUFM4HYamzd+pqbb98uWWcJx3V5fFCyHEqgVD+NE=

mgd commented on 2020-05-23 16:18 (UTC)

@reber: Which version of gcc are you using on that "old" machine and which version on the current one?

The modification of the code I made is correcting an error in the code that I guess is there in the code on your "old" machine as well.

<wild guess> Maybe older versions of gcc accepted dublicated identical definitions of the same variable and silently merged them together (I haven't followed gcc development in a while, so I don't know). </wild guess>

In any case you must not define the same global variable twice. So that seems a bug in the source. In other words, my change is fixing a sourcecode error that has nothing to do whatsoever with any tools or libraries involved. iff my wild guess as of above is correct it is just that a change in the tools (gcc) is exposing an error that was there all along.

Kind regards, Michael