----- Original Message -----
From: "Peter Robinson" <pbrobinson(a)gmail.com>
To: "Jakub Cajka" <jcajka(a)redhat.com>
Cc: ppc(a)lists.fedoraproject.org
Sent: Saturday, January 23, 2016 4:52:36 AM
Subject: Re: Golang-1.6 in Fedora 24
>> On Thu, Jan 21, 2016 at 3:48 PM, Jakub Cajka <jcajka(a)redhat.com> wrote:
>> > Hello,
>> > I have submitted change proposal[1] to re-base golang in Fedora 24,
>> > with
>> > re-based golang support for PowerPC should be considerably
>> > improved[2].
>> >
>> > For testing. I have prepared COPR repository with pre-release
>> > golang[3](for ppc64le only). You can enable the repository easily with
>> > command "dnf copr enable jcajka/golang1.6" and then "dnf
install
>> > golang".
>> >
>> > To test golang on ppc64 you need to build it yourself. Download the
>> > srpm
>> > from up mentioned COPR repo page[4]. And build it using mock with
>> > command similar to the following "mock -r fedora-rawhide-ppc64
>> > --resultdir results golang-1.6.src.rpm", after the build finishes,
>> > results(rpms to be installed) will be place in to the
"results"
>> > directory.
>>
>> I believe I'll need to coordinate with you to get a binary set
>> (ppc64/ppc64le/noarch/src rpms) that are identical for bootstrapping
>> of golang to import into koji. For the we'll need to ensure the build
>> is a lower NVR than the first 1.6.0 build that lands in primary (I
>> usually use 0.1 ie if the first primary build will be
>> golang-1.6.0-1.fc24 built the bootstrap build golang-1.6.0-0.1.fc24).
>>
>
> There is no need for pre-build binaries from golang side, as gcc-go should
> work just fine for the bootstrap of golang and I thought that it is not
> necessary from "koji" side.
I thought as of 1.5 you had to cross compile golang with golang as
they'd dropped the ability to bootstrap a new arch with gcc-go and
hence you needed to cross compile first to get a working compiler. We
certainly had to do that for aarch64 in 1.5
I not sure about the reasons for that at that time. Building golang1.5+, requires any
go1.4+ compiler, which gcc-go(was gcc5+ available back then?) satisfies and from my
experience it "just" works(for this case).
> My plan was to built golang with "bootstrap" option for %{power64}, and
> then stage spec with it disabled(no other change, waiting for mass rebuild
> bump) as mass re-build would rebuild it "regular" way(golang bootstrapped
> with gcc-go should be usable same way as "regularly" built one).
The general practice is to enable the flag across all arches
?
If any of you don't see any issues with it, I will start pushing the changes,
including the default compiler switch, tomorrow.
>
> > In details:
> >
> > - push re-based golang
> >
> > - change macros for %{power64}(if not disapproved), do builds
> > (go-srpm-macros, go-compilers)
> >
> > - disable bootstrap option in golang on %{power64}(no build sent to koji)
> >
> > - wait for mass rebuild
> >
> > Does it sound right?
> >
> >>
> >> > Please test and provide any feedback.
> >> >
> >> > Also this brings up question of switching default Go compiler to
> >> > golang
> >> > for both ppc64/ppc64le in Fedora 24. What are yours opinions about
it?
> >>
> >> I think we should do it now and just get on with it :)
> >>
> > :)
>