On Tue, 16 Mar 2021 22:29:39 +0900 Takayuki Nagata <tnagata@xxxxxxxxxx> wrote: > Hi Billa, > > I am not sure if compressed instruction support can be disabled, but > it appears to me that --with-arch= should be rv32gc or rv64gc for > multilib. It is implemented in the gcc/config.gcc file. > > Florian mentioned that there is no glibc without compressed > instruction support. Perhaps, gcc port might also have any constraints > with regard to that. also such toolchain configuration related questions should be directed to the respective upstreams (gcc, glibc), Fedora is only a consumer here Dan > > Regards, > Takayuki Nagata > > 2021年3月16日(火) 19:26 Billa Surendra <billa.iitmadras@xxxxxxxxx>: > > > > > > > Dear all, > > > > From last 10 days I am struggling to rebuilding gcc-10.2.1-9.fc33.src.rpm SRPM on RISC-V Fedora image. Here I am planning to rebuilt this SRPM without compressed instruction support. Following changed I have done on gcc.spec file. > > > > %ifarch riscv64 > > --with-arch=rv64g --with-abi=lp64 > > %endif > > > > Even by changing above two flags for different options. still i am not able to rebuilt it. Here I am listing all combinations and error result what I have tried for rebuilding gcc SRPM. > > > > 1. %ifarch riscv64 > > --with-arch=rv64g --with-multilib > > > > > > Result: #error "rv32i-based targets are not supported" > > > > > > 2. %ifarch riscv64 > > --with-arch=rv64imafd --enable-multilib --with-multilib-list=lp64 > > > > > > Result: > > > > unsupported --with-arch for --with-multilib-list > > make[2]: *** [Makefile:4441: configure-stage1-gcc] Error 1 > > make[2]: Leaving directory '/root/rpmbuild/BUILD/gcc-10.2.1-20201125/obj-riscv64-redhat-linux' > > > > > > 3. %ifarch riscv64 > > --with-arch=rv64imafd --enable-multilib --with-multilib-list=lp64d > > > > Result: > > > > unsupported --with-arch for --with-multilib-list > > make[2]: *** [Makefile:4441: configure-stage1-gcc] Error 1 > > make[2]: Leaving directory '/root/rpmbuild/BUILD/gcc-10.2.1-20201125/obj-riscv64-redhat-linux' > > > > > > 4. %ifarch riscv64 > > --with-arch=rv64g --with-abi=lp64d --with-multilib-list=lp64d > > > > Result: > > > > unsupported --with-arch for --with-multilib-list > > make[2]: *** [Makefile:4441: configure-stage1-gcc] Error 1 > > > > > > 5. %ifarch riscv64 > > --with-arch=rv64g --with-abi=lp64 --with-multilib-list=lp64 > > > > > > Result: unsupported --with-arch for --with-multilib-list > > > > > > 6. %ifarch riscv64 > > --with-arch=rv64g --enable-multilib > > > > Result: #error "rv32i-based targets are not supported" > > > > > > 7. %ifarch riscv64 > > --with-arch=rv64g --with-abi=lp64 > > > > Result: #error "rv32i-based targets are not supported" > > > > > > 8. %ifarch riscv64 > > --with-arch=rv64g --with-multilib-generator="rv64ima-lp64--f" > > > > Result: #error "rv32i-based targets are not supported" > > > > > > 9. %ifarch riscv64 > > --with-arch=rv64g --with-abi=lp64 --with-multilib-generator="rv64ima-lp64--f" > > > > Result: error: #error "rv32i-based targets are not supported" > > > > > > 10. %ifarch riscv64 > > --with-arch=rv64g --enable-multilib --with-multilib-generator="rv64ima-lp64--f" > > > > > > Result: #error "rv32i-based targets are not supported" > > > > > > Here very important observation I have noted. when I am giving below option > > > > %ifarch riscv64 > > --with-arch=rv64g --disable-multilib > > > > Here all library packages are going to /usr/lib folder path, but in-between rebuilding process move commands are there, that are trying to move files from /usr/lib64 path. But no file is there in /usr/lib64 path. all falied move commads files are there in /usr/lib path. > > > > > > > > Can anyone please spend some time on this issue and help me out for successfull rebulding gcc SRPM. Please suggest perfect combination for sucessfull rebuilding. I hope someone faced same problem before i think, thier expreince will heplfull for me. > > > > Thanks > > Billa Surendra > > > > > > _______________________________________________ > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > 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@xxxxxxxxxxxxxxxxxxxxxxx > > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
