On 03/09/16 14:15, Graham Inggs wrote:
A wild stab in the dark: don't we need to binNMU lazarus before we can
build packages with it?
I'd say yes, in that build log it looks like it's lazbuild which is
crashing. So yes a binnmu of lazarus seems the next step.
Then, don't we need to binNMU
Hi Graham,
On 03-09-16 15:15, Graham Inggs wrote:
> Of course you mean s/doublecmd/ddrescueview/ there.
Indeed, duh...
> A wild stab in the dark: don't we need to binNMU lazarus before we can
> build packages with it?
Hmm, forgot about that. You are probably right.
> Then, don't we need to
On 3 September 2016 at 13:47, Paul Gevers wrote:
> Unfortunately it doesn't seem to solve all issues. At least doublecmd
> now only FTBFS on powerpc (yes, fpc installed fine):
>
> An unhandled exception occurred at $0FE281F0:
> EAccessViolation:
> $0FE281F0
> $0FE36604
>
Hi
Unfortunately it doesn't seem to solve all issues. At least doublecmd
now only FTBFS on powerpc (yes, fpc installed fine):
An unhandled exception occurred at $0FE281F0:
EAccessViolation:
$0FE281F0
$0FE36604
$0FDED188
$0FDED25C
See
On 03/09/16 03:36, peter green wrote:
On 02/09/16 23:05, Abou Al Montacir wrote:
Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++
On 02/09/16 23:05, Abou Al Montacir wrote:
Upstream suggests the following patch which may be temporary:
diff --git a/rtl/linux/powerpc/cprt0.as b/rtl/linux/powerpc/cprt0.as
index e237d8d..a5672e3 100644
--- a/rtl/linux/powerpc/cprt0.as
+++ b/rtl/linux/powerpc/cprt0.as
@@ -88,12 +88,8 @@
Hi All,
On Mon, 2016-08-29 at 11:59 +0200, Abou Al Montacir wrote:
...
> Please hold on, upstream fond the issue.
> The issue is related to longjump in cprt0.as.
> They are going to give us a fix in the next few days.
Upstream suggests the following patch which may be temporary:diff --git
Hi All,
On Sun, 2016-08-28 at 18:13 +0200, Paul Gevers wrote:
> Hi
>
> On 25-08-16 21:21, Paul Gevers wrote:
> > I have a fpc package
> > available on debomatic¹ that only for powerpc goes back to the old
> > version of fpcmkcf and I confirm that that works. So I agree with
> > Graham, that this
Hi
On 25-08-16 21:21, Paul Gevers wrote:
> I have a fpc package
> available on debomatic¹ that only for powerpc goes back to the old
> version of fpcmkcf and I confirm that that works. So I agree with
> Graham, that this probably just hides the issue that is to be also found
> elsewhere, at least
Hi Paul,
>Using buildid for compat level >= 9
>dpkg-gencontrol: warning: Built-Using field of package
>lazarus-ide-1.6: unknown substitution variable ${bu:version}
>dpkg-gencontrol: warning: can't parse dependency fpc (= )
>dpkg-gencontrol: error: error occurred while parsing Built-Using field:
On 18 August 2016 at 20:50, Paul Gevers wrote:
> @Graham, I suggest you also get this done in Ubuntu soon, such that the
> next release has the latest fpc from Debian again.
Steve Langasek starting working through LP: #1562480 [1] and removing
powerpc binaries.
He found a
Hi
On 25-08-16 09:29, Graham Inggs wrote:
> I also understood that many of the executables (if not all?) that were
> built with the broken version of fpc would be broken.
Well, at least pasdoc isn't broken. I just tried it and it works.
> So fpcmkcfg-3.0.0 is just one of many that will crash,
I think Alexander is on to something here:
> Look like https://bugs.launchpad.net/bugs/1570055 is the same bug
> (or at least related) and the bug is in glibs.
>
> 1) segfault during program exit in _IO_wsetb after output to stdout
> 2) same platform powerpc, same glibs version 2.23 but not
Hi,
>Good finding, but I miss the words "on powerpc" ;) .
true, obviously only powerpc (partch.debian.org) was tested :)
>That file is not extremely big and the change is not incredibly large.>We
>should be able to nail this down for the FTBFS. Still, the issue may
>be outside this file as
Hi Gianfranco,
On 24-08-16 14:38, Gianfranco Costamagna wrote:
> Interesting findings:
> fpcmkcfg-2.6.4 is *not* failing in neither Jessie, nor Sid.
Good finding, but I miss the words "on powerpc" ;) .
> for this, I copied the file from 2.6.4 over the one from 3.0.0, and I did a
> rebuild.
>
control: reopen -1
ok, after digging into the issue I did:
create a jessie-backport chroot for building
create a sid chroot for testing fpcmkcfg- binaries
(it crashes just by running the tool with no parameters).
Interesting findings:
fpcmkcfg-2.6.4 is *not* failing in neither Jessie, nor Sid.
On 23/08/16 19:28, Paul Gevers wrote:
Hi Peter,
On 23-08-16 04:52, peter green wrote:
I tried building the new package in a jessie chroot (which worked with a
few minor packaging tweaks), then running the results in a sid chroot
(unfortunatley I was doing this on a porterbox so I couldn't
Hi Peter,
On 23-08-16 04:52, peter green wrote:
> I tried building the new package in a jessie chroot (which worked with a
> few minor packaging tweaks), then running the results in a sid chroot
> (unfortunatley I was doing this on a porterbox so I couldn't install them).
That was the same
On 22/08/16 21:01, Paul Gevers wrote:
I am including the patch right now in our packaging. I'll upload it to
the archive and I'll then continue bootstrapping on powerpc. Give me a
couple of days. Feel free to bootstrap powerpc before I do.
I tried building the new package in a jessie chroot
Hi,
On 22-08-16 17:49, Abou Al Montacir wrote:
> It seems that this is now fixed!
>
>>> Can you please check if r34366 resolves the problem?
>
>>Sorry, I made a mistake, you need r34368 as well.
>
> Can anybody test this?
I am including the patch right now in our packaging. I'll upload it to
Dear All,
It seems that this is now fixed!
>Am 22.08.2016 um 12:22 schrieb Florian Klämpfl:
>>> Am 22.08.2016 um 10:10
schrieb Florian Klämpfl:
>>> Thanks for the reminder, I got stuck with the QEMU
setup, but I have
>>> finally a running one as well as a fix. If make all works,
I will commit it
Hi,
>@Graham, I suggest you also get this done in Ubuntu soon, such that the
>next release has the latest fpc from Debian again.
I reused the same bug as before:
https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1595485G.
Hi all,
On 12-08-16 22:51, Paul Gevers wrote:
> If no solution to this issue is created soon, I think it is best to
> acknowledge that we (all involved) can't practically fix the issue
> (caused by lack of skills and/or time) and we'll need request removal of
> the whole fpc stack in sid and
Hi Adam,
During Debconf you found out what the issue was with fpc on powerpc
(glibc update related). We haven't seen a solution yet (I expect you are
too busy), but could you at least share your current knowledge such that
others could investigate further and e.g. check that upstream doesn't
24 matches
Mail list logo