v1.06 compiled 2002/08/10 from the debian packages in debian unstable. It seems to work fine but chokes on main.pp line 1182. Commenting out the offending line gets lazarus up and going. Is it a problem with the compiler (too old or so) that gives the error?

Yes, a recent 1.0.7 is recommended.

Mattias Gaertner wrote

There are debian packages on the lazarus web site for 1.0.7 and 1.1.

Found them! This is very usefull.

It would be even more usefull still if you could make them available as an apt source so I won't have to worry about upgrading.

Anders

I tried to contact the maintainer once if he could test the newly updated debian files. but i never got an answer back :(

Running 'make deb' as root in the top dir of fpc will also build the *.deb packages as snapshot (0-<date> as debian version) in /usr/src

Tony Maro wrote

And, 1.0.7 is released on the FPC site, just nobody has bothered to update the Debian packages apparently...

This is http://www.freepascal.org/ we are talking about right?

On the front page it clearly states that the latest release is 1.0.6. This is also the case for download page including one mirror I randomly checked.

So since it is not released obviously noone has made debian packages of it yet.

Or is my browser malfunctioning?

You don't want to run a buggy compiler do you? ;-)

No thanks.

If you want a quick and easy tutorial on installing FPC for use with Lazarus check my website at: http://tony.maro.net/mod.php?mod=userpage&page_id=2

A nightmare! There is no way to easily delete the files once you have unpacked them. There is no control over where stuff goes and that is totally unacceptable to me.

I recently used these exact instructions to install 1.0.7 on a Debian distro.

I believe that, but I don't want to mess up my nice clean filesystem by randomly unpacking stuff into it.

Anders

[ Charset ISO-8859-1 unsupported, converting... ]

There are several answers possible to this:

1 Sometimes there is no choice. Delaying lazarus development till the next FPC release is often not an option.
2 The lazarus team tries to delay stepping over to non release compilers as long as possible. This is easier just after a release, and quite hard if release engineering for a new FPC release has already begun. 3 The 1.0.x series is a fixes branch. Upgrading is relatively easy. The 1.1.x branch is bleeding edge.
4 While not released as formal release, daily snapshots for 1.0.7 are available.

Hi list,

I tried to check out lazarus from CVS yesterday and compiling it with fpc v1.06 compiled 2002/08/10 from the debian packages in debian unstable. It seems to work fine but chokes on main.pp line 1182. Commenting out the offending line gets lazarus up and going. Is it a problem with the compiler (too old or so) that gives the error?

I tried to create a little project with a form and a button and some small things. It compiles fine and everything, but when I try to doubleclick a button to add a callback, it gives me an messagebox that says "... TDEFAULTCOMPONENTEDITOR has created the error: unable to find method. ...". In log-window below the code editor it says unit sysutils not found. Is this a problem with my installation or some bug?

Good thinking requiring a compiler that has never been released.

Anders

Well the problem isn't requiring a compiler never released, the problem is a bug that's in 1.0.6 that causes a buffer to not resize properly, corrupting form files.

And, 1.0.7 is released on the FPC site, just nobody has bothered to update the Debian packages apparently...

You don't want to run a buggy compiler do you? ;-)

If you want a quick and easy tutorial on installing FPC for use with Lazarus check my website at:

http://tony.maro.net/mod.php?mod=userpage&page_id=2

I recently used these exact instructions to install 1.0.7 on a Debian distro.

-Tony

The 1.0.6 will celebrate its first birth day in three days. I wish, the fpc team would release a new version more often, but I know, that it means a lot of work, which is better spend elsewhere. Lazarus is using some features of the FCL and the compiler, that are hardly used by any other program. That's why it finds some bugs first and needs a fixed fpc version. Writing workarounds would break Delphi compatibility. If you want a lazarus working together with the fpc release, then you must checkout a one year old lazarus. I think, the new features of lazarus are a good price for installing a newer, but unreleased compiler. Especially as there are tgz, rpm and debs in the lazarus downloads section. The coming 1.0.8 has good chances to stay the recommended lazarus compiler for a long time.

So since it is not released obviously noone has made debian packages of it yet.

There are debian packages on the lazarus web site for 1.0.7 and 1.1.

Mattias

In one mail you wonder about requiring a non released compiler and in the next you want auto upgrade features for such things. ;)

Eventually there will be apt source lists.

Mattias

Uh, perhaps I misunderstand what you are saying. If you want to untar them somewhere else, then by all means, change the -C switch in the tar command.

As shown in the tutorial, every file is installed in: /usr/local/lib/fpc/1.0.7/

which can be safely deleted if you wanted to get rid of it. Other than that, just delete the symbolic link you created at: /usr/local/bin/ppc386

I don't understand where the nightmare is... It's not as hard as you think, and there's certainly not a lack of control.

I probably would have felt much as you do, except I took the stance that if I was going to be a programmer, I should probably make an attempt to understand what was going on with the compiler, such as where it installs, how to configure it, etc. rather than just letting a package do it all for me.

But, I'm glad Mattias got or found 1.0.7 .deb's for you.

-Tony

Hey! It should be easy! The ftp server is already there so if I understand it right you just need one or two package list files to get it up and running.

:)

Eventually there will be apt source lists.

Great!

Well thanks for helping me find those debs. I don't know if they have always been there and I have just not been able to find them or if they are recent, but anyway with packages it could be easier to get working (which it is now).

Anders