ppc June 2017

ppc@lists.fedoraproject.org

2 participants
3 discussions

ppc64le: c++: internal compiler error: Killed (program cc1plus)
by Sérgio Basto 10 Mar '19

10 Mar '19

Hello ppc list , I don't know where I should report this issue, if this is not the correct place, please tell me where it is, thanks. I can't build opencv-3.1 on ppc64le the builds always ends with : {standard input}: Assembler messages: {standard input}:36678: Warning: end of file not at end of a line; newline inserted {standard input}:39048: Error: unknown pseudo-op: `.l295' {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive c++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. make[2]: *** [modules/cvv/CMakeFiles/opencv_cvv.dir/src/view/rawview.cpp.o] Error 4 make[2]: *** Waiting for unfinished jobs.... Build logs: https://copr.fedorainfracloud.org/coprs/sergiomb/opencv/build/183181/ https://copr-be.cloud.fedoraproject.org/results/sergiomb/opencv/fedora- 23-ppc64le/00183181-opencv/build.log.gz https://copr-be.cloud.fedoraproject.org/results/sergiomb/opencv/fedora- rawhide-ppc64le/00181899-opencv/build.log.gz Best regards, -- Sérgio M. B.

4 7

Review of Power architecture specific packages
by Dan Horák 26 Jun '17

26 Jun '17

Hi all, recently a bug against powerpc-utils [1] has been filed as a result of the modularity work to minimize the base runtime environment. This lead us to think about the install-time and run-time dependencies of architecture specific packages as a whole. There is now a wiki page [2] to collect the information, before we make changes in Fedora - in the lorax templates for the installer, in the comps file for "installed by default", etc. The result should be a list of packages and package changes to allow the minimal image to boot and a definition of "architecture add-on module" with with management, monitoring, etc. tools. Feel free to edit the wiki or post your results to the list. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1463749 [2] https://fedoraproject.org/wiki/Architectures/PowerPC/Packages Dan

1 0

Re: [golang-dev] Re: instruction sets used for Power
by Jakub Cajka 19 Jun '17

19 Jun '17

----- Original Message ----- > From: "'John Paul Adrian Glaubitz' via golang-dev" <golang-dev(a)googlegroups.com> > To: "Lynn Boger" <laboger(a)gmail.com>, "golang-dev" <golang-dev(a)googlegroups.com> > Sent: Saturday, June 17, 2017 8:37:34 PM > Subject: Re: [golang-dev] Re: instruction sets used for Power > > On 06/16/2017 02:26 PM, Lynn Boger wrote: > > Support for the ppc64 v1 ABI was never added to golang. That means the > > types of linking modes that can be used with golang on ppc64 big endian > > are limited, > > preventing many of the commonly used Go applications to build or run on > > ppc64 big endian. None of the newer buildmodes (pie, shared, etc.) are > > supported on > > ppc64 big endian because of this. While there have been a few complaints > > on this, there haven't been many. To me that is an indicator of how > > golang on > > ppc64 big endian is used. I believe if there were serious users for ppc64 > > big endian, there would have been more requests for full linker support. > > At least checking for packages with "golang" in their name, there don't seem > to be many Go > packages on ppc64 which fail to build. In fact, I can only count four: > > glaubitz@wuiet:~$ wanna-build --arch ppc64 --list build-attempted | grep -i > golang > misc/golang-github-docker-docker-credential-helpers_0.5.0-2 by > buildd_ppc64-kapitsa [extra:uncompiled:calprio{32}:days{39}] > misc/golang-github-docker-libnetwork_0.8.0-dev.2+git20170202.599.45b4086-1 by > buildd_ppc64-ookuninushi [extra:uncompiled:calprio{32}:days{24}] > misc/dh-make-golang_0.0~git20161120.0.71f5e23-1 by buildd_ppc64-ookuninushi > [extra:uncompiled:bp{-10000}:calprio{-9968}:days{96}] > misc/golang-gogoprotobuf_0.3+git20170120.144.265e960d-1 by > buildd_ppc64-kapitsa [extra:uncompiled:bp{-10000}:calprio{-9968}:days{96}] > glaubitz@wuiet:~$ > > > golang for ppc64 big endian was always documented as an "experimental port" > > and has never been available on the golang.org/dl website. > > Being able to download a binary build isn't necessary when Fedora, Debian and > openSUSE are > building Golang packages for ppc64 by default. > > > gccgo is a good option, and it can be targeted for power5 or power8. > > But is it 100% on par with Golang? gccgo isn't of much use if I can > only build a fraction of the important Go packages like Docker, rkt > or Kubernetes with it. To be honest I'm currently considering proposal of drop(stop building) of all Go based packages in Fedora for ppc64 architecture starting from next Fedora release(unless Fedora moves to be p8+). Gccgo could be a way forward but it will require substantial time investment that I don't feel good about requiring from fellow packagers(especially as Go packaging in Fedora is mostly one man(jchaloup's) show, when not counting docker, kubernetes, openshift and golang package maintainers) and that I can't personally do(due to time constrains). Gccgo mostly worked(hm.. haven't checked on it in a while), but I'm afraid that among many things some packages/projects which use their own build scripts are quiet strict in their expectations/assumptions and will most probably require some hacking(*looks with dread at kubernetes and its derivates*). As of ppc64 port. Will gc get ppc64 extld/Cgo support? If I have followed the discussions properly(might have missed something) it will be at power ABIv2 level, right?, which seems to me as bit odd as most of the ppc64 distribution(operation systems) that I know are ABIv1 and AFAIK ABI is incompatible, right? JC PS: BCC'ed fedora's ppc ML(ppc(a)lists.fedoraproject.org), to take any "Fedora" discussion there. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaubitz(a)debian.org > `. `' Freie Universitaet Berlin - glaubitz(a)physik.fu-berlin.de > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > > -- > You received this message because you are subscribed to the Google Groups > "golang-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-dev+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

ppc June 2017