Only relevant for crosscompile!!! The sdl-config script contains hardcoded /usr/lib path, if the configure script of some package invokes sdl-config to gather library information even with SYSROOT_SET -L/usr/lib(64) is returned Reproducible: Always Steps to Reproduce: 1. Setup crosstoolchain and cross-root 2. emerge any package which configure script calls sdl-config Actual Results: At linking stage the wrong library path is used by Libtool! Expected Results: Linking is fine! add ${SYS_ROOT} to -L${exec_prefix} ==> -L${SYS_ROOT}/${exec_prefix} before installing sdl-config in case of crosscompilation
i dont know where you're finding this "SYS_ROOT", but is not a standard thing and nothing in the tree should be using it if anything is to change in sdl-config, it's changing it so that it does not output -L paths for /usr/lib or /usr/lib64 at all
SYS_ROOT=/usr/${CHOST} Its used (and exported) by several ebuilds for crosscompilation. Removing the library-path alltogether is wrong. The librarypath should point to the CHOSTs library path this can be changed through a simple sed in the install section of the ebuild before copying the sdl-config to its destination. You are right in the point that its not ideal to use an exported variable for the path even if e.g. directfb-config is doing it that way.
reopen with a patch
bugzilla
No response, closing.
