Please help creating a Debian Ports TODO

Hi, I have started writing down all the tasks that are currently open for Debian Ports: > https://people.debian.org/~glaubitz/debian-ports-todo.txt Could someone who has the time turns this into a wiki page for Debian Ports? > https://wiki.debian.org/Ports?action=show&redirect=DebianPorts Tha

Re: R: Need help to make a Radeon HD6970 to work on a G5

and > windfarm spinning like a Jet. > > Kind Regards > Luigi > -- > *Da:* Link Electronics > *Inviato:* venerdì 13 settembre 2024 02:40 > *A:* luigi burdo > *Cc:* John Paul Adrian Glaubitz ; > debian-powerpc@lists.debian.org > *Oggetto:*

Re: R: Need help to make a Radeon HD6970 to work on a G5

next mesa > versions, > just sharing in case more people come up with a similar issue and a closure > for the topic. Thank you so much for taking the time to report the issue and help get it fixed! This is really the valuable effort that helps me keep the port afloat. Thanks, Adrian

Re: R: Need help to make a Radeon HD6970 to work on a G5

IGLX: Suspending AIGLX clients for VT switch [ 189.994] (II) UnloadModule: "libinput" [ 189.995] (II) UnloadModule: "libinput" [ 190.088] (II) Server terminated successfully (0). Closing log file. On Thu, Sep 12, 2024 at 7:45 AM luigi burdo wrote: > Hi John Paul, >

R: R: Need help to make a Radeon HD6970 to work on a G5

: Need help to make a Radeon HD6970 to work on a G5 Hi Luigi, On Thu, 2024-09-12 at 09:05 +, luigi burdo wrote: > this is my really old guide about install linux on PowerMac G5 (quad) but the > append to linux kernel are working today too. > I have on My Quad A Quadro and a 6570 H

Re: R: Need help to make a Radeon HD6970 to work on a G5

Hi Luigi, On Thu, 2024-09-12 at 09:05 +, luigi burdo wrote: > this is my really old guide about install linux on PowerMac G5 (quad) but the > append to linux kernel are working today too. > I have on My Quad A Quadro and a 6570 HD <-- for linux. Why not post the necessary commands to append t

R: Need help to make a Radeon HD6970 to work on a G5

Hello, this is my really old guide about install linux on PowerMac G5 (quad) but the append to linux kernel are working today too. I have on My Quad A Quadro and a 6570 HD <-- for linux. this is the link. hope it will help you [PPC] Instruction for Install Ubuntu & sons on PowerMac G5 Qu

Re: Need help to make a Radeon HD6970 to work on a G5

Hi Link, On Wed, 2024-09-11 at 19:44 -0300, Link Electronics wrote: > I would like to thank Adrian Glaubitz in advance for his many years of > continuing to support the PowerPC platform on Debian Linux. You're very welcome. I'm glad it's useful to you. > I have a PowerMac G5 Late 2005, been usin

Re: Need help to make a Radeon HD6970 to work on a G5

I forgot to say that I have installed firmware-linux-nonfree and firmware-amd-graphics, and the last lines of dsmeg actually are: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait time out. [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). On Wed, Sep

Need help to make a Radeon HD6970 to work on a G5

Hello everyone, I would like to thank Adrian Glaubitz in advance for his many years of continuing to support the PowerPC platform on Debian Linux. I have a PowerMac G5 Late 2005, been using it for a few months now and was using the geforce 6600LE video card that came with it, I compiled some projec

please help to do giveback on jimtcl

Hi, Could anyone help me to do a giveback for jimtcl[0] on ppc64el with new upload? It was built like this in previous uploads. Thanks in advance. BR, Bo [0]: https://buildd.debian.org/status/package.php?p=jimtcl

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, Am 23.10.23 um 21:59 schrieb Rene Engelhard: Am 29.10.23 um 11:13 schrieb Rene Engelhard: > (The workaround would be --without-java which I verified to work on > zelenka (see aboe), but this opens a can of worms. Not only disabling > some (built-in) features like the Report Builder but especi

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, Am 24.10.23 um 15:45 schrieb René Engelhard: Am 24. Oktober 2023 08:58:22 MESZ schrieb John Paul Adrian Glaubitz: Hello! On Mon, 2023-10-23 at 23:20 +0200, Rene Engelhard wrote: we're explicitly building with OpenJDK 8 while Debian builds with OpenJDK 17 [2] which might explain the diff

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, Am 24. Oktober 2023 08:58:22 MESZ schrieb John Paul Adrian Glaubitz : >Hello! > >On Mon, 2023-10-23 at 23:20 +0200, Rene Engelhard wrote: >> > > we're explicitly building with OpenJDK 8 while Debian builds >> > > with OpenJDK 17 [2] which might explain the different test results. >> >> Wh

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hello! On Mon, 2023-10-23 at 23:20 +0200, Rene Engelhard wrote: > > > we're explicitly building with OpenJDK 8 while Debian builds > > > with OpenJDK 17 [2] which might explain the different test results. > > Which is no option here... It may not be an option, but it might give you a pointer how

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, Am 23.10.23 um 23:06 schrieb John Paul Adrian Glaubitz: On Mon, 2023-10-23 at 21:59 +0200, Rene Engelhard wrote: since LibreOffice 7.6 (which added some more tests which were manual before to the automatic set) the testtools' bridge test fails: https://buildd.debian.org/status/fetch.php?p

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hello! On Mon, 2023-10-23 at 21:59 +0200, Rene Engelhard wrote: > since LibreOffice 7.6 (which added some more tests which were manual > before to the automatic set) the testtools' bridge test fails: > > https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=ppc64el&ver=4%3A7.6.2-3&sta

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, forgot to edit $SUBJECT. This is just ppc64el for now. (While s390x also has broken bridges --without-java doesn't seem to help here unfortunately :/) Regards, Rene Am 23.10.23 um 21:59 schrieb Rene Engelhard: Hi, since LibreOffice 7.6 (which added some more  tests which were m

help needed with LibreOffice Java bridge on s390x/ppc64el

Hi, since LibreOffice 7.6 (which added some more tests which were manual before to the automatic set) the testtools' bridge test fails: https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=ppc64el&ver=4%3A7.6.2-3&stamp=1697981409&raw=0 See the discussion upstream in https://lists.

Re: Please help reporting upstream bugs

On Sat, Jun 24, 2023 at 5:10 AM John Paul Adrian Glaubitz wrote: > > There are still many packages in Debian that fail to build from source on > PowerPC > targets, both 32-bit and 64-bit big-endian PowerPC, so I thought it might be > a good > idea to ask the community for he

Please help reporting upstream bugs

Hello! There are still many packages in Debian that fail to build from source on PowerPC targets, both 32-bit and 64-bit big-endian PowerPC, so I thought it might be a good idea to ask the community for help reporting these bugs upstream. The list of affected packages can be found by following

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

What is the size limit for attached files on this list? It seems my mail with attached log file archive is not coming through:( It's 4.2MB big Here is a dropbox link for it: https://www.dropbox.com/s/hi01grmov78boaf/install-log.tar.gz?dl=0 Hope it will work! Thanks! On 2022-10-15 19:31, G

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hello there, Did my last mail with attached gzip file reach the mailing list? (I've managed to archive it, thanks everyone for suggestions!) Asking because it is 4.2MB big archive, and I am not sure if it actually was sent, because it is still standing in my Outbox.. but it's also listed among "Sen

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

On 10/13/22 8:12 PM, vavagoga wrote: > Thanks for the suggestion! But... hmm... well.. I  tried to output it to > my home dir and also tried copying the whole install directory to the > desktop and also my home directory, but it keeps on saying I don't have > permission... So my guess is it looks l

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Thanks for the suggestion! But... hmm... well.. I  tried to output it to my home dir and also tried copying the whole install directory to the desktop and also my home directory, but it keeps on saying I don't have permission... So my guess is it looks like I don't actually have read permission

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

On 10/13/22 7:19 PM, vavagoga wrote: > Oh yeah, I have found it in /var/log/installer, thanks for the tip! > > But, when I try to compress it - it says: permission denied.. hmm.. why > is that? Is ther any work around for that? You don't have permission to write to that directory. Tell tar to out

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Oh yeah, I have found it in /var/log/installer, thanks for the tip! But, when I try to compress it - it says: permission denied.. hmm.. why is that? Is ther any work around for that? On 2022-10-14 01:23, John Paul Adrian Glaubitz wrote: The installer log is found in "/var/log/syslog" during in

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hi! On 10/14/22 00:12, vavagoga wrote: Well, sorry for being ignorant, I am quite new to Linux... No worries. Could you direct me to some tutorial or something which would help me to understand how to "switch to another virtual console" to access syslog? When the installer is ru

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hey, Adrian, thanks for your reply! Well, sorry for being ignorant, I am quite new to Linux... Could you direct me to some tutorial or something which would help me to understand how to "switch to another virtual console" to access syslog? I have tried following: I disconnected my

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hi! On 10/13/22 07:22, vavagoga wrote: An update about my problem with GRUB.. After wiping up disk and PRAM reset I was able to install GRUB, but it doesn't boot... If I start G5 when pressing "option" button it then shows GNU icon as boot option, but it's not booting from there - when I click

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

t;Select and Install Software" didn't install properly this time either, > but it was the closest to finish I ever got - it failed at 94% this time) > > Would appreciate any help, > > Thanks! > > > On 2022-10-06 00:44, Ben Westover wrote: >> Hello,

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

efreshes and nothing happens... Are there any steps I could take to fix it somehow?.. (BTW "Select and Install Software" didn't install properly this time either, but it was the closest to finish I ever got - it failed at 94% this time) Would appreciate any help, Thanks! On 2

Re: Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hello, On October 5, 2022 5:37:35 PM EDT, vavagoga wrote: >Hey there! > >I've been advised by kaiser.friedrich on youtube to join this list for more >detailed help with my problem.. > >I am trying to install Debian on my old G5, but installation always fail >during &q

Seeking for help with Debian 11 (2022-03-28 image) - can't install GRUB

Hey there! I've been advised by kaiser.friedrich on youtube to join this list for more detailed help with my problem.. I am trying to install Debian on my old G5, but installation always fail during "Select and install software" and then also during GRUB installation.. May

Re: Help with yaboot configuration

On 2/19/21 4:09 PM, John Paul Adrian Glaubitz wrote: Hi Bob! On 2/19/21 7:47 AM, Bob McGowan wrote: The kernel prints a bunch of normal type lines, then panics because it can't find the root device. It also reports a list of partitions it can find. The only disks are the ram disk (partition

Re: Help with yaboot configuration

On 2/19/21 8:13 AM, Jeffrey Walton wrote: On Fri, Feb 19, 2021 at 2:12 AM Bob McGowan wrote: Hello, I have a B&W G3 which I have upgraded to 1G RAM. It also has an Adaptec SCSI controller I added to use with a 32G LVD SCSI disk. It also has the original SCSI 9G SCSI disk on which I've been a

Re: Help with yaboot configuration

Hi Bob! On 2/19/21 7:47 AM, Bob McGowan wrote: > The kernel prints a bunch of normal type lines, then panics because it can't > find the root > device. It also reports a list of partitions it can find. The only disks > are the ram disk > (partitions 0-15) and sr0. > > This looks like it is mi

Re: Help with yaboot configuration

On Fri, Feb 19, 2021 at 2:12 AM Bob McGowan wrote: > > Hello, > > I have a B&W G3 which I have upgraded to 1G RAM. It also has an Adaptec > SCSI controller I added to use with a 32G LVD SCSI disk. It also has > the original SCSI 9G SCSI disk on which I've been able to install OSX > 10.4.2, initi

Help with yaboot configuration

Hello, I have a B&W G3 which I have upgraded to 1G RAM.  It also has an Adaptec SCSI controller I added to use with a 32G LVD SCSI disk.  It also has the original SCSI 9G SCSI disk on which I've been able to install OSX 10.4.2, initially. It has since upgraded to 10.4.11, if that is useful t

RE:Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Ok, in that case, I think that a comment in the d/rules files is enough in order to keep in mind that we have this issue with ppc64el.

RE:Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

> Well, the test is obviously broken and upstream currently can't be bothered > to fix > it on non-x86 targets. He will certainly have to do it at some point given > that ARM64 > is replacing more and more x86_64 systems, but I wouldn't bother, personally. so what is the best solution in order t

Re: Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

On 12/18/20 4:49 PM, Andreas Tille wrote: >> Well, the test is obviously broken and upstream currently can't be bothered >> to fix >> it on non-x86 targets. He will certainly have to do it at some point given >> that ARM64 >> is replacing more and more x86_64 systems, but I wouldn't bother, perso

RE:Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

> Yes, good catch. The spec file for the openSUSE package has this [1]: so it does not fit with our policy: do not hide problems ;) The problem is that I do not have enougt time to investigate... on a porter box

Re: Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

On Fri, Dec 18, 2020 at 04:44:04PM +0100, John Paul Adrian Glaubitz wrote: > > > > so it does not fit with our policy: do not hide problems ;) Well, we do not need to *hide* the problem. We can exclude the test and *document* the problem - say in a README.Debian on the affected architecture. >

Re: Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

On 12/18/20 4:42 PM, PICCA Frederic-Emmanuel wrote: >> Yes, good catch. The spec file for the openSUSE package has this [1]: > > so it does not fit with our policy: do not hide problems ;) > > The problem is that I do not have enougt time to investigate... on a porter > box Well, the test is o

Re: Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Hi Frederic! On 12/18/20 4:00 PM, PICCA Frederic-Emmanuel wrote: > looking at the Opensuze log, I can find this > > [ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3 > --ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or > test_shgo_scipy_vs_lmfit_2)' > [

RE:Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Hello looking at the Opensuze log, I can find this [ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3 --ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or test_shgo_scipy_vs_lmfit_2)' [ 97s] = test session starts

Re: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

On Fri, Dec 18, 2020 at 03:41:58PM +0100, John Paul Adrian Glaubitz wrote: > On 12/18/20 3:19 PM, Andreas Tille wrote: > > I wonder whether we could get some help from PowerPC team to solve this > > issue. If we can not get that test working I see only two options: > >

Re: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

On 12/18/20 3:19 PM, Andreas Tille wrote: > I wonder whether we could get some help from PowerPC team to solve this > issue. If we can not get that test working I see only two options: > >1. Skip this specific test >2. Exclude ppc64el from architecture list > > Any

[Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Control: tags -1 -upstream Control: tags -1 help Hi, I wonder whether we could get some help from PowerPC team to solve this issue. If we can not get that test working I see only two options: 1. Skip this specific test 2. Exclude ppc64el from architecture list Any help would be really

Re: help with diagnosing rust SEGV on powerpc (using porterbox perotto.debian.net)

bugs.debian.org/953648 Pointers for further debugging help would be welcome! I looked into seeing whether upstream's current version of bindgen would exhibit the same problem (debian has bindgen 0.51.1 due to rust-nettle-sys and rust-onig-sys having hard-coded dependencies on that version, afa

help with diagnosing rust SEGV on powerpc (using porterbox perotto.debian.net)

Hi PowerPC porters-- i'm trying to debug a build failure on powerpc using a porterbox: https://buildd.debian.org/status/fetch.php?pkg=rust-nettle-sys&arch=powerpc&ver=2.0.4-2&stamp=1580935398&raw=0 Upstream is helpful and responsive but i'm getting a bit stuck on the porterbox itself: https://g

Re: Help requested for htslib build failure on ppc64el

Hi Michael! On 01/09/2019 06:08 PM, Michael Crusoe wrote: https://buildd.debian.org/status/package.php?p=htslib&suite=experimental http://metadata.ftp-master.debian.org/changelogs/main/h/htslib/htslib_1.9-9~floatingpoint0_changelog

Re: Help requested for htslib build failure on ppc64el

https://buildd.debian.org/status/package.php?p=htslib&suite=experimental http://metadata.ftp-master.debian.org/changelogs/main/h/htslib/htslib_1.9-9~floatingpoint0_changelog Seems to work after all! Maybe a qemu bug? -- Michael R. Crusoe Co-founder & Lead, Common Workflow Language project https:

Re: Help requested for htslib build failure on ppc64el

Ping. On 01/04/2019 08:01 PM, Gustavo Romero wrote: Hi Michael, Thanks for the diff and the additional information on the failure. Since I could not reproduce the issue locally, would you mind to point a buildd machine (I tried the buildd logs for htslib without success) where it fails, plea

Re: Help requested for htslib build failure on ppc64el

Hi Michael, Thanks for the diff and the additional information on the failure. Since I could not reproduce the issue locally, would you mind to point a buildd machine (I tried the buildd logs for htslib without success) where it fails, please? Thank you. Regards, Gustavo On 01/02/2019 02:41

Re: Help requested for htslib build failure on ppc64el

În mie., 2 ian. 2019 la 15:27, Gustavo Romero a scris: > Hello Michael, > > On 12/31/2018 02:50 PM, Michael Crusoe wrote: > > În lun., 31 dec. 2018 la 06:42, Gustavo Romero < > grom...@linux.vnet.ibm.com > a scris: > > diff --git a/sam.c b/sam.c > > inde

Re: Help requested for htslib build failure on ppc64el

On 01/02/2019 11:27 AM, Gustavo Romero wrote: Hello Michael, On 12/31/2018 02:50 PM, Michael Crusoe wrote: În lun., 31 dec. 2018 la 06:42, Gustavo Romero mailto:grom...@linux.vnet.ibm.com>> a scris:     diff --git a/sam.c b/sam.c     index aa94776..23233a0 100644     --- a/sam.c     +++ b/sam.c

Re: Help requested for htslib build failure on ppc64el

Hello Michael, On 12/31/2018 02:50 PM, Michael Crusoe wrote: În lun., 31 dec. 2018 la 06:42, Gustavo Romero mailto:grom...@linux.vnet.ibm.com>> a scris: diff --git a/sam.c b/sam.c index aa94776..23233a0 100644 --- a/sam.c +++ b/sam.c @@ -1408,7 +1408,7 @@ int sam_parse1(kstri

Re: Help requested for htslib build failure on ppc64el

În lun., 31 dec. 2018 la 06:42, Gustavo Romero a scris: > Hi Michael, Steffen, > Hey Gustavo, > On 12/30/2018 05:35 PM, Steffen Möller wrote: > > I admit this is a bit over my head. It may be worthwhile to peek a boo > at the latest gcc snapshots > https://packages.debian.org/de/sid/ppc64/gcc

Re: Help requested for htslib build failure on ppc64el

Hi Gustavo, On 31.12.18 05:42, Gustavo Romero wrote: Hi Michael, Steffen, [...] That said, I dug a bit further and it looks like that sam_parse1() is actually generating a different value for the floats in question, so when they are loaded back for the comparison they are already screwed up,

Re: Help requested for htslib build failure on ppc64el

Hi Michael, Steffen, On 12/30/2018 05:35 PM, Steffen Möller wrote: I admit this is a bit over my head. It may be worthwhile to peek a boo at the latest gcc snapshots https://packages.debian.org/de/sid/ppc64/gcc-snapshot/download that may have a fix for that issue already. I don't think it's

Re: Help requested for htslib build failure on ppc64el

Hi Michael, I admit this is a bit over my head. It may be worthwhile to peek a boo at the latest gcc snapshots https://packages.debian.org/de/sid/ppc64/gcc-snapshot/download that may have a fix for that issue already. As a workaround to quickly proceed with what you are really after, and fo

Re: Help requested for htslib build failure on ppc64el

Hi Michael, On 12/27/2018 04:35 PM, Gustavo Romero wrote: On 12/27/2018 12:41 PM, Michael Crusoe wrote: https://buildd.debian.org/status/fetch.php?pkg=htslib&arch=ppc64el&ver=1.9-7&stamp=1545236716&raw=0 Can I get some assistance here? Rebuilding using Qemu and the earlier source packages pro

Re: Help requested for htslib build failure on ppc64el

Hi, On 12/27/2018 12:41 PM, Michael Crusoe wrote: https://buildd.debian.org/status/fetch.php?pkg=htslib&arch=ppc64el&ver=1.9-7&stamp=1545236716&raw=0 Can I get some assistance here? Rebuilding using Qemu and the earlier source packages produces the same error, so maybe this is a regression in

Help requested for htslib build failure on ppc64el

https://buildd.debian.org/status/fetch.php?pkg=htslib&arch=ppc64el&ver=1.9-7&stamp=1545236716&raw=0 Can I get some assistance here? Rebuilding using Qemu and the earlier source packages produces the same error, so maybe this is a regression in the compiler? -- Michael R. Crusoe Co-founder & Lead

Please help: systemctl: error while loading shared libraries

Hi all! I am a user of Debian PowerPC. For several months, I receive the following error: systemctl: error while loading shared libraries: R_PPC_REL24 relocation at 0x004a8880 for symbol `gcry_control' out of range My system: Openwrt 15.05, LXC container OS: Debian Linux 10.0 (within LXC

Re: Help needed for small assembler script for the iraf package

8<--- > > The "zdojmp" counterpart is a portable C function. > > I created a small repository [2] that contains the assembler I collected > so far as well as two test programs. > > However, I have no idea how to write the same for the

Help needed for small assembler script for the iraf package

ns the assembler I collected so far as well as two test programs. However, I have no idea how to write the same for the 64-bit platform ppc64el. Maybe someone could help me here? Preferably under the IRAF license [3], so that it can be included upstream later. There is no direct request from the

Re: Trying to compile Mac-on-Linux 0.9.72.1 - various errors; Help appreciated

What I did: 1) Download MOL from https://sourceforge.net/projects/mac-on-linux/files/mac-on-linux/mol-0.9.72.1/mol-0.9.72.1.tar.bz2/download and unpack, I used /usr/local/src/ for unpacking. 2) Get dependencies, requirements: a) apt install build-essential fakeroot devscripts b) ./autogen

Trying to compile Mac-on-Linux 0.9.72.1 - various errors; Help appreciated

Hello! I'm trying to compile Mac-on-Linux (MOL) on a current Debian unstable powerpc system. It hangs and I don't know what's wrong, so HELP is highly appreciated. Before you ask: yes, I know that MOL is likely to fail on a recent Linux system. Anyway, the error doesn'

Still unresolved upstream, help needed

Cc'd to debian-powerpc On Fri, 13 Jan 2017 10:17:18 + Ghislain Vaillant wrote: control: forwarded -1 https://github.com/h5py/h5py/issues/817 Upstream is running out of ideas, so any help from the team would be warmly welcome. Cheers, Ghis

Removal of powerpc as release architecture - would a donated Power Mac help?

ely something a community can live with. My question as a pure user is: would it help the devs if they got a Power Mac G4 as a donation? As a user there isn't really much else to do but to support the distribution by using it, spreading the word and donating some of the aff

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Frederic Bonnard a écrit le 26/10/2015 14:19 : > Gilles, > that worked, see attached, the screenshot. Yay! Thanks again for your help :) _g. > On Fri, 23 Oct 2015 08:34:06 +0200, Frederic Bonnard > wrote: >> Hey Gilles, >> yes sure. I'll try that today, and will l

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Hey Gilles, yes sure. I'll try that today, and will let you know about it. F. On Thu, 22 Oct 2015 22:46:54 +0200, Gilles Filippini wrote: > Hi Frédéric, > > Is there a chance you could give a try at launching scilab 5.5.2-2~exp3 > currently in experimental. This is why I worked on bluegen2 and

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Hi Frédéric, Is there a chance you could give a try at launching scilab 5.5.2-2~exp3 currently in experimental. This is why I worked on bluegen2 and libjobl2-java (see #798652). My test on a ppc64el porter box with VNC crashed the X server. Thanks, _g. signature.asc Description: OpenPGP digi

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Hi Frédéric, Frederic Bonnard a écrit le 16/10/2015 17:35 : > Hi Gilles, > sorry for the time it took, but I struggled hard to have a graphical setup > working and now that I did it, maybe I could have something easier. > For the short answer, check the attached png : it worked. Great \o/ > The

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Le 2015-10-14 17:07, Frederic Bonnard a écrit : Hi Gilles, here is what I get when trying to run the test : -- debian@abanc:~$ java -cp .:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jogl2.jar OneTriangleAWT libEGL warning: failed to open /dev/dri/card0 libEGL warning: DRI2: failed to open i96

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Hi Gilles, here is what I get when trying to run the test : -- debian@abanc:~$ java -cp .:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jogl2.jar OneTriangleAWT libEGL warning: failed to open /dev/dri/card0 libEGL warning: DRI2: failed to open i965 (search paths /usr/lib/powerpc64le-linux-gnu/d

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Hi Frédéric, Le 2015-10-09 23:28, Gilles Filippini a écrit : Le 2015-10-09 15:47, Gilles Filippini a écrit : Le 2015-10-09 14:17, Frederic Bonnard a écrit : Would you mind building from the source packages? I should have them ready by this evening. Sources are ok for me. This evening, I won'

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

Le 2015-10-09 15:47, Gilles Filippini a écrit : Le 2015-10-09 14:17, Frederic Bonnard a écrit : Would you mind building from the source packages? I should have them ready by this evening. Sources are ok for me. This evening, I won't be next to the machine. Will a remote X display be ok for the

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

n: OpenJDK Runtime Environment (7.0_85-b01) (build >> 1.7.0_85-b01) >> # Java VM: OpenJDK 64-Bit Server VM (24.85-b03 mixed mode linux-ppc64 >> compressed oops) >> # Derivative: IcedTea 2.6.1 >> # Distribution: Debian GNU/Linux unstable (sid), package 7u85-2.6.1-3 &g

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

5ee284, pid=9911, > >> tid=70366626443680 > >> # > >> # JRE version: OpenJDK Runtime Environment (7.0_85-b01) (build > >> 1.7.0_85-b01) > >> # Java VM: OpenJDK 64-Bit Server VM (24.85-b03 mixed mode linux-ppc64 > >> compressed oops) > >>

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

: IcedTea 2.6.1 # Distribution: Debian GNU/Linux unstable (sid), package 7u85-2.6.1-3 # Problematic frame: # V [libjvm.so+0x54e284] jni_GetLongField+0x74 And I'm unable to state whether this is due to my clumsy VNC configuration or to a broken gluegen / jogl build. Any help appreciated. Thanks in advance, _g.

Re: Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

03 mixed mode linux-ppc64 > compressed oops) > # Derivative: IcedTea 2.6.1 > # Distribution: Debian GNU/Linux unstable (sid), package 7u85-2.6.1-3 > # Problematic frame: > # V [libjvm.so+0x54e284] jni_GetLongField+0x74 > > And I'm unable to state whether this is due to

Help with porting opengl java libraries (gluegen2 / libjogl2-java) to ppc64el

pc64 compressed oops) # Derivative: IcedTea 2.6.1 # Distribution: Debian GNU/Linux unstable (sid), package 7u85-2.6.1-3 # Problematic frame: # V [libjvm.so+0x54e284] jni_GetLongField+0x74 And I'm unable to state whether this is due to my clumsy VNC configuration or to a broken gluege

Help with src:openexr

Dear PowerPC gurus, I am looking for a little help with src:openexr. The test suite is currently failing on every single big endian arch we have: https://buildd.debian.org/status/package.php?p=openexr&suite=experimental I've been merging a patch from fedora which claims to fix big-endi

Re: libgc update, your help needed!

YunQiang Su writes: > Oh, no. mips64el misses more symbols. :( Not an issue and thanks for the logs! > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774885 > should also have been fixed. In theory it should build against the system's libatomic-ops (at least now). I'll try to keep an eye on

Re: libgc update, your help needed!

On Sat, Aug 22, 2015 at 9:02 PM, Christoph Egger wrote: > Hi! > > YunQiang Su writes: >> I just test in on another machine manually. >> it has not the gctest fail. :0: > > Thanks for the prompt reply! Was that on a porterbox or some personal > machine? I test it on personal machines. > >> On mi

Re: libgc update, your help needed!

Hi! YunQiang Su writes: > I just test in on another machine manually. > it has not the gctest fail. :0: Thanks for the prompt reply! Was that on a porterbox or some personal machine? > On mips/mips64el, it has the same symbol files problem. Exactly the same? would you mind sending the buildlog

Re: libgc update, your help needed!

On Sat, Aug 22, 2015 at 4:16 PM, Christoph Egger wrote: > Hi folks! > > I've prepared a new version of libgc in experimental which I intent to > upload to unstable soon. Unfortunately it FTBFS on (one of) your > architectures (arm64, ppc64el hangs ; mipsel fails a test). It would be > great if y

libgc update, your help needed!

Hi folks! I've prepared a new version of libgc in experimental which I intent to upload to unstable soon. Unfortunately it FTBFS on (one of) your architectures (arm64, ppc64el hangs ; mipsel fails a test). It would be great if you can point me to a upstream commit (or a patch) to backport so lib

Help with Debian Site

I started doing some clean up work on the Debain PPC/FAQ wiki. It is really outdated and needs work. If any is intrested in helping out you are more than welcome. Thanks! -- Herminio Hernandez Jr pgpd01z7Fzcem.pgp Description: PGP signature

Re: HELP: test kernel patches on the real thing

On Fri, 5/8/15, Wolfram Sang wrote: >Very welcome! Did you work a little more with >this machine & kernel. Fan etc still working correctly? Yes, everything's working as it should. >Can you point people to this patch in #714345 and >update the bug until it can be closed? Sure. Thanks once ag

Re: HELP: test kernel patches on the real thing

> >So, did you have sound? This message "Failed to register i2c > >client keywest at 0x35 (-16)" is gone now... > > I forgot to check! I was just happy the pretty dmesg output > looked differnt. :)) > Anyway, now that I do check, I have sound! For the first time > in two years I have a Jes

Re: HELP: test kernel patches on the real thing

On Wed, 5/6/15, Wolfram Sang wrote: >So, did you have sound? This message "Failed to register i2c >client keywest at 0x35 (-16)" is gone now... I forgot to check! I was just happy the pretty dmesg output looked differnt. Anyway, now that I do check, I have sound! For the first time in two y

Re: HELP: test kernel patches on the real thing

> Attached are the dmesg outputs, first for the patch below alone, and second > for both patches. So, did you have sound? This message "Failed to register i2c client keywest at 0x35 (-16)" is gone now... > By the way, patch told me the patch below is malformed at line 21, > "static bool i2c_p

Re: HELP: test kernel patches on the real thing

ually (and triple checked). Regards, Dan On Mon, 5/4/15, Wolfram Sang wrote: Subject: Re: HELP: test kernel patches on the real thing To: "Dan DeVoto" Cc: debian-powerpc@lists.debian.org Date: Monday, May 4, 2015, 3:09 PM On Mon, Ma

Re: HELP: test kernel patches on the real thing

On Mon, May 04, 2015 at 01:58:28PM -0700, Dan DeVoto wrote: > >Can you send me the device tree of your machine in the > >mean time? > > Sure, thanks for working on this, but I'm not sure what device > tree refers to. Is there a specific command output or text file > I should send you? Let's sk

Re: HELP: test kernel patches on the real thing

Mon, 5/4/15, Wolfram Sang wrote: Subject: Re: HELP: test kernel patches on the real thing To: "Dan DeVoto" Cc: debian-powerpc@lists.debian.org Date: Monday, May 4, 2015, 10:47 AM > I'm the original filer of Debian bug #714345. >  I applied your sound patch and com

  1   2   3   4   5   6   7   8   9   10   >