Forum > Linux

Download of FPC 3.2 for Raspberry Pi does not work

(1/4) > >>

Linkat:
Could'nt download the file:

--- Code: Pascal  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---fpc-3.2.0.arm-linux-eabihf-raspberry.tar
https://www.freepascal.org/down/arm/linux-hungary.html

The link doesn't work. The same with the mirror in Canada.

I couldn't find this file on
Index von ftp://ftp.freepascal.org/pub/fpc/dist/3.2.0/

and on SourceForge.

Where can I get it from?

MarkMLl:
Checking with wget, I get a "No such file" error on ftp://ftp.hu.freepascal.org/pub/fpc/dist/3.2.0/arm-linux/fpc-3.2.0.arm-linux-eabihf-raspberry.tar

This one looks OK ftp://ftp.hu.freepascal.org/pub/fpc/dist/3.0.2/arm-linux/fpc-3.0.2.arm-linux-eabi.tar

However that appears to be a 3.0.2 not a 3.2.0... not sure what's going on, I think we need input from an admin, or from somebody who can advise on the preferred compiler version (https://wiki.freepascal.org/Lazarus_on_Raspberry_Pi suggests that it should be bundled with Raspbian).

MarkMLl

Linkat:

Does this file (fpc-3.2.0.arm-linux-eabihf-raspberry.tar) exist?
Where can I get it?
fpc-3.2.0.arm-linux-eabihf-raspberry.tar
Thanks.

trev:
Maybe it's been renamed to this: ftp://mirror.freemirror.org/pub/fpc/dist/3.2.0/arm-linux/fpc-3.2.0.arm-linux-on-aarch64.tar

Broken links first reported in August last year: https://www.mail-archive.com/fpc-pascal@lists.freepascal.org/msg53195.html

Last image: https://sourceforge.net/projects/freepascal/files/Linux/3.0.2/fpc-3.0.2.arm-linux-eabihf-raspberry.tar/download

Updating from 3.0.2 to 3.0.4: http://translate.google.com/translate?prev=/language_tools&u=https%3A%2F%2Fwww.framboise314.fr%2Finstaller-la-derniere-version-de-lazarus-mai-2020-sur-raspberry-pi%2F

Linkat:
Thanks @trev for the information.

In the mailing list you can see, that this problem is known since August 2020.

It's not good, that no one feels responsible.

 

Navigation

[0] Message Index

[#] Next page

Go to full version