Re: srpm rebuilding on RISC-V fedora image

2021-03-08 Thread Billa Surendra 
Dear David,

Thanks for your help.. I have successfully created RISC-V arch temporary config 
file for MOCK. Tried rebuilding SRPM using MOCK, its successfully rebuilt.

Thanks
BIlla
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: srpm rebuilding on RISC-V fedora image

2021-03-03 Thread David Abdurachmanov 
On Thu, Mar 4, 2021 at 8:29 AM Billa Surendra  wrote:
>
>
> Without Correcting right URL to fedora-33-riscv64.cfg file we can not use 
> MOCK for rebuilding SRPM's for RISC-V architecture.  Can anyone please 
> suggest what I can do now to correct it?. How can I contact MirrorManager to 
> correct the URL to the right location?.

Koji generated disto-repos for Fedora/RISCV are here, for example,
http://fedora.riscv.rocks/repos-dist/f33/latest/
http://fedora.riscv.rocks/repos-dist/rawhide/latest/

There is no official mock config for Fedora/RISCV, so you need to copy
one of the existing configs (for example, aarch64) and adjust (mainly
arch and correct repository URL)

You can also pull directly from Koji working repos too, for example,
http://fedora.riscv.rocks/repos/f33-build/latest/

For example here is a config generated by Koji build system:

[root@hifive koji]# cat f33-build-554869-65360.cfg
# Auto-generated by the Koji build system

# Koji buildroot id: 554869
# Koji buildroot name: f33-build-554869-65360
# Koji repo id: 65360
# Koji tag: f33-build

config_opts['basedir'] = '/var/lib/mock'
config_opts['chroot_setup_cmd'] = 'groupinstall srpm-build'
config_opts['chroothome'] = '/builddir'
config_opts['dnf_warning'] = True
config_opts['package_manager'] = 'dnf'
config_opts['root'] = 'f33-build-554869-65360'
config_opts['rpmbuild_networking'] = True
config_opts['rpmbuild_timeout'] = 604800
config_opts['target_arch'] = 'riscv64'
config_opts['use_host_resolv'] = True
config_opts['yum.conf'] =
'[main]\ncachedir=/var/cache/yum\ndebuglevel=1\nlogfile=/var/log/yum.log\nreposdir=/dev/null\nretries=20\nobsoletes=1\ngpgcheck=0\nassumeyes=1\nkeepcache=1\ninstall_weak_deps=0\nstrict=1\n\n#
repos\n\n[build]\nname=build\nbaseurl=http://fedora.riscv.rocks/kojifiles/repos/f33-build/65360/riscv64\n'

config_opts['plugin_conf']['ccache_enable'] = False
config_opts['plugin_conf']['root_cache_enable'] = False
config_opts['plugin_conf']['yum_cache_enable'] = False

config_opts['macros']['%_host'] = 'riscv64-redhat-linux-gnu'
config_opts['macros']['%_host_cpu'] = 'riscv64'
config_opts['macros']['%_rpmfilename'] =
'%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm'
config_opts['macros']['%_topdir'] = '/builddir/build'
config_opts['macros']['%distribution'] = 'Fedora Project'
config_opts['macros']['%packager'] = 'Fedora Project'
config_opts['macros']['%vendor'] = 'Fedora Project'

config_opts['files']['etc/hosts'] = '127.0.0.1   localhost
localhost.localdomain localhost4 localhost4.localdomain4\n::1
localhost localhost.localdomain localhost6 localhost6.localdomain6\n'

>
> Thanks in advance
> Billa
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: srpm rebuilding on RISC-V fedora image

2021-03-03 Thread Billa Surendra 

Without Correcting right URL to fedora-33-riscv64.cfg file we can not use MOCK 
for rebuilding SRPM's for RISC-V architecture.  Can anyone please suggest what 
I can do now to correct it?. How can I contact MirrorManager to correct the URL 
to the right location?.

Thanks in advance
Billa
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: srpm rebuilding on RISC-V fedora image

2021-03-03 Thread Peter Robinson 
On Wed, Mar 3, 2021 at 12:30 PM Richard W.M. Jones  wrote:
>
> On Wed, Mar 03, 2021 at 05:45:35PM +0530, Billa Surendra wrote:
> > Dear Richard,
>
> Please send messages to the Fedora devel list so there is
> a public record and so others can help.
>
> > I am trying to initialize the mock chroot before performing the first 
> > rebuild
> > SRPM on RISC-V fedora image.
> >
> > In order to initialize the chroot for fedora-33-riscv64 I have started 
> > running
> > the below command:
> >
> > $ mock -r fedora-33-riscv64.cfg --init
> >
> > But initialization did not proceed further. I am getting following error.
> >
> > Error:
> >
> > [root@fedora-riscv mock]# mock -r fedora-33-riscv64.cfg --init
> > INFO: mock.py version 2.8 starting (python version = 3.9.1, NVR =
> > mock-2.8-1.fc33)...
> > Start(bootstrap): init plugins
> > INFO: selinux disabled
> > Finish(bootstrap): init plugins
> > Start: init plugins
> > INFO: selinux disabled
> > Finish: init plugins
> > INFO: Signal handler active
> > Start: run
> > Start: clean chroot
> > Finish: clean chroot
> > Start(bootstrap): chroot init
> > INFO: calling preinit hooks
> > INFO: enabled root cache
> > INFO: enabled package manager cache
> > Start(bootstrap): cleaning package manager metadata
> > Finish(bootstrap): cleaning package manager metadata
> > INFO: enabled HW Info plugin
> > Mock Version: 2.8
> > INFO: Mock Version: 2.8
> > Start(bootstrap): dnf install
> > No matches found for the following disable plugin patterns: local, spacewalk
> > fedora   14 kB/s |  71 kB 00:04
> > Errors during downloading metadata for repository 'fedora':
> >   - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=
> > fedora-33=riscv64 (IP: 13.212.21.54)
> > Error: Failed to download metadata for repo 'fedora': Cannot prepare 
> > internal
> > mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?
> > repo=fedora-33=riscv64 (IP: 13.212.21.54)
> > ERROR: Command failed:
> >  # /usr/bin/dnf --installroot 
> > /var/lib/mock/fedora-33-riscv64-bootstrap/root/
> > --releasever 33 --setopt=deltarpm=False --allowerasing --disableplugin=local
> > --disableplugin=spacewalk install dnf dnf-plugins-core
> > No matches found for the following disable plugin patterns: local, spacewalk
> > fedora   14 kB/s |  71 kB 00:04
> > Errors during downloading metadata for repository 'fedora':
> >   - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=
> > fedora-33=riscv64 (IP: 13.212.21.54)
>
> This URL is wrong.  You're going to need to work out how to point to
> the Fedora/RISC-V Koji instance (http://fedora.riscv.rocks/koji/).  I
> don't know exactly how to do that but I'm sure someone on the Fedora
> development list can help.

Is that just the direct koji made repos? I suspect what we actually
need to do is like what we used to do on the secondary arches which
was a Minimal "Everything" compose, AKA just enough compose, to
generate the Everything repos and then sync that somewhere that is not
on the koji instance for a "Emerging Architecture" so it can then be
fronted by MirrorManager which would correctly point the URL above to
the right location.

Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: srpm rebuilding on RISC-V fedora image

2021-03-03 Thread Richard W.M. Jones 
On Wed, Mar 03, 2021 at 05:45:35PM +0530, Billa Surendra wrote:
> Dear Richard,

Please send messages to the Fedora devel list so there is
a public record and so others can help.

> I am trying to initialize the mock chroot before performing the first rebuild
> SRPM on RISC-V fedora image.
> 
> In order to initialize the chroot for fedora-33-riscv64 I have started running
> the below command:
> 
> $ mock -r fedora-33-riscv64.cfg --init
> 
> But initialization did not proceed further. I am getting following error.
> 
> Error: 
> 
> [root@fedora-riscv mock]# mock -r fedora-33-riscv64.cfg --init
> INFO: mock.py version 2.8 starting (python version = 3.9.1, NVR =
> mock-2.8-1.fc33)...
> Start(bootstrap): init plugins
> INFO: selinux disabled
> Finish(bootstrap): init plugins
> Start: init plugins
> INFO: selinux disabled
> Finish: init plugins
> INFO: Signal handler active
> Start: run
> Start: clean chroot
> Finish: clean chroot
> Start(bootstrap): chroot init
> INFO: calling preinit hooks
> INFO: enabled root cache
> INFO: enabled package manager cache
> Start(bootstrap): cleaning package manager metadata
> Finish(bootstrap): cleaning package manager metadata
> INFO: enabled HW Info plugin
> Mock Version: 2.8
> INFO: Mock Version: 2.8
> Start(bootstrap): dnf install
> No matches found for the following disable plugin patterns: local, spacewalk
> fedora                                           14 kB/s |  71 kB     00:04   
>  
> Errors during downloading metadata for repository 'fedora':
>   - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=
> fedora-33=riscv64 (IP: 13.212.21.54)
> Error: Failed to download metadata for repo 'fedora': Cannot prepare internal
> mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?
> repo=fedora-33=riscv64 (IP: 13.212.21.54)
> ERROR: Command failed:
>  # /usr/bin/dnf --installroot /var/lib/mock/fedora-33-riscv64-bootstrap/root/
> --releasever 33 --setopt=deltarpm=False --allowerasing --disableplugin=local
> --disableplugin=spacewalk install dnf dnf-plugins-core
> No matches found for the following disable plugin patterns: local, spacewalk
> fedora                                           14 kB/s |  71 kB     00:04   
>  
> Errors during downloading metadata for repository 'fedora':
>   - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=
> fedora-33=riscv64 (IP: 13.212.21.54)

This URL is wrong.  You're going to need to work out how to point to
the Fedora/RISC-V Koji instance (http://fedora.riscv.rocks/koji/).  I
don't know exactly how to do that but I'm sure someone on the Fedora
development list can help.

Rich.

> Error: Failed to download metadata for repo 'fedora': Cannot prepare internal
> mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?
> repo=fedora-33=riscv64 (IP: 13.212.21.54)
> 
> 
> Here I am planning to rebuild gcc SRPM on a mock by utilizing 
> fedora-33-riscv64
> arch on RISC-V fedora image. Can you please suggest what I have to do now.
> 
> Thanks
> 
> Billa
> 
> 
> 
> On Wed, Feb 24, 2021 at 4:03 PM Richard W.M. Jones  wrote:
> 
> On Wed, Feb 24, 2021 at 02:50:02PM +0530, Billa Surendra wrote:
> > Dear David and Richard,
> >
> > As you suggested, I have downloaded the latest RISC-V fedora image from
> this
> > link  state=closed=flat=
> > createAppliance=-id> and booted by using QEMU emulator. 
> >
> > Now started rebuilding gcc srpm  taken from this  dl.amnesia.boum.org/
> > fedora/releases/33/Everything/source/tree/Packages/g/>  on booted
> fedora. 
> >
> > Here I have changed the gcc.spec file for not supporting compressed
> > instructions. again re created  srpm.
> >
> > Actually here QEMU takes a lot of time (2-3 days) for rebuilding, even 
> it
> hangs
> > some time in fairly fast x86 hardware (25 GB RAM and 8 cores).
> 
> It takes 3 days to rebuild GCC even on SiFive Unleashed.  You just
> have to be patient and don't make a mistake.
> 
> > Is there any way to increase the number of cores from 8 to 24 in QEMU 
> -smp 8 
> > option ?.  or I have to use a sifive board for that.
> 
> Last time I looked into this, 8 was an architectural limit on the
> number of cores.  I don't know if more are supported now - try it and
> see.  I doubt it will give you very much more performance for building
> GCC even if it works.
> 
> Rich.
> 
> 
> > If you feel a sifive board is best for rebuilding fedora 
> packages(without
> > compressed support), which one I have to use ?.
> >
> > Please help out regarding the above problem.
> >
> > Thanks in advance
> >
> > Billa
> >   
> >
> >  
> >
> >
> 
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/
> ~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
>