| Summary: | Build issue: FTBFS Makefile.am INCLUDES= $(all_includes) $(KDE_INCLUDES)/tde | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | non-core programs | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | blocker | CC: | bugwatch, darrella, michele.calgaro |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Darrell
2014-01-25 22:43:49 CST
Darrell, is the bug still valid? I can build all those modules in Debian/jessie Yes, valid. Everybody else seems to be able to build these packages except me. There is either a configuration option or other presumption I am not aware. Could you attach a build log for at least one of those packages and the build option you use? >Could you attach a build log for at least one of those packages and the build
>option you use?
The original problem description contains the necessary information. All of the modules fail the same way:
g++: error: /tde: No such file or directory
Build scripts use the same generic configuration for all:
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QT_INCLUDE_DIR} \
--with-qt-libraries=${QT_LIB_DIR} \
$DEBUG_AUTOTOOL_OPT || exit 1
All those modules seems to build fine in deb and rpm distros. Closing the bug. Reopen if you can still replicate the problem :-) |