Hi All,

If Snapshots are available this means the compiler had no problems, nothing more, nothing less. ok.

I read this also as: If snapshots are NOT available the compiler refused them, right?

In that case Win32/64 setups both with FPC 2.4.0 and 2.4.3 do not compile since juli 27th, as far as I can see on the snapshot download pages.

Maybe someone in charge can please take a look?

Thanks in advance,
John

John vd Waeter wrote

I read this also as: If snapshots are NOT available the compiler refused them, right?

No, there could also be various issues which would hang the service which builds the snapshots, like was the case this last days.

We are investigating what went wrong.

We are investigating what went wrong.

Thanks!

John

Ok, there are new snapshots now. Careful that not all are built yet, but enought to test wince.

Felipe Monteiro de Carvalho wrote

Ok, there are new snapshots now.

Is it intentional that the win32 builds with fpc 2.5.1 are not listed on the website?

Felipe Monteiro de Carvalho wrote

Ok, there are new snapshots now. Careful that not all are built yet, but enought to test wince.

Download 2.4.0 version is in progress... ;-)

2010/8/2 Bernd Kreuss :

Yes, Those are even more experimental than the other snapshots and they would make that download page even more crowded, Of course you can still download then directly from the fpc site.

VIncent

Hello, folks.

I am afraid that this is an out-of-date (say Leopard!, PowerPC!!) issue, the l atest snapshot (lazarus-0.9.29.27011-20100805-powerpc-macosx.dmg) does not sta rt under a user account. The current 'stable' release (0.28.2) also fails to s tart under a user account but saying 'LSOpenFromURLSpec() failed with error - 10810' when is opened from command line. Both versions work quite well under t he root or an admin account.

How to work-around for this issue?

Thanks,

Haruo, Niigata, Japan.

Did you set the permissions properly?

I have a "developer" group setup for users that have rights to use Lazarus/FPC

sudo chgrp -Rf developer /Developer/Source
sudo chmod -Rf ug+rw /Developer/Source

The -Rf parameters to change group and permissions is important to recursively set these options.

If you create the group, you should do so using Apple's User Manager program not just the Darwin shell.

Andrew, Thank you for your reply.

I created the 'developer' group and made 'chgrp'ing and 'chmod'ing of /Develop er/Lazarus directory according to your assistance. However, it did not work. I also tried chgrp and chmod for /Developer directory, in vain. Of course, my u ser account was included in the 'developer' group. I could launch Xcode.app on my user account before creating 'developer' group, so that, IMHO, there shoul d be another matter to prevent starting Lazarus.

Regards,

Haruo Toda, Niigata Japan.

Hi, folks, I have work-around the issue.

I noticed the following error message Lazarus said when it was launched inside the App bundle.

---------
power-mac-g5:MacOS todaharuo$ cd /Developer/Lazarus/Lazarus.app/Contents/MacOS power-mac-g5:MacOS todaharuo$ ./lazarus
[FORMS.PP] ExceptionOccurred
Sender=EPrinter
Exception=Printer " " does't exists.
Stack trace:
$00A63E14
$00A624C0
$00A620E4
$00A63388
TApplication.HandleException Printer " " does't exists. Stack trace:
$00A63E14
$00A624C0
$00A620E4
$00A63388
exception at 00A63E14:
Printer " " does't exists.
---------

At this time, I used the newly installed Hewlett-Packard OfficeJet H470 printe r. Then I changed the printer to Adobe PDF by using Apple's Printer select pan el. Lazarus started correctly. Once started, it starts regardless of printer s election.

Thanks all.

Haruo.

Did you log-out and re-login after joining the group? I know that a re-start sometimes is required after adding users to groups otherwise access denied errors will persist until security is synchronized.

With regard to this - I had noticed a similar problem, and even prepared a patch which I had forgotten to submit. See

<http://bugs.freepascal.org/view.php?id=17120>

Colin

Colin, I read your patch. That seems to solve really what I encountered.

It may be a rather rare case, running Lazarus first on a newly settled Mac -- before any printing works ;-)

Regards, Haruo.

Haruo Toda wrote

Colin, I read your patch. That seems to solve really what I encountered. It may be a rather rare case, running Lazarus first on a newly settled Mac -- before any printing works ;-)

while it may be an unusual case, it has been found and can now be handled... consider the situation where someone doesn't have a printer and won't be printing at all and how this problem would effect them ;)