On 24 Oct 2014, at 14:29, Marco van de Voort wrote:
Btw, afaik running make in utils/fpcm would only work if you had
reached
fcl-base, since you need those include dirs.
It worked because the release compiler would use its own fcl-base units.
On 10/24/2014 12:39 AM, Jonas Maebe wrote:
On 23/10/14 17:16, Vsevolod Alekseyev wrote:
There's no separate makefile for fpcmake alone, is there?
It used to be as simple as going into utils/fpcm and performing a make
all, but with the new FPC-based build system I think that is
unfortunately
On 10/24/2014 03:32 PM, Joost van der Sluis wrote:
On 10/24/2014 12:39 AM, Jonas Maebe wrote:
On 23/10/14 17:16, Vsevolod Alekseyev wrote:
There's no separate makefile for fpcmake alone, is there?
It used to be as simple as going into utils/fpcm and performing a make
all, but with the new
That may be true, but takes tricks. The compiler from me WILL build
trunk, because it is a trunk. I do not have much time but as I stated
before i WILL update it. It just takes a bit longer. Also, I won't do a
full .deb for it, unless some helps with that. I wasn't able to do that
yet and do
Jonas,
In that case I would advice people to use my version of 2.7.1 for the
Raspberry Pi and let me deal with any build difficulties. I am fully
aware you removed the OVERRIDEVERSIONCHECK from the documentation.
The most recently published build by me takes full advantage of most of
the
At the moment, there is not a good, publicly available, starting
compiler other than my unofficial builds.
The real starting compiler has never been public AFAIK.
Maybe the guy(s) or/and girl(s) who have done the original build for the
Raspberry Pi can shed a light on that one...
On
On 23/10/14 10:55, Thaddy de Koning wrote:
The most recently published build by me takes full advantage of most of
the features for ARMV6 EABIHF.
Plz advice on how to progress,
By never saying that people should build trunk with trunk.
Jonas
___
Which means you shut out the platform.
Which is a teaching platform.
On 10/23/2014 11:04 AM, Jonas Maebe wrote:
On 23/10/14 10:55, Thaddy de Koning wrote:
The most recently published build by me takes full advantage of most of
the features for ARMV6 EABIHF.
Plz advice on how to progress,
By
On 23/10/14 11:00, Thaddy de Koning wrote:
At the moment, there is not a good, publicly available, starting
compiler other than my unofficial builds.
The real starting compiler has never been public AFAIK.
The real starting compiler is a cross-compiler. You always have to start
using a
I know it is a cross- compiler. My builds include a (actually 2)
cross-compiler(based on my own builds 2.7.1) The original is NOT a
2.6.X build that is publicly available. That's the point.
Where is the dogfood?
Where is the starting compiler for Raspian/Debian?
Point me at that and I
On 23/10/14 11:09, Thaddy de Koning wrote:
On 10/23/2014 11:04 AM, Jonas Maebe wrote:
On 23/10/14 10:55, Thaddy de Koning wrote:
Plz advice on how to progress,
By never saying that people should build trunk with trunk.
Which means you shut out the platform.
I'm not saying you can't
On 23/10/14 11:16, Thaddy de Koning wrote:
I know it is a cross- compiler. My builds include a (actually 2)
cross-compiler(based on my own builds 2.7.1) The original is NOT a
2.6.X build that is publicly available. That's the point.
Where is the dogfood?
Where is the starting
Not for ARMV6 EABIHF
On 10/23/2014 11:23 AM, Jonas Maebe wrote:
On 23/10/14 11:16, Thaddy de Koning wrote:
I know it is a cross- compiler. My builds include a (actually 2)
cross-compiler(based on my own builds 2.7.1) The original is NOT a
2.6.X build that is publicly available. That's the
Bad practise is the only practise if knowledge about good practise is
not available.
I am fully prepared to accept you are right. In fact, in my professional
settings I would not do otherwise.
But this is a special case, for a huge platform, and somebody, somehow,
forgot about the license
On 23/10/14 11:28, Thaddy de Koning wrote:
The starting compiler is any official FPC 2.6.4 compiler that can be
downloaded from our website. With any of those compilers, you can build
both cross and native trunk compiler for any of the targets supported
only by trunk. That's how all targets
Thaddy de Koning wrote:
Not for ARMV6 EABIHF
Building for ARMV6+vfpv2 armhf is indeed a bit of a messs.
Afaict it's not possible to build a cross compiler that defaults to
armv6 ARMHF without modifying the source. With the right flags you
should be able to create a cross-compiler that is
On 10/23/2014 11:49 AM, Jonas Maebe wrote:
On 23/10/14 11:28, Thaddy de Koning wrote:
The starting compiler is any official FPC 2.6.4 compiler that can be
downloaded from our website. With any of those compilers, you can build
both cross and native trunk compiler for any of the targets
ok, but can we now please return this thread to the original subject re
2.7.1 (and 2.6.4) for rpi. TIA John
On 23 October 2014 13:41, Joost van der Sluis jo...@cnoc.nl wrote:
On 10/23/2014 11:49 AM, Jonas Maebe wrote:
On 23/10/14 11:28, Thaddy de Koning wrote:
The starting compiler is any
With this in mind, how is one supposed to go about implementing a brand
new target? Should I build a compiler from modified release branch, then
use that to compile the modified trunk?
On 10/23/2014 5:04 AM, Jonas Maebe wrote:
By never saying that people should build trunk with trunk.
In our previous episode, Thaddy de Koning said:
Bad practise is the only practise if knowledge about good practise is
not available.
Should I change cursive to bold here then?
http://www.stack.nl/~marcov/buildfaq/#toc-Section-2.2
___
fpc-devel
On 23/10/14 16:21, Vsevolod Alekseyev wrote:
With this in mind, how is one supposed to go about implementing a brand
new target? Should I build a compiler from modified release branch, then
use that to compile the modified trunk?
You build a cross-compiler for your brand new target from the
If you follow the steps in that post, you'll get the following:
makefile:197: *** The Makefile doesn't support target i386-winphonesim,
please r
un fpcmake first. Stop.
If you run fpcmake -Tall -w first, you'll get the same. Looks like the
first step should be rebuilding fpcmake itself with
On 23/10/14 17:06, Vsevolod Alekseyev wrote:
If you follow the steps in that post, you'll get the following:
makefile:197: *** The Makefile doesn't support target i386-winphonesim,
please r
un fpcmake first. Stop.
If you run fpcmake -Tall -w first, you'll get the same. Looks like the
There's no separate makefile for fpcmake alone, is there?
On 10/23/2014 11:12 AM, Jonas Maebe wrote:
On 23/10/14 17:06, Vsevolod Alekseyev wrote:
If you follow the steps in that post, you'll get the following:
makefile:197: *** The Makefile doesn't support target i386-winphonesim,
please r
un
On 10/23/2014 08:41 AM, Joost van der Sluis wrote:
On 10/23/2014 11:49 AM, Jonas Maebe wrote:
On 23/10/14 11:28, Thaddy de Koning wrote:
The starting compiler is any official FPC 2.6.4 compiler that can be
downloaded from our website. With any of those compilers, you can build
both cross and
In our previous episode, Vsevolod Alekseyev said:
There's no separate makefile for fpcmake alone, is there?
No. There are more such cases, and while there are tricks for advanced
users, like with the starting compiler version, I suggest you stick to
the official requirement of having the full
On 23/10/14 17:16, Vsevolod Alekseyev wrote:
There's no separate makefile for fpcmake alone, is there?
It used to be as simple as going into utils/fpcm and performing a make
all, but with the new FPC-based build system I think that is
unfortunately no longer possible.
Jonas
On 23/10/14 17:43, Marco van de Voort wrote:
In our previous episode, Vsevolod Alekseyev said:
There's no separate makefile for fpcmake alone, is there?
No. There are more such cases, and while there are tricks for advanced
users, like with the starting compiler version, I suggest you stick
Thanks. So what exactly does it do? How does one access? Just for wheezy or
will it work on jessie too? John
On 22 October 2014 00:08, peter green plugw...@p10link.net wrote:
peter green wrote:
So it would seem FPC is currently broken on
stable Raspbian which is a pity.
It's fine on plain
deb http://plugwash.raspbian.org/wsf wheezy-wsf main
Thanks. So what exactly does it do? How does one access?
It's an apt repository I just set up for fixes to dependency problems
caused by the foundations webkit-related packages (they shipped an
updated webkit and a load of related updates
-Message d'origine-
De : fpc-devel-boun...@lists.freepascal.org [mailto:fpc-devel-
boun...@lists.freepascal.org] De la part de peter green
Envoyé : mardi 21 octobre 2014 10:32
À : FPC developers' list
Objet : Re: [fpc-devel] Building 2.7.1 on current Raspbian fails
Paul Michell
Pierre Free Pascal wrote:
https://archive.raspbian.org/raspbian/pool/main/f/fpc/
The 2.6.4 release is able to successfully compile
a 2.7.1 trunk compiler.
:) Thanks for confirming.
Several files are missing in this source release:
The source package which is made up of
Paul Michell wrote:
I should probablly get arround to doing a raspbian version of 2.6.4.
Yes please :)
Ok, i've just uploaded 2.6.4
https://archive.raspbian.org/raspbian/pool/main/f/fpc/
___
fpc-devel maillist -
On Tuesday 21 Oct 2014 09:31:42 peter green wrote:
Ok, i've just uploaded 2.6.4
https://archive.raspbian.org/raspbian/pool/main/f/fpc/
Thank you, how am I best to install this?
I naively thought that would update the version installed
when you perform:
sudo apt-get update
sudo apt-get
Don't know why you have this problem with wheezy, but can confirm I'm
running rpi jessie, and the 'sudo' sequence above works for me ok ie does
70Mbyte download installs fpc with no errors. Haven't really tested it,
but help says it is 2.6.2 -8 rpil+b2 2014/7/21 for arm.
john
On 21 October
On Tuesday 21 Oct 2014 13:45:25 John Lee wrote:
Don't know why you have this problem with wheezy, but can confirm I'm
running rpi jessie, and the 'sudo' sequence above works for me ok ie does
70Mbyte download installs fpc with no errors. Haven't really tested it,
but help says it is 2.6.2 -8
Paul Michell wrote:
On Tuesday 21 Oct 2014 13:45:25 John Lee wrote:
Don't know why you have this problem with wheezy, but can confirm I'm
running rpi jessie, and the 'sudo' sequence above works for me ok ie does
70Mbyte download installs fpc with no errors. Haven't really tested it,
but
peter green wrote:
So it would seem FPC is currently broken on
stable Raspbian which is a pity.
It's fine on plain raspbian, unfortunately it seems that the raspberry
pi foundation are shipping a newer version of binutils which conflicts
with the fpc packaging from wheezy.
Since the
On Friday 17 Oct 2014 23:02:29 John Lee wrote:
Looks as if you have a working fpc 2.7.1 snapshot for rpi. IAre you
planning to make this available on your web site? If not, can you zip pls
it, and put it on cloud or some ftp site - I'll then put it on fpc ftp site.
John
I was intending to
On Saturday 18 Oct 2014 12:12:26 Marco van de Voort wrote:
...
(fpdoc requiring crt*)
crt* files are part of build-essentials and are basically *nix binary
startup code.
Most binaries don't need them, since they use RTL supplied versions of these
startup files for pascal-only programs.
On Sunday 19 Oct 2014 02:32:49 peter green wrote:
Paul Michell wrote:
I'm currently trying to build 2.7.1 from SVN on the latest Raspbian
(2014-09-09).
I've previously built this with either 2.6.0 from the repository, or with
Thaddy de Koning's build from March 2014.
Currently,
In our previous episode, Paul Michell said:
Ideally, I would like to establish a build process that doesn't require any
changes to the FPC codebase.
Then you must learn to setup a complete cross-compile setup, including
target libraries and startup, and make sure the compiler only finds those.
ok, thanks, let me know where I can get rpi wheezy or jessie binary when
you are ready I'll publish it as an fpc ftp snapshot. I'll do same for
2.6.x too.
John
On 20 October 2014 10:59, Paul Michell p...@michellcomputing.co.uk wrote:
On Friday 17 Oct 2014 23:02:29 John Lee wrote:
Looks as
John Lee wrote:
I'll do same for 2.6.x too.
Note that plain 2.6.x doesn't support armhf, in debian/raspbian we have
a patch adding support.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
In our previous episode, Paul Michell said:
make clean all NO_UNIT_PROCESS OPT=-dNO_THREADING
I have now! ;)
It got passed the prior problem, but now halts with a similar issue in fpdoc.
Thanks Joost
(fpdoc requiring crt*)
crt* files are part of build-essentials and are basically *nix
Paul Michell wrote:
I'm currently trying to build 2.7.1 from SVN on the latest Raspbian
(2014-09-09).
I've previously built this with either 2.6.0 from the repository, or with
Thaddy de Koning's build from March 2014.
Currently, neither of these will build 2.7.1 on a Raspberry Pi. So I have
I'm currently trying to build 2.7.1 from SVN on the latest Raspbian
(2014-09-09).
I've previously built this with either 2.6.0 from the repository, or with
Thaddy de Koning's build from March 2014.
Currently, neither of these will build 2.7.1 on a Raspberry Pi. So I have also
tried with the
On 10/17/2014 12:09 PM, Paul Michell wrote:
I'm currently trying to build 2.7.1 from SVN on the latest Raspbian
(2014-09-09).
I've previously built this with either 2.6.0 from the repository, or with
Thaddy de Koning's build from March 2014.
Currently, neither of these will build 2.7.1 on a
On Friday 17 Oct 2014 11:35:30 Henry Vermaak wrote:
fpmake.pp(46) Warning: crti.o not found, this will probably cause a
linking failure
fpmake.pp(46) Warning: crtbegin.o not found, this will probably cause a
linking failure
fpmake.pp(46) Warning: crtend.o not found, this will
This is known. I forgot a bit about my rasp, but I will try to make a
new build + build instructions within a week.
The warnings can be -partially - ignored though...
Tnx Paul, maybe we can coordinate this?
On 10/17/2014 1:02 PM, Paul Michell wrote:
On Friday 17 Oct 2014 11:35:30 Henry
On Friday 17 Oct 2014 12:40:58 Joost van der Sluis wrote:
Did you try
make clean all NO_UNIT_PROCESS OPT=-dNO_THREADING
I have now! ;)
It got passed the prior problem, but now halts with a similar issue in fpdoc.
Thanks Joost
On Friday 17 Oct 2014 13:06:21 Thaddy de Koning wrote:
This is known. I forgot a bit about my rasp, but I will try to make a
new build + build instructions within a week.
The warnings can be -partially - ignored though...
Tnx Paul, maybe we can coordinate this?
Yes, of course, feel free to
Paul Michell wrote:
I'm currently trying to build 2.7.1 from SVN on the latest Raspbian
(2014-09-09).
I've previously built this with either 2.6.0 from the repository, or with
Thaddy de Koning's build from March 2014.
Currently, neither of these will build 2.7.1 on a Raspberry Pi. So I have
On Friday 17 Oct 2014 12:02:23 Paul Michell wrote:
On Friday 17 Oct 2014 11:35:30 Henry Vermaak wrote:
...
Where are these files on your system? I remember after multiarch
happened on debian I had to add some library paths to get fpc to link.
This sounds like a similar
On 10/17/2014 10:58 AM, Paul Michell wrote:
What are the files crti.o, crtn.o, crtbegin.o, crtend.o used for by Free Pascal?
from their name, many think they are CRT related but they are C RunTime
libraries, actually...
Is this dependency something new, or has it always been there?
if
Paul
Looks as if you have a working fpc 2.7.1 snapshot for rpi. IAre you
planning to make this available on your web site? If not, can you zip pls
it, and put it on cloud or some ftp site - I'll then put it on fpc ftp site.
TIA John
On 17 October 2014 21:16, waldo kitty wkitt...@windstream.net
56 matches
Mail list logo
