Hi! I sent you the logs, did you get them? If there is anything I can do else, just leave me a message. The results will be posted in here, so anyone else running into that can find the solution. Best Regards Ulrich -----Original Message----- From: Gergely Nagy <algernon@balabit.hu> To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Sent: Wed, Jun 15, 2011 9:54 am Subject: Re: [syslog-ng] Cross-compile problem with path in 3.2.4 Ulrich Prinz <uprinz2@netscape.net> writes:> I cross compiled syslog-ng 3.2.4 for my ARM board. I called ./configure > with the usual --host, --prefix and --exec-prefix options. Then I ran > make with DESTDIR to my cross target directory.> I moved everything to my ARM target and syslog-ng starts up. While it > locates and loads the configuration files properly, there is a problem > with the modules:[..snip..]> Checking the directory shows:> /etc2/syslog-ng # ll /lib/syslog-ng/> drwxr-xr-x 2 root root 1024 Jun 14 16:01 ./> drwxr-xr-x 7 root root 3072 Jun 14 16:01 ../> -rw-r--r-- 1 root root 139122 Jun 14 16:01 libaffile.a> -rwxr-xr-x 1 root root 1289 Jun 14 16:01 libaffile.la*[..snip..]The reason it doesn't work, is because the shared objects are missing:it will not load .a files, only .sos. (More or less...)Could you perhaps send a complete build log, along with the output ofconfigure? (Privately to me works aswell, as the full log might be toobig for the list)I might be able to figure out why the shared libs did not get built.In the mean time, as a workaround, I'd suggest compiling syslog-ng in anemulator instead: that's a lot slower, but I know that it works, that'show I got syslog-ng onto my router ;)-- |8]______________________________________________________________________ ________Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ngDocumentation: http://www.balabit.com/support/documentation/?product=syslog-ngFAQ: http://www.balabit.com/wiki/syslog-ng-faq