I'm leaving the list. Please contact me either in IRC or via mail for
results of the discussion on -core
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
> I think this should be a nice solution:
> bootstrap---.tar.gz
>
> This results in:
> bootstrap-386-linux-1.9.8.tar.gz containing a 1.0.10 version binary, for
> example.
>
> Please note i used "386" for , not x86, or something. So is
> always a valid ppc* ending. This eases up scripting.
In th
On Wed, 30 Mar 2005, Daniel Herzog wrote:
> I think this should be a nice solution:
> bootstrap---.tar.gz
>
> This results in:
> bootstrap-386-linux-1.9.8.tar.gz containing a 1.0.10 version binary, for
> example.
>
> Please note i used "386" for , not x86, or something. So is
> always a valid
I think this should be a nice solution:
bootstrap---.tar.gz
This results in:
bootstrap-386-linux-1.9.8.tar.gz containing a 1.0.10 version binary, for
example.
Please note i used "386" for , not x86, or something. So is
always a valid ppc* ending. This eases up scripting.
___
> On Wed, 2005-03-30 at 20:52 +0200, Daniel Herzog wrote:
>
> > No. - i just tought ppcppc was linux on ppcwell then, replace it
> > with the correct one :-)
>
> It is also called ppcppc on linux:
> $ file /usr/lib/fpc/1.9.4/ppcppc
> /usr/lib/fpc/1.9.4/ppcppc: ELF 32-bit MSB executable, Power
PROTECTED] Behalf Of Daniel
> Herzog
> Sent: 30 March 2005 19:52
> To: FPC developers' list
> Subject: Re: [fpc-devel] Packaging
>
>
> > Does the darwin ppcppc binary actually work on linux-ppc?
>
> No. - i just tought ppcppc was linux on ppcwell then, replace it
On Wed, 2005-03-30 at 20:52 +0200, Daniel Herzog wrote:
> No. - i just tought ppcppc was linux on ppcwell then, replace it
> with the correct one :-)
It is also called ppcppc on linux:
$ file /usr/lib/fpc/1.9.4/ppcppc
/usr/lib/fpc/1.9.4/ppcppc: ELF 32-bit MSB executable, PowerPC or cisco 4500
> Does the darwin ppcppc binary actually work on linux-ppc?
No. - i just tought ppcppc was linux on ppcwell then, replace it
with the correct one :-)
$ ./ppcppc
bash: ./ppcppc: cannot execute binary file
$ file ppcppc
ppcppc: Mach-O executable ppc
$ file ppc386
ppc386: ELF 32-bit LSB execu
On 30 mrt 2005, at 19:32, Dr. Karl-Michael Schindler wrote:
Does the darwin ppcppc binary actually work on linux-ppc?
No, you need a different ppcppc for that.
Jonas
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mai
Does the darwin ppcppc binary actually work on linux-ppc?
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
> I had exactly the same situation with fpc for fink and solved it exactly
> as suggested by Daniel Herzog. I would go for Individual bootstrap tar
> balls for each arch, because this saves a lot of bandwidth. I called the
> one for macosx/darwin: fpc-1.9.8.darwin.bootstrap.tar.gz. maybe it
> shoul
>>Even better:
>>One single archive containing all ppc* starting compilers - this way i
>>could also package it quite easily for all arches, and it would easy to
>>script it using "ppc${ARCH}" everywhere...you see?
>
>
> I don't see it. Because that package will be huge since you need a ppc for
>
I had exactly the same situation with fpc for fink and solved it exactly as suggested by Daniel Herzog. I would go for Individual bootstrap tar balls for each arch, because this saves a lot of bandwidth. I called the one for macosx/darwin: fpc-1.9.8.darwin.bootstrap.tar.gz. maybe it should be fpc-1
> Even better:
> One single archive containing all ppc* starting compilers - this way i
> could also package it quite easily for all arches, and it would easy to
> script it using "ppc${ARCH}" everywhere...you see?
I don't see it. Because that package will be huge since you need a ppc for
every cp
>> A sample configuration, or the great (i really like it) samplecfg tool,
>> are needed, to avoid possibly broken/outdated/... /etc/fpc.cfg files
>>
>> please add this somehow too.
>>
> I'm sorry. Forget about it - OPT="-n" solves it...
This is not needed. The top Makefile already sets RELEASE=1
> A sample configuration, or the great (i really like it) samplecfg tool,
> are needed, to avoid possibly broken/outdated/... /etc/fpc.cfg files
>
> please add this somehow too.
>
I'm sorry. Forget about it - OPT="-n" solves it...
___
fpc-devel maillis
A sample configuration, or the great (i really like it) samplecfg tool,
are needed, to avoid possibly broken/outdated/... /etc/fpc.cfg files
please add this somehow too.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.o
Even better:
One single archive containing all ppc* starting compilers - this way i
could also package it quite easily for all arches, and it would easy to
script it using "ppc${ARCH}" everywhere...you see?
___
fpc-devel maillist - fpc-devel@lists.free
Thanks. I'll, for now, work around it using the binary.tar.
In practise, the only "problem" is the bigger download, and getting the
ppc386 out of it...
> This was clear from the beginning :)
> But thank you for taking the trouble yo elaborate.
>
> We're discussing on the core list how we can acc
On Tue, 29 Mar 2005, Daniel Herzog wrote:
> Okay. I'll totally rephrase this now:
>
> Gentoo builds (almost) everything from source.
> This is done via ebuilds.
> There is grap this file:
> ftp://ftp.freepascal.org/pub/fpc/beta/source-1.9.8/fpc-1.9.8.source.tar.gz
> And compile and install it.
>>Okay. I'll totally rephrase this now:
>>
>>Gentoo builds (almost) everything from source.
>>This is done via ebuilds.
>>There is grap this file:
>>ftp://ftp.freepascal.org/pub/fpc/beta/source-1.9.8/fpc-1.9.8.source.tar.gz
>>And compile and install it.
>
>
> Don't expect this directory to exists
> Okay. I'll totally rephrase this now:
>
> Gentoo builds (almost) everything from source.
> This is done via ebuilds.
> There is grap this file:
> ftp://ftp.freepascal.org/pub/fpc/beta/source-1.9.8/fpc-1.9.8.source.tar.gz
> And compile and install it.
Don't expect this directory to exists very lo
Okay. I'll totally rephrase this now:
Gentoo builds (almost) everything from source.
This is done via ebuilds.
There is grap this file:
ftp://ftp.freepascal.org/pub/fpc/beta/source-1.9.8/fpc-1.9.8.source.tar.gz
And compile and install it.
To do this, i need a starting compiler, nothing more.
It
On Tue, 29 Mar 2005, Marco van de Voort wrote:
> > On Tue, 29 Mar 2005, Daniel Herzog wrote:
> >
> > > Hi all,
> > >
> > > In order to get fpc into portage, the gentoo packaging system
> > > it would be necessary to make available a bootstrap tar ball (640 KB)
> > > with the ppc386 binary and
On 29 mrt 2005, at 15:52, Michael Van Canneyt wrote:
In order to get fpc into portage, the gentoo packaging system
it would be necessary to make available a bootstrap tar ball (640 KB)
with the ppc386 binary and a default fpc.cfg file.
640 K ? Is that a joke ? The compiler sources alone are more th
> On Tue, 29 Mar 2005, Daniel Herzog wrote:
>
> > Hi all,
> >
> > In order to get fpc into portage, the gentoo packaging system
> > it would be necessary to make available a bootstrap tar ball (640 KB)
> > with the ppc386 binary and a default fpc.cfg file.
>
> 640 K ? Is that a joke ? The compil
On Tue, 29 Mar 2005, Daniel Herzog wrote:
> Hi all,
>
> In order to get fpc into portage, the gentoo packaging system
> it would be necessary to make available a bootstrap tar ball (640 KB)
> with the ppc386 binary and a default fpc.cfg file.
640 K ? Is that a joke ? The compiler sources alone
Hi all,
In order to get fpc into portage, the gentoo packaging system
it would be necessary to make available a bootstrap tar ball (640 KB)
with the ppc386 binary and a default fpc.cfg file.
My suggestion would be the same dir as the fpc source tar ball, i.e.
ftp://ftp.freepascal.org/mirrors/fpc/
> Hi guys.
>
> It would be nice if you could add a starting compiler to your source
> packages, this eases up packaging with gentoo alot. this is especially
> important for the 1.9.x series, which is changed. (the stable release
> looks kinda freezed until 2.0.0 is released)
Sources shouldn't cont
Hi guys.
It would be nice if you could add a starting compiler to your source
packages, this eases up packaging with gentoo alot. this is especially
important for the 1.9.x series, which is changed. (the stable release
looks kinda freezed until 2.0.0 is released)
daniel
_
30 matches
Mail list logo
