Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 880061 - gnome-base/librsvg-2.55.1 - thread 'main' panicked at 'Invalid TARGET: powerpc64-gentoo-linux-musl', /var/tmp/portage/gnome-base/librsvg-2.55.1/work/cargo_home/gentoo/system-deps-6.0.2/src/lib.rs:810:32
Summary: gnome-base/librsvg-2.55.1 - thread 'main' panicked at 'Invalid TARGET: powerp...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL: https://gitlab.gnome.org/GNOME/librsv...
Whiteboard:
Keywords:
Depends on:
Blocks: musl-porting
  Show dependency tree
 
Reported: 2022-11-06 14:46 UTC by ernsteiswuerfel
Modified: 2022-12-21 23:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (ppc64, 2.55.1) (librsvg-2.55.1:20221106-110725.log,208.78 KB, text/plain)
2022-11-06 14:46 UTC, ernsteiswuerfel
Details
emerge --info (file_880061.txt,6.88 KB, text/plain)
2022-11-06 14:46 UTC, ernsteiswuerfel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ernsteiswuerfel archtester 2022-11-06 14:46:01 UTC
Created attachment 828099 [details]
build.log (ppc64, 2.55.1)

For 2.54.x there is a patch from stefson (https://github.com/stefson/gentoo-extras/issues/1#issuecomment-1280774879) but the patch does not work on 2.55.1 any longer.

[...]
  --- stderr
  thread 'main' panicked at 'Invalid TARGET: powerpc64-gentoo-linux-musl', /var/tmp/portage/gnome-base/librsvg-2.55.1/work/cargo_home/gentoo/system-deps-6.0.2/src/lib.rs:810:32
  stack backtrace:
     0:        0x128a4e6ac - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h23ac1b1b4898f90d
     1:        0x128a8a110 - core::fmt::write::hac9ec6191e9e2f8b
     2:        0x128a480f0 - std::io::Write::write_fmt::h94e005cb68e84eda
     3:        0x128a5227c - std::panicking::default_hook::{{closure}}::hfcd2d34a98a91cdf
     4:        0x128a51c28 - std::panicking::default_hook::h19c598b7b0a76046
     5:        0x128a52ad0 - std::panicking::rust_panic_with_hook::h45e3ca31c2c1d450
     6:        0x128a52788 - std::panicking::begin_panic_handler::{{closure}}::hfe751aedd5597f92
     7:        0x128a4ece4 - std::sys_common::backtrace::__rust_end_short_backtrace::hf30076b121310bad
     8:        0x128a52368 - rust_begin_unwind
     9:        0x128772cc8 - core::panicking::panic_fmt::h9a708ec1e14b6224
    10:        0x1287954f4 - system_deps::Config::check_cfg::{{closure}}::he6280a8ff6b078c2
    11:        0x12877f988 - core::option::Option<T>::unwrap_or_else::h94edbab5170f1d3c
    12:        0x1287953e4 - system_deps::Config::check_cfg::h790b92f8ab7b688a
    13:        0x128792e70 - system_deps::Config::probe_pkg_config::h9f1cf7e19efb74c3
    14:        0x1287927c4 - system_deps::Config::probe_full::hee754f0e424103be
    15:        0x1287922cc - system_deps::Config::probe::h7d77f779aa890bd7
    16:        0x1287736dc - build_script_build::main::h21bbbf8d66c5cc08
    17:        0x128776528 - core::ops::function::FnOnce::call_once::hd687bd4f3a0b7cad
    18:        0x128777538 - std::sys_common::backtrace::__rust_begin_short_backtrace::h953f5fb138f84d5e
    19:        0x1287770ac - std::rt::lang_start::{{closure}}::h1584354a7bd08ca1
    20:        0x128a4ddfc - std::rt::lang_start_internal::hb0e9589d58ee039f
    21:        0x128777060 - std::rt::lang_start::h37e1bc0443060c01
    22:        0x128775648 - main
    23:     0x3fff946a5ee0 - <unknown>
make[2]: *** [Makefile:1554: librsvg_c_api.la] Error 101
make[2]: Leaving directory '/var/tmp/portage/gnome-base/librsvg-2.55.1/work/librsvg-2.55.1-.ppc64'
make[1]: *** [Makefile:1077: all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/portage/gnome-base/librsvg-2.55.1/work/librsvg-2.55.1-.ppc64'
make: *** [Makefile:712: all] Error 2
 * ERROR: gnome-base/librsvg-2.55.1::gentoo failed (compile phase):
 *   emake failed
Comment 1 ernsteiswuerfel archtester 2022-11-06 14:46:34 UTC
Created attachment 828101 [details]
emerge --info
Comment 2 ernsteiswuerfel archtester 2022-11-20 13:45:27 UTC
Hopefully will be fixed in next point release as soon as https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/770 is merged.
Comment 3 ernsteiswuerfel archtester 2022-11-25 14:34:28 UTC
Seems to be a separate issue after all, not related to upstream https://gitlab.gnome.org/GNOME/librsvg/-/issues/917 nor the upstream fix for this issue https://gitlab.gnome.org/GNOME/librsvg/-/commit/efa9ef9ecf15cd03ea5317308811a4bcc6f3d848
Comment 4 ernsteiswuerfel archtester 2022-12-21 23:57:42 UTC
Upstream bug has been closed with following comment:

"I have no idea of how build environments look for a platform like that.  For 'exotic platforms', you are on your own 😃  I hope you find some ideas in these:

The panic you are seeing comes from this check in system-deps where it checks that get_builtin_target_by_triple() was able to find a suitable target.  In turn, get_builtin_target_by_triple() is implemented here, which works by just comparing the triple strings against the ALL_BUILTINS list.  You'll notice that there's no triple there with gentoo in it.

https://github.com/crossbeam-rs/crossbeam/pull/922 - replace the gentoo vendor in target triples with unknown.

I have no idea if just replacing gentoo with unknown will work, although there is an entry for powerpc64-unknown-linux-musl, which may be what you want.

What's easier for you to try?  Patch something in system-deps or cfg-expr so they modify the triple string with unknown?  Use a cross-compilation scheme to use an explicit powerpc64-unknown-linux-musl instead of gentoo's default?
I'll close this bug because it is not really librsvg's fault."

So how to proceed from here on?