On Wed, Sep 3, 2014 at 9:51 AM, Stephan Kulow <coolo@suse.de> wrote:
This is the whole point of using ./configure - figure out where stuff is at build time (or figure out that stuff can't be found and report an error), so that the following assertion is true: IF the thing builds successfully, THEN it will work properly at runtime - no matter what O/S you build it on.
The problem with this: if your program hard codes the path in the binary, your spec file doesn't need to require util-linux but the exact path hardcoded.
Fine - except I already tried that and it didn't work and there's no way for me to fix it! We are going in circles; see previous loop here: http://lists.opensuse.org/opensuse-factory/2014-09/msg00027.html http://lists.opensuse.org/opensuse-factory/2014-09/msg00033.html http://lists.opensuse.org/opensuse-factory/2014-09/msg00034.html -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org