On Wednesday 10 June 2015, 08:38:53, Olaf Meeuwissen wrote:
Olaf Meeuwissen writes:
Niels Ole Salscheider writes:
Am 2015-06-09 14:21, schrieb m. allan noah:
We need more info here. Where do you see this expansion problem?
allan
The problem is that LIBDIR is passed as a define
Niels Ole Salscheider writes:
On Wednesday 10 June 2015, 08:38:53, Olaf Meeuwissen wrote:
[...]
The double quotes in Makefile.am are eaten by the shell. You would also
need to change the above to
-DLIBDIR=\$(libdir)/sane\
in backend/Makefile.am and run autoreconf to update the rest
Otherwise, linux will be expanded to 1 when it is stringified.
This is a problem for e. g. LIBDIR, which might contain a target triplet.
On my system, /usr/x86_64-pc-linux-gnu-gcc would expand to x86_64-pc-1-gnu-gcc.
---
include/sane/sanei.h | 3 +++
1 file changed, 3 insertions(+)
diff --git
Am 2015-06-09 14:21, schrieb m. allan noah:
We need more info here. Where do you see this expansion problem?
allan
The problem is that LIBDIR is passed as a define from the build system.
Then, STRINGIFY(LIBDIR) is used in backend/dll.c to get a string of the
search path for the backends.
Niels Ole Salscheider writes:
Am 2015-06-09 14:21, schrieb m. allan noah:
We need more info here. Where do you see this expansion problem?
allan
The problem is that LIBDIR is passed as a define from the build system.
Then, STRINGIFY(LIBDIR) is used in backend/dll.c to get a string of the
Olaf Meeuwissen writes:
Niels Ole Salscheider writes:
Am 2015-06-09 14:21, schrieb m. allan noah:
We need more info here. Where do you see this expansion problem?
allan
The problem is that LIBDIR is passed as a define from the build system.
Then, STRINGIFY(LIBDIR) is used in
We need more info here. Where do you see this expansion problem?
allan
On Sun, Jun 7, 2015 at 4:14 PM, Niels Ole Salscheider
niels_...@salscheider-online.de wrote:
Otherwise, linux will be expanded to 1 when it is stringified.
This is a problem for e. g. LIBDIR, which might contain a target
