Quote:
Originally Posted by knc1
Ah, there is a way to tell config "don't test" - I have seen it used in some of the Buildroot make-files.
At which point my mind goes: "Poof" about details. Sorry.
|
Hmm yeah... now you mention it so have I. well its; 4am.
http://www.samba.org/samba/ftp/stabl...a-3.6.7.tar.gz
is the current
for this one I went with
./configure --prefix=/mnt/us --exec-prefix=/mnt/us --disable-rpath --target=arm-unknown-linux-gnueabi --host=i686-pc-linux --disable-shared --enable-gnutls --with-perl-binary=/mnt/us/usr/bin/perl --with-perl-archdir=/mnt/us/usr --with-automount --oldincludedir=/mnt/us/usr/include --disable-rpath-install --disable-rpath-private-install --disable-symbol-versions --localstatedir=/var --with-cachedir=${PREFIX}/cache --with-lockdir=/var/lock --with-logfilebase=${PREFIX}/log/samba --with-sockets-dir=/var/run --with-modulesdir=${LIBDIR}
git clone git://git.samba.org/samba.git samba
is the Git
this one I tried
--prefix=/mnt/us --exec-prefix=/mnt/us --with-gnu-ld --disable-rpath --target=arm-unknown-linux-gnueabi --host=i686-pc-linux --enable-static --disable-shared --cross-compile -p --enable-selftest --enable-coverage --enable-gnutls --with-perl-binary=/mnt/us/usr/bin/perl --with-perl-archdir=/mnt/us/usr --with-smbwrapper --with-automount --with-smbmount --download --oldincludedir=/mnt/us/usr/include --disable-rpath-install --disable-rpath-private-install --disable-symbol-versions --localstatedir=/var --with-cachedir=${PREFIX}/cache --with-lockdir=/var/lock --with-logfilebase=${PREFIX}/log/samba --with-sockets-dir=/var/run --with-modulesdir=${LIBDIR} --quick
Perhaps that may save someone some time.
----------------------------------------------
If some kind soul would help me out with this I would be eternally grateful.
Well, I imagine once we get it rocking for us, the whole community will be (however silently)
I gotta crash. did a no sleeper just 2 days ago. cant do another.
Later
===============================================
FROM
http://www.flameeyes.eu/autotools-my...tom-tests.html
5.2. “Run Tests”
Sometimes, the mere presence of a function, or of a constant's definition, is not enough for a test to be considered successful. For instance an interface's optional function might be present as a stub returning a “not implemented” error condition, or a constant might be declared but ignored by the functions that are supposed to make use of it. For these reasons, it is sometimes a necessity to execute the code after building it, and wait for its results.
Important
Executing test code in a build scenario can be tricky: the system used to build a package might very well not be the same where the code would be executed (this is the case for most Linux – and not – distributions' build farms) which could lead to erroneous results or, in case the architectures of the two systems are not compatible, an unusable test, which will interrupt the course of the ./configure execution.
For those reasons it is important to make sure that the results of all the tests executed on the build host can be overridden. To do so, the best solution is to cache the results, so that a simple environment variable can be used to skip over the test execution, providing the correct, precalculated value.
==================================
maybe value in that.