That's really strange. With a non-modified configure.in (which means
that is containing this misplaced stanza), I did:
# cd /usr/ports/security/tor/
# make deinstall
# make clean
# make install
and... voilá:
mb# ldd /usr/local/bin/tor
/usr/local/bin/tor:
libtcmalloc.so.2 => /usr/local/
Very interesting. That first stanza is indeed wrongly placed. But
when you move it, does it start working?
I tried a couple of things without success. So, what code should be
placed in where?
And why does it seem that ./configure is not getting the
--with-tcmalloc option at all?
No idea.
On Fri, Aug 10, 2012 at 6:21 PM, Jordi Espasa Clofent
wrote:
> Well, finally it seems a Tor configure.in bug/problem:
>
> http://lists.freebsd.org/pipermail/freebsd-ports/2012-August/077440.html
>
> So.. I guess it has to be fixed by some tor dev then.
Very interesting. That first stanza is inde
Well, finally it seems a Tor configure.in bug/problem:
http://lists.freebsd.org/pipermail/freebsd-ports/2012-August/077440.html
So.. I guess it has to be fixed by some tor dev then.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.to
On 08/10/2012 04:56 PM, Jordi Espasa Clofent wrote:
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 i
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 ce
On Fri, Aug 10, 2012 at 10:14 AM, Jordi Espasa Clofent
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
On 08/09/2012 04:54 PM, Nick Mathewson wrote:
On Thu, Aug 9, 2012 at 6:04 AM, Jordi Espasa Clofent
wrote:
Can you see what arguments are being passed to configure, and what
configure does with them? Is the freebsd build process passing
--with-tcmalloc to the configure script?
Sure.
mb# pw
On Thu, Aug 9, 2012 at 6:04 AM, Jordi Espasa Clofent
wrote:
>>
>> Can you see what arguments are being passed to configure, and what
>> configure does with them? Is the freebsd build process passing
>> --with-tcmalloc to the configure script?
>
>
> Sure.
>
> mb# pwd && make showconfig
Hm. Does a
On 08/09/2012 01:43 AM, Nick Mathewson wrote:
On Wed, Aug 8, 2012 at 7:09 PM, Jordi Espasa Clofent
wrote:
Here is the log:
===> Installing for tor-0.2.2.37
===> tor-0.2.2.37 depends on file: /usr/local/lib/libcrypto.so.7 - found
===> tor-0.2.2.37 depends on shared library: event-2.0 - fou
On Wed, Aug 8, 2012 at 7:09 PM, Jordi Espasa Clofent
wrote:
> Here is the log:
>
> ===> Installing for tor-0.2.2.37
> ===> tor-0.2.2.37 depends on file: /usr/local/lib/libcrypto.so.7 - found
> ===> tor-0.2.2.37 depends on shared library: event-2.0 - found
> ===> tor-0.2.2.37 depends on shar
Remove (or move) the port's ‘work’ directory and run ‘make’.
(You can't easily *install* an upgraded or recompiled FreeBSD port or
package without removing the old one, though.)
That's possible yes. Or you can use -f flag with portupgrade.
However this is not the point.
___
Here is the log:
===> Installing for tor-0.2.2.37
===> tor-0.2.2.37 depends on file: /usr/local/lib/libcrypto.so.7 - found
===> tor-0.2.2.37 depends on shared library: event-2.0 - found
===> tor-0.2.2.37 depends on shared library: tcmalloc - found
===> Generating temporary packing list
=
On 8/8/12, Nick Mathewson wrote:
> On Wed, Aug 8, 2012 at 4:26 PM, Jordi Espasa Clofent
> wrote:
>>> What line does the build process use when linking Tor?
>>
>>
>> Hi again Nick,
>>
>> I have no idea, but I guess I could do the next:
>>
>> 1. Stop the tor service
>> 2. deinstall the present port
On Wed, Aug 8, 2012 at 4:26 PM, Jordi Espasa Clofent
wrote:
>> What line does the build process use when linking Tor?
>
>
> Hi again Nick,
>
> I have no idea, but I guess I could do the next:
>
> 1. Stop the tor service
> 2. deinstall the present port
> 3. Check the tcmalloc option is enabled
> 4.
What line does the build process use when linking Tor?
Hi again Nick,
I have no idea, but I guess I could do the next:
1. Stop the tor service
2. deinstall the present port
3. Check the tcmalloc option is enabled
4. install the port and redirect all the output to a log file
$ /usr/local/etc/r
On Mon, Aug 6, 2012 at 2:06 PM, Jordi Espasa Clofent
wrote:
> On 08/06/2012 07:03 PM, Nick Mathewson wrote:
>>
>> Hm. Tor itself doesn't have a tcmalloc compilation option, so whatever
>> it's doing is something freebsd added. To debug this kind of thing,
>> what I usually suggest is to rebuild
On 08/06/2012 07:03 PM, Nick Mathewson wrote:
Hm. Tor itself doesn't have a tcmalloc compilation option, so whatever
it's doing is something freebsd added. To debug this kind of thing,
what I usually suggest is to rebuild and look carefully at which
compiler and linker options are used in build
Hm. Tor itself doesn't have a tcmalloc compilation option, so whatever
it's doing is something freebsd added. To debug this kind of thing, what I
usually suggest is to rebuild and look carefully at which compiler and
linker options are used in building Tor, and see if they include the
appropriate
Hi,
I posted this message in tor-relays, but it seems to me (and another
people) that dev mail-list is better channel to use.
Thanks!
Original Message
Hi all,
From time to time my tor node (minibofh) stopped to work properly;
since it's a tiny FreeBSD VPS, the root origin w
20 matches
Mail list logo
