sablot-config is a script that is created at build time that spits out various paths for the sablotron library. However, it spits out the path from when it was built, which isn't very useful: # sablot-config --libs -L/var/tmp/portage/sablotron-1.0/image//lib -lexpat # sablot-config --help Usage: sablot-config [OPTION] Known values for OPTION are: --prefix=DIR change sablot prefix [default /var/tmp/portage/sablotron-1.0/image/] --libs print library linking information --cflags print pre-processor and compiler flags --help display this help and exit --version output version information Reproducible: Always Steps to Reproduce: 1. emerge sablotron 2. sablot-config --libs 3. marvel at it not giving the correct path Actual Results: sablot-config spits out a patch in /var/tmp/portage/sablotron-1.0/image Expected Results: sablot-config should spit out something like: -L/usr/lib -lsablot This might not break a normal system, as it will already be including /usr/lib, but it will definately cause problems when trying to do things like 32/64 bit systems etc, and its wrong so it should be fixed.
Agreed, I can confirm the behaviour. Will look into it.
Okay, problem was econf --prefix=${D} which generates sablot-config from sablot-config.in. Using ${D} there means we have /var/tmp etc, because that's the full path to the image directory. Now only pass prefix= to einstall, which is the better way of doing it.
