Which version on Debian Wheezy
lazarus / 32-Linux

----------------------------------------------------------------------
Neuromancer · 2014-06-14 19:30

Hello,

I am using Debian Wheezy (stable version) because there are too much
problems with Debian Testing.

But the version of Lazarus provided in the Debian repositories is
quite old (0.9.30.4) as well as the provided version of FPC (2.6.0).

Do a higher version of Lazarus (1.0.12, 1.0.14, 1.2...) work on Debian
Wheezy ?

----------------------------------------------------------------------
Rails · 2014-06-14 19:44

They should. You might have to upgrade some packages, though. Your
best bet is to upgrade your Debian to testing or unstable.

What sort of problems are you having with testing? Are they in general
or only related to Laz/FPC?

Be advised that once you have installed one of the older Lazarus
versions on Linux, you may need to delete everything Lazarus from your
installation before installing another version.

BTW, I am using 1.2.2 on Debian unstable on this system .

----------------------------------------------------------------------
BigChimp · 2014-06-15 09:23

Using trunk FPC+trunk Laz occassionally on a Debian unstable VM; works
fine.

In addition to what Rails said: next to your apt-installed system wide
FPC+Lazarus you can compile & install e.g. Laz trunk+FPC fixes 2.6 in
your home directory, keeping them separate. You could use e.g. fpcup
for it (disclaimer: I'm one of the fpcup authors)

----------------------------------------------------------------------
Rails · 2014-06-15 12:50

Quote from: BigChimp on June 15, 2014, 11:23:02 amUsing trunk
FPC+trunk Laz occassionally on a Debian unstable VM; works fine.

In addition to what Rails said: next to your apt-installed system wide
FPC+Lazarus you can compile & install e.g. Laz trunk+FPC fixes 2.6 in
your home directory, keeping them separate. You could use e.g. fpcup
for it (disclaimer: I'm one of the fpcup authors)

I have fpcup installed on another Debian Unstable machine (along with
1.2 installed in the conventional manner). Works fine. I thought about
mentioning it before, but decided against it because I thought it
might add a confusion factor.