Hello, The scripts generated by libtool aren't part of the final delivery. The executables in .libs/ will get installed during 'make install' into their final destination and then libtool will (re)link executables against the freshly installed libraries. This is why a successful 'make install' is needed and then the result could get copied to the target host. gmake compares timestamps of source and compiled files to track dependencies so if there was a change after the build process then reconfigure / rebuild gets triggered - this should get avoided but it is more or less impossible to guess what happened on your system after running make... For example many years ago I had issues with certain filesystems not storing fractions of seconds so timestamps were rounded to seconds and comparision became a bit stochastic... Regards, Sandor On 10/04/2017 05:08 PM, Robert King wrote:
Not easily, and not without getting permission from the director of development.
Let’s start with an easy question. …/syslog-ng/syslog-ng is a script. Is this part of the **final** distribution to be installed on the target system? There is also …/syslog-ng/.libs/syslog-ng with is an ELF binary executable. Is this part of the **final** distribution to be installed on the target system? Why are there two executable files with the same name?
…/syslog-ng/.libs/syslog-ng is being natively built on a generic Linux Mint system, but not on my cross-development system. How do you suggest troubleshooting this? Going through the generated Makefile in the project root directory is a nightmare. There is no makefile in …/syslog-ng, so I can’t try to build just that.
Sorry that I was irritated earlier, but I’ve been fighting this for three weeks and my boss is getting angry.
*From:* syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] *On Behalf Of *Budai, László *Sent:* Wednesday, October 04, 2017 10:00 AM *To:* Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> *Subject:* Re: [syslog-ng] Cross-compiling syslog-ng 3.11.1 for an embedded application.
Hi,
could you share a build environment where we can easily reproduce the issue(eg.: a docker file, or, image )?
Laszlo Budai
On Wednesday, October 4, 2017, Robert King <robert.king@tellabs.com <mailto:robert.king@tellabs.com>> wrote:
*From:* syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu <javascript:_e(%7B%7D,'cvml','syslog-ng-bounces@lists.balabit.hu');>] *On Behalf Of *Scheidler, Balázs *Sent:* Tuesday, October 03, 2017 11:32 PM *To:* Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu <javascript:_e(%7B%7D,'cvml','syslog-ng@lists.balabit.hu');>> *Subject:* Re: [syslog-ng] Cross-compiling syslog-ng 3.11.1 for an embedded application.
Hi,
Again, so without your help and a civilized exchange of emails this can't be troubleshot, as I never saw your environment, and can't check various details that would affect compilation.
What information would you like from me to progress?
We are using gmake to build the targets. We are calling the configure script with the following arguments:
PKG_CONFIG_PATH=$PCRERELEASE/lib/pkgconfig:$EVENTLOGRELEASE/lib/pkgconfig:$GLIBRELEASE/lib/pkgconfig \
SED=/bin/sed \
./configure \
--host=$HOST \
PKG_CONFIG_PATH=$PCRERELEASE/lib/pkgconfig:$EVENTLOGRELEASE/lib/pkgconfig:$GLIBRELEASE/lib/pkgconfig \
--build=$BUILD \
--prefix=$INSTALLDIR \
--bindir=$INSTALLDIR/bin \
--sbindir=$INSTALLDIR/sbin \
--includedir=$INSTALLDIR/include \
--libdir=$INSTALLDIR/lib \
--sharedstatedir=$INSTALLDIR/share \
--exec-prefix=$EXECDIR \
--libexecdir=$EXECDIR/lib \
--localstatedir=$EXECDIR/etc/syslog-ng/var \
--sysconfdir=$EXECDIR/etc/syslog-ng/etc \
--enable-shared=yes \
--enable-ssl \
--enable-static=yes \
--enable-dynamic-linking=yes \
--disable-json \
--enable-pcre=no \
--with-libmongo-client=no \
--with-librabbitmq-client=no \
CC=$MVL/bin/ppc_440-gcc \
CFLAGS="-g -O2" \
CPP=$MVL/bin/ppc_440-cpp \
CPPFLAGS="-I$EVENTLOGRELEASE/include -I$GLIBRELEASE/include -I$TARGET/usr/include -I$TARGET/usr/local/include" \
LDFLAGS="-L/vobs/tools/openssl/openssl/release/$OS/lib -L$EVENTLOGRELEASE/lib -L$GLIBRELEASE/lib -L$TARGET/lib -L$TARGET/usr/lib" \
OPENSSL_CFLAGS="${OPENSSL_CC_INC_PATH} ${OPENSSL_CC_FIPS_INC_PATH} -DBUILD_WITH_SSL" \
OPENSSL_LIBS="-lssl -lcrypto" \
LIBS="-lssl -lcrypto"
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq