Latest version of OpenMSX in Linux Mint

Страница 1/2
| 2

By thezorry

Resident (56)

Аватар пользователя thezorry

20-03-2016, 18:44

Hello.

Maybe this is a newbie question (I'm kind of new to linux world), but I'm not able to install latest version of OpenMSX in Linux Mint 17.3, if I install it from the package repositories of Mint, I'm only getting version 0.10. With my prevoious ubuntu install, I had the same problem. How do I do to install 0.12 version? I've done a quick search in the subforum but I did not find any answer, so please excuse me if this is an answered question.

Thank you guys!

Для того, чтобы оставить комментарий, необходимо регистрация или !login

By Manuel

Ascended (17503)

Аватар пользователя Manuel

20-03-2016, 19:26

Your distro doesn't have a more modern version available. In the case of Linux Mint, it just seems they're running behind.

Solutions:
1) upgrade your distro to a more recent one. But in your case that doesn't help, as 0.10.0 is the latest there. Ubuntu has a bit more recent versions, but the Ubuntu with the latest openMSX release has not been released yet. See https://launchpad.net/ubuntu/+source/openmsx
2) Build openMSX yourself, from the source code. Luckily, on Linux, that's quite easy.

Regarding 2, you can choose between the latest release or the latest and greatest source code.

All details (pay a lot of attention to the Debian/Ubuntu specific parts, ignore Windows/Mac parts) here: http://openmsx.org/manual/compile.html
Let me know if you need help.

Good luck!

By RetroTechie

Paragon (1563)

Аватар пользователя RetroTechie

20-03-2016, 21:32

"Change distro, or build from source"... ugh - there's more ways to Rome. Tongue

In this case, one option is to manually install .deb packages as needed. Taking my own Debian Linux (testing) install as example:

/etc/apt/sources.list includes http://ftp.de.debian.org/debian/ as one of the places where packages are searched. Simply copying that URL into a browser, I find openMSX packages here: http://ftp.de.debian.org/debian/pool/main/o/openmsx/

You see packages for version 0.8.2, 0.10.1 and 0.12.0 for various architectures. @ This point, best is to remove the older openMSX (and perhaps directly related packages too) from the system. Then:

1) Download the newer .deb package for your architecture. In my case: openmsx_0.12.0-1+b1_amd64.deb
2) As root, change to download directory. Followed by

dpkg -i openmsx_0.12.0-1+b1_amd64.deb

(or do "sudo" followed by above command).
3) If successful, you're done. But just taking the package itself & ignoring dependencies, chances are this will fail (see dpkg output for details). If so:
4) If necessary, remove partially installed package. Then take one of the dependencies that was missing, and install that. Preferably a distro-provided version (easier & safer), if not available a newer version that's obtained / installed using this same procedure.

Repeat (recursively), and most likely one of 2 things will happen:
1) Success. All dependencies installed either from distro or manually located .deb's. And with those in place, newer openMSX installed successfully using dpkg.
2) Somehow you can't get all dependencies in place because one or more of them can't co-operate with other packages on your system. Oh wait... that is probably the reason newer openMSX wasn't in your distro's repository in the first place. :P

So quite a bit of manual work & success not guaranteed. But still easier than "upgrade distro". And if it works, also easier to manage than "compile from source". The latter often isn't as difficult as users may assume, but going that route you lack package management comforts like checking what's installed (or easy removal of all files belonging to a package).

By Manuel

Ascended (17503)

Аватар пользователя Manuel

20-03-2016, 22:29

As you basically already said, installing packages from outside your distro is asking for trouble. No one will guarantee in any way that they will work. There are large chances that it will not. This is not Windows... things stop working if you go outside your distro or at least no one will support it.

Compiling from source isn't at all that bad. And the default location for the installation is in /opt, so that's very easy to remove, with one sudo rm -rf command.

Anyway, whatever you like, but installing random debs from outside of your distro is a nifty way of ruining your system, if you ask me. That's why I'd never recommend it.

By RetroTechie

Paragon (1563)

Аватар пользователя RetroTechie

20-03-2016, 23:35

Manuel wrote:

Anyway, whatever you like, but installing random debs from outside of your distro is a nifty way of ruining your system, if you ask me. That's why I'd never recommend it.

Agree completely! But that's not what you'd be doing here. If you start browsing in a repository found in /etc/apt/sources.list, you're not finding 'random debs' but .deb's from your very own distro. Just newer versions among those - which are destined to migrate into your system anyway (over time). That's something very different than grabbing .deb's from other distro's at random.

In the case of Linux Mint, most of those packages will come from Ubuntu repositories. And the packages you'd be upgrading to newer versions (openmsx*) would be just the application packages. Lower-level dependencies are already installed, or can be installed using the regular package tools like Synaptic, so (rare exceptions aside) you're not installing incompatible system libraries that 1001 other packages rely on. Buttt....

Quote:

Compiling from source isn't at all that bad.

Also agree on that one. In my experience: if you manage to compile from source, it usually gives you a binary that's least likely to segfault or similar. As opposed to installing from binary packages that may or may not be built against different library versions etc.

The advantage of .deb method is that once installed, if a newer version becomes available package will be upgraded automatically as part of regular system updates. Whereas for a package installed from source, upgrading is manual work.

There's pro's and cons to each. But in general: the less manual work, the better.

By gdx

Prophet (4040)

Аватар пользователя gdx

21-03-2016, 01:19

Linux Mint is worrying.

https://lwn.net/Articles/676664/

By thezorry

Resident (56)

Аватар пользователя thezorry

29-03-2016, 10:18

Thank you all for the responses. Sorry for not posting anything before, I was out for holidays. After reading gdx post, I will think about moving away from mint, but before I decide, I will try to build the latest version of openMSX and tell you the results.

By rolandve

Master (233)

Аватар пользователя rolandve

18-05-2016, 14:04

I am trying to build the newest version on MINT. Getting the dependencies is a lot of searching but that works out. I have a new openmsx binary based on the master branch in github that run. It somehow looks for configuration files.. (machines/....xml not found in context) but where? Copying the files to the right place is not the issue.

Getting to compile open-catapult, now thats even more a head-ache because wxWidgets required a wxWidgets XRC file.... but where is that? Can't download it. I installed all the wxWidget files in the ubuntu repository, but this dependency keeps failing. The documentation doesn't dive in to this.

By Manuel

Ascended (17503)

Аватар пользователя Manuel

18-05-2016, 18:47

Getting the dependencies is very easy, just do:
sudo apt-get build-dep openmsx

sudo apt-get build-dep openmsx-catapult

Doing a make install installs it in the default location /opt/openMSX etc. Did you do make install at all?

By rolandve

Master (233)

Аватар пользователя rolandve

18-05-2016, 20:01

Yes, I did, after I remembered that make install exists, just like make uninstall.
openMSX in the repository is still 0.10 so with sudo apt-get build-sep openmsx, I would have gotten the 0.1 code.
I'll keep the build-sep option in mind, now I hand-picked all the dependencies.

Turns out the problem was with wxWidgets. I was using a newer version that gave error on the code.
Have it running now.

Once you know what to do, its always easy.

By Manuel

Ascended (17503)

Аватар пользователя Manuel

18-05-2016, 22:06

The build-dep doesn't pull in openMSX code, only installs all packages of its build-dependencies. It may not be 100% right, but you'll have most of them (if not all). See also http://openmsx.org/manual/compile.html#libs under Debian and Ubuntu (also true for Mint, it's also Debian based).

Which wxWidgets did you use and are you using now? It should work fine with 3.0.

Страница 1/2
| 2