On Fri, Aug 10, 2012 at 10:14 AM, Jordi Espasa Clofent <[email protected]> wrote: > On 08/09/2012 04:54 PM, Nick Mathewson wrote: >> Have a look near the top of "config.log" (please don't send the whole >> file; it will be enormous) -- there should be a part that says what >> command line configure got. > > > I guess is /usr/ports/security/tor/work/tor-0.2.2.37/config.log > > Well, in here I see: > > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > > It was created by configure, which was > generated by GNU Autoconf 2.69. Invocation command line was > > $ ./configure --with-openssl-dir=/usr/local --disable-asciidoc > --enable-linker-hardening --enable-gcc-hardening --enable-buf-freelists > --disable-instrument-downloads --enable-threads --enable-transparent > --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ > --build=i386-portbld-freebsd8.1 >
Yup. No --with-tcmalloc there. For whatever reason, the freebsd build process didn't pass --with-tcmalloc to configure. If the ports maintainer isn't being responsive, maybe some other freebsd people could have a look? If the build process is telling Tor the wrong stuff, then that is almost certainly something going wrong with the build process. -- Nick _______________________________________________ tor-dev mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
