devel/apr1 on FreeBSD 10.0-RELEASE (amd64)

[olli hauer]

On 2014-05-03 11:55, Leander Schäfer wrote:
> Hi
> 
> 
> When I installed apr on a freshly installed FreeBSD machine, I fell over several "File not found" errors, etc. I thought you may be interested in it.
> 
> apr-1.5.1.tar.gz                              100% of  996 kB  171 kBps 00m06s
> apr-util-1.5.3.tar.gz                         100% of  853 kB 1472 kBps 00m01s
> expat-2.1.0.tar.gz                            100% of  549 kB  909 kBps 00m00s
> config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir setting
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib'
> libtool: install: warning: `libexpat.la' has not been installed in `/usr/local/lib'
> gdbm-1.11.tar.gz                              100% of  792 kB  412 kBps 00m02s
> make-3.82.tar.bz2                             100% of 1213 kB  512 kBps 00m03s
> config.status: WARNING:  'po/Makefile.in.in' seems to ignore the --datarootdir setting
> pkg-static: No package(s) matching libtool
> libtool-2.4.2.tar.gz                          100% of 2570 kB  583 kBps 00m05s
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib'
> libtool: install: warning: `./libgdbm.la' has not been installed in `/usr/local/lib'
> libtool: install: warning: `./libgdbm.la' has not been installed in `/usr/local/lib'
> libtool: install: warning: `./libgdbm.la' has not been installed in `/usr/local/lib'
> db-4.8.30.tar.gz                              100% of   21 MB 1756 kBps 00m12s
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'
> libtool: install: warning: `libdb-4.8.la' has not been installed in `/usr/local/lib/db48'

<-- start devel/apr1 related messages -->

> rm: conftest*: No such file or directory
> rm: conftest*: No such file or directory
> grep: /usr/ports/devel/apr1/work/apr-1.5.1/libtool: No such file or directory
> configure: WARNING: sys/syslimits.h: accepted by the compiler, rejected by the preprocessor!
> configure: WARNING: sys/syslimits.h: proceeding with the compiler's result
> rm: libtoolT: No such file or directory
> mkdir /usr/ports/devel/apr1/work/stage/usr/local/share/apr
> mkdir /usr/ports/devel/apr1/work/stage/usr/local/share/apr/build-1
> mkdir /usr/ports/devel/apr1/work/stage/usr/local/include/apr-1
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib'
> mkdir /usr/ports/devel/apr1/work/stage/usr/local/lib/apr-util-1
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib/apr-util-1'
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib/apr-util-1'
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib/apr-util-1'
> libtool: install: warning: relinking `libaprutil-1.la'
> libtool: install: warning: remember to run `libtool --finish /usr/local/lib'
> Compilation for devel/apr1 done
> 
> 
> 
> Best regards
> Leander

Hi,

those warnings say noting without context (full warning line + lines before) and how the messages are recorded.

I suspect the make output was redirected with `make > foo.log'.
If this is the case you see on your console the output from the configure script that is redirected to /dev/stdout.

To see the full output use `script -q mybuild.log make ...' or look into work/$port/config.log

The full output recorded with `script ...'

 build.log:checking if cc supports -c -o file.o... rm: conftest*: No such file or directory
 build.log:checking whether -lc should be explicitly linked in... rm: conftest*: No such file or directory



-- 
Regards,
olli