[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How-to solve runpath-errors when splitting packages?

From: Hartmut Goebel
Subject: How-to solve runpath-errors when splitting packages?
Date: Tue, 5 Mar 2019 22:05:47 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1


I'm currently packaging zbar (a bar-code scanner suite). zbar includes
"generic" binaries as well as "qt" anf "gtk" ones (zbarcam, zbarcam-qt,
zbarcam-gtk). I want to avoid having qt or gtk or even both as a
dependency of the `zbar` packages, as these would pull in *huge*

I already managed to split the output into several. Here is an the
file-list for zbar:qt:


Obviously zbarcam-gtk should use from the same output.

How can I make zbarcam-gtk find the lib? Any ideas?

I already tried:

0) Nothing special: phase "validate-runpath" fails.

1) Setting "#:validate-runpath? #f": build passes, but the program does
not find the lib.

2) Passing the equivalent of "LDFLAGS=-Wl,-rpath=${out_gtk}/lib
-Wl,-rpath=${out_qt}/lib" to configure. This leads to some "recursive
dependency error".

Hartmut Goebel

| Hartmut Goebel          | address@hidden               |
| | compilers which you thought are impossible |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]