[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: cannot compile 0.2.1.10-alpha



Nick and coderman, thank you for your responding.
I downloaded the 0.2.1.10-alpha source tarball again
and configure it and make it. It succeeded this time.
It's running normally as a client now. And then I come back to
the first tarball I've downloaded a few days ago, re-
configure it and make it again, also succeed this time.
I just don't know how could this happen.

The compiling is totally according to the instructions
for building Tor from tor-win32-mingw-creation.txt in the
'doc' file. But it's from 0.1.2.19 source tarball. I've
compared this instructions with the new ones from the
new source version(say 0.2.1.10-alpha). No big differences
except the versions: I use MinGW-5.1.3.exe, openssl-
0.9.8g.tar.gz and libevent 1.3e. I'm wondering if I should
change the versions later. But the compiling did succeed
with those older versions. It seems it's not affected.

The config.log is rewritten since I reconfigured it. So I'm afraid I
have lost the script before the successful compiling now.

At last, here's a question which confuse me for a long long time.
Everytime when my PC is running as a relay, even for a
little while, I cannot reach any web pages later. I'm not sure if it
has something to do with the PC itself. The configuration is as follows:
Pentium 4 CPU 2.93GHz,
502MB RAM,
Windows XP Professional(version 2002) Service Pack 3

the bandwidth limits and the exit policies for my relay are 
both default in Vidalia, that is >1.5Mbps.

On Thu, Jan 15, 2009 at 1:37 AM, Nick Mathewson <nickm@xxxxxxxxxxxxx> wrote:
On Tue, Jan 13, 2009 at 08:38:34PM -0800, coderman wrote:
> On Tue, Jan 13, 2009 at 7:59 PM, zmj <zangmj@xxxxxxxxx> wrote:
> > windows xp+sp3+mingw
> >...
>
> how did you invoke configure?
>
> what version of mingw?

It would also be helpful to have a copy of the config.log script that
configure generated, since something seems to have gone wrong there.
The file torint.h is only supposed to define ssize_t if the platform
has no ssize_t, but it seems that yours has one in sys/types.h that
autoconf did not detect.

(The config.log file will be very big.  Please do not email it to the
whole list.  Just compress it and send a copy to me and coderman, if
you could.)

thanks,
--
Nick Mathewson <nickm@xxxxxxxxxxxxx>