On Mon, Apr 29, 2024 at 04:17:37PM +0200, Florian Weimer wrote: > * Stephen Smoogen: > > > I guess we need to see what RPM owns that symlink and get it into the > > build root > > Sorry, I meant $RPM_BUILDROOT or %buildroot (the staging area used by > rpmbuild). That's not controlled by the system package manager, > obviously.
I see - AIUI %buildroot is always empty when RPM starts the %install phase. Maybe we can modify RPM macros to drop in the symlink here? Still, in practical terms hundreds of C libraries are built today and don't have any issue. Rich. > Thanks, > Florian > > > On Mon, Apr 29, 2024 at 08:22 Florian Weimer <fwei...@redhat.com> wrote: > > > > * Richard W. M. Jones: > > > > >> I don't want us to have RPM spec file hacks just to get RISC-V to > > >> install in the correct locations. The symbolic link evidently does not > > >> cover all cases. > > > > > > What cases aren't covered by the symlink? We have a full, working > > > Fedora/RISC-V distro using it at the moment. > > > > The symbolic link isn't in the buildroot. If shared objects are listed > > explicitly in %files (as some guidelines recommend) and upstream > > hard-codes the ABI directory names for installation purposes, the build > > fails. > > > > Setting %_libdir to /usr/lib64/lp64d instead might work. Fixing > > upstream to honor --libdir=/usr/lib64 in ./configure might be another > > option. > > > > Thanks, > > Florian > > -- > > _______________________________________________ > > 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, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > > > -- > > _______________________________________________ > > 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, report it: > > https://pagure.io/fedora-infrastructure/new_issue > -- > _______________________________________________ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
