Tomas Hajny wrote:
> On 5 Aug 06, at 21:03, Florian Klaempfl wrote:
>> Tomas Hajny wrote:
>>> Peter Vreman wrote:
>> on't bother with Solaris in 2.0.x, it won't work at all. None of
>> the Solaris fixes from 2.1.1 have been merged
> On a positive note, Sparc/Solaris works fine in 2.1.1
On 5 Aug 06, at 21:03, Florian Klaempfl wrote:
> Tomas Hajny wrote:
> > Peter Vreman wrote:
> on't bother with Solaris in 2.0.x, it won't work at all. None of
> the Solaris fixes from 2.1.1 have been merged
> >>> On a positive note, Sparc/Solaris works fine in 2.1.1
> >> I tried to merge
Jonas Maebe wrote:
> Sent.
Thanks, got it. I've just added another Perl rule to the filters to hopefully
allow patches while rejecting any other multiparts.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_
On 05 Aug 2006, at 23:42, Mark Morgan Lloyd wrote:
Drat- sorry, the patch didn't get here (filters on ML are more than
a little
agressive). Any chance of a copy to either markMLl.in or
markMLl.fpc2 .AT.
telemetry .DOT. co.uk?
Sent.
Jonas
___
f
Jonas Maebe wrote:
> I would suggest to use 2.0.4-rc2 with the patch I posted to the list.
> It should work fine.
Drat- sorry, the patch didn't get here (filters on ML are more than a little
agressive). Any chance of a copy to either markMLl.in or markMLl.fpc2 .AT.
telemetry .DOT. co.uk?
--
Mar
On 05 Aug 2006, at 23:26, Mark Morgan Lloyd wrote:
I guess that's the last time I look at 2.0.2- it's obviously got
problems.
I would suggest to use 2.0.4-rc2 with the patch I posted to the list.
It should work fine.
Jonas
___
fpc-pascal maill
Mark Morgan Lloyd wrote:
> Compilation (make cycle) now progresses beyond that one and gets to this:
>
> /home/markMLl/pascal/src/fpcsrc/compiler/ppc1 -Fi../inc -Fi../sparc -Fi../unix
> -Fisparc -FE. -FU../../rtl/units/sparc-linux -dsparc -Us -Sg system.pp
> Free Pascal Compiler version 2.0.4-rc2
Tomas Hajny wrote:
> Peter Vreman wrote:
on't bother with Solaris in 2.0.x, it won't work at all. None of
the Solaris fixes from 2.1.1 have been merged
>>> On a positive note, Sparc/Solaris works fine in 2.1.1
>> I tried to merge it in the past but aborted it. The Solaris RTL
>> changes h
Peter Vreman wrote:
>>
>>>on't bother with Solaris in 2.0.x, it won't work at all. None of
>>>the Solaris fixes from 2.1.1 have been merged
>>
>>On a positive note, Sparc/Solaris works fine in 2.1.1
>
> I tried to merge it in the past but aborted it. The Solaris RTL
> changes had a too much conflic
on't bother with Solaris in 2.0.x, it won't work at all. None of
the Solaris fixes from 2.1.1 have been merged
On a positive note, Sparc/Solaris works fine in 2.1.1
I tried to merge it in the past but aborted it. The Solaris RTL
changes had a too much conflicts to qualify for a merge to 2
Looking forward to getting that far :-) I'm considering running up v8 in a
SPARCserver but right now I can do without the extra heat.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_
On 3 aug 2006, at 19:03, Jonas Maebe wrote:
on't bother with Solaris in 2.0.x, it won't work at all. None of
the Solaris fixes from 2.1.1 have been merged
On a positive note, Sparc/Solaris works fine in 2.1.1
Jonas
___
fpc-pascal maillist - fpc
On 3 aug 2006, at 17:14, Mark Morgan Lloyd wrote:
Thanks, every bit helps. I'm hoping to look at Solaris at some
point but I've
only got v8 running here at present- I'm hoping there'll be a v10
with the new
machines.
Don't bother with Solaris in 2.0.x, it won't work at all. None of the
Jonas Maebe wrote:
> I can reproduce the problem under SPARC/Solaris. I'll try to get at
> least that one compiling (don't have access to a sparc/linux machine)
> and commit the needed patches.
Thanks, every bit helps. I'm hoping to look at Solaris at some point but I've
only got v8 running here
On 3 aug 2006, at 16:10, Mark Morgan Lloyd wrote:
As discussed earlier I was starting off with the released 2.0.0
compiler. Source
files from fpcbuild_2_0_4_rc2.zip downloaded about 24 hours ago-
I've got
limited free bandwidth here.
I can reproduce the problem under SPARC/Solaris. I'll t
OK, 4x calls missing as below
1 1>[EMAIL PROTECTED]:~/pascal/src/fpcsrc/rtl/linux/sparc$ diff -u sysnr.inc~
sysnr.inc
--- sysnr.inc~ 2006-02-15 07:19:26.0 +
+++ sysnr.inc 2006-08-03 13:49:10.0 +
@@ -207,14 +207,14 @@
syscall_nr_setpgid = 185 ; // Common
Peter Vreman wrote:
> 2.0.4 (and also the current 2.1.1) can still be build by 2.0.0.
Sure- on an Intel platform.
Running on i386- I've just had another session and can confirm that 2.0.2 can
build both its own sources and those of 2.0.4, so my earlier problem was
definitely something to do with
Mark Morgan Lloyd wrote:
> Jonas Maebe wrote:
>
>> > The only thing that bothers me here is that while this is the
>> > correct solution
>> > it might not be possible. With the major caveat that I'm a beginner
>> > at this but
>> > I've demonstrated that 2.0.0 can't compile 2.0.2, and I suspect
>>
Mark Morgan Lloyd schreef:
Jonas Maebe wrote:
The only thing that bothers me here is that while this is the
correct solution
it might not be possible. With the major caveat that I'm a beginner
at this but
I've demonstrated that 2.0.0 can't compile 2.0.2, and I suspect
that once I've
fixed the m
Jonas Maebe wrote:
> > The only thing that bothers me here is that while this is the
> > correct solution
> > it might not be possible. With the major caveat that I'm a beginner
> > at this but
> > I've demonstrated that 2.0.0 can't compile 2.0.2, and I suspect
> > that once I've
> > fixed the mis
> Vincent Snijders wrote:
>
>> Look up the syscall_nr_exit_group (the number for exit_group syscall)
>> for sparc and
>> add it to rtl/linux/sparc/sysnr.inc and try to compile again.
>>
>> This syscall was not used in fpc 2.0.2, but was added afterwards. You
>> might find
>> more of those.
>
> Than
Vincent Snijders wrote:
> Look up the syscall_nr_exit_group (the number for exit_group syscall) for
> sparc and
> add it to rtl/linux/sparc/sysnr.inc and try to compile again.
>
> This syscall was not used in fpc 2.0.2, but was added afterwards. You might
> find
> more of those.
Thanks. I'll f
On 3 aug 2006, at 11:11, Mark Morgan Lloyd wrote:
Forget about old stable releases like 2.0.2, only work with
current svn
(2.0.4 or 2.1.1).
The only thing that bothers me here is that while this is the
correct solution
it might not be possible. With the major caveat that I'm a beginner
Peter Vreman wrote:
> There is only one correct solution: Fix the building of the 2.0.4 by
> looking up the correct syscall in the C headers.
>
> Forget about old stable releases like 2.0.2, only work with current svn
> (2.0.4 or 2.1.1).
The only thing that bothers me here is that while this is
Mark Morgan Lloyd schreef:
Tomas Hajny wrote:
I propose to check with the 2.0.4-rc2 sources. You can get these from
ftp://ftp.freepascal.org/pub/fpc/beta/2.0.4-rc2/source/,
That builds (make cycle) OK on/for linux-i386 using FPC 2.0.2, but on
linux-sparc using FPC 2.0.0 I get:
Target OS: Lin
> Tomas Hajny wrote:
>
>> I propose to check with the 2.0.4-rc2 sources. You can get these from
>> ftp://ftp.freepascal.org/pub/fpc/beta/2.0.4-rc2/source/,
>
> That builds (make cycle) OK on/for linux-i386 using FPC 2.0.2, but on
> linux-sparc using FPC 2.0.0 I get:
>
> Target OS: Linux for SPARC
>
Tomas Hajny wrote:
> I propose to check with the 2.0.4-rc2 sources. You can get these from
> ftp://ftp.freepascal.org/pub/fpc/beta/2.0.4-rc2/source/,
That builds (make cycle) OK on/for linux-i386 using FPC 2.0.2, but on
linux-sparc using FPC 2.0.0 I get:
Target OS: Linux for SPARC
Compiling syst
On 2 aug 2006, at 10:20, Mark Morgan Lloyd wrote:
Not only that, but a kernel crash always means something is wrong in
the kernel. No matter how badly a program is written, the (Linux)
kernel should never crash (UML or otherwise).
Yes, agreed. I might re-test as I get to understand things bet
Jonas Maebe wrote:
>
> On 2 aug 2006, at 00:47, Mark Morgan Lloyd wrote:
>
> > * If I run the tests (make full) on i386 2.0.2 I get a UML (User
> > Mode Linux on
> > 2.4.32) kernel crash on testfpuc.pp. I'll try and check this out on
> > a "real"
> > system presently, I've found UML to be pretty
On 2 aug 2006, at 00:47, Mark Morgan Lloyd wrote:
* If I run the tests (make full) on i386 2.0.2 I get a UML (User
Mode Linux on
2.4.32) kernel crash on testfpuc.pp. I'll try and check this out on
a "real"
system presently, I've found UML to be pretty robust but knowing
the effort
that's
I'm hoping to be able to sit down tomorrow and read more documentation, but for
the moment here's where I'm at.
* I can build i386 2.0.2 and appear to get something working out of it using
make cycle or make zipinstall. "Working" in this context is that it will
generate a runnable program from he
Tomas Hajny wrote:
Thanks Tomas, all good stuff :-)
I'll be back.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
___
fpc-pascal maillist - fpc-pascal@lists.freepas
Peter Vreman wrote:
> >* Are there further validation tests available?
>
> There is a testsuite available in SVN (or fpc.zip) under fpc/trunk/tests
Thanks. Got fpc/tests from the source which I presume is what you're referring
to.
> >* How can I build an installation bundle to move to a virgi
Peter Vreman wrote:
> At 17:06 31-7-2006, you wrote:
>>First, is this the best list to discuss this?
Yes for basic questions like "how to do this or that". When discussing
more complex stuff like "is this the right way for fixing problem XYZ
which popped up on SPARC", or "attached diff should fix
At 17:06 31-7-2006, you wrote:
First, is this the best list to discuss this?
I've got rather agressive filtering in my mailing list gateway. If
anybody tries
to send any attachments etc. to me please use markMLl.fpc2 .AT.
telemetry .DOT.
co .DOT. uk.
I admit readily to being a beginner as f
First, is this the best list to discuss this?
I've got rather agressive filtering in my mailing list gateway. If anybody tries
to send any attachments etc. to me please use markMLl.fpc2 .AT. telemetry .DOT.
co .DOT. uk.
I admit readily to being a beginner as far as FPC is concerned, and
inexperi
36 matches
Mail list logo
