Opened 18 months ago

Last modified 3 months ago

#26356 needs_information defect

Tor 0.3.3.6 fails to compile under cygwin (x86_64)

Reported by: gk Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.3.1-alpha
Severity: Normal Keywords: regression, 033-unreached-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

From the 0.3.3.6 blog post's comments (https://blog.torproject.org/comment/275501#comment-275501):

I try to build latest tor 0.3.3.6 from source under "x86_64 Cygwin".
Earlier versions did compile, I'm running now "Tor version 0.3.2.9 (git-9e8b762fcecfece6)."

Compilation now Fails with the following erros:

make all-am
make[1]: Entering directory '/cygdrive/f/tor-0.3.3.6'
CC src/ext/ed25519/ref10/src_ext_ed25519_ref10_libed25519_ref10_a-fe_0.o
In file included from src/ext/ed25519/ref10/crypto_int32.h:6,
from src/ext/ed25519/ref10/fe.h:4,
from src/ext/ed25519/ref10/fe_0.c:1:
./src/common/torint.h:214:2: error: #error "Can't define ssize_t."
#error "Can't define ssize_t."
^~~~~
./src/common/torint.h:237:2: error: #error "void * is either >8 bytes or <= 2. In either case, I am confused."
#error "void * is either >8 bytes or <= 2. In either case, I am confused."
^~~~~
./src/common/torint.h:241:2: error: #error "Missing type int8_t"
#error "Missing type int8_t"
^~~~~
./src/common/torint.h:244:2: error: #error "Missing type uint8_t"
#error "Missing type uint8_t"
^~~~~
./src/common/torint.h:247:2: error: #error "Missing type int16_t"
#error "Missing type int16_t"
^~~~~
./src/common/torint.h:250:2: error: #error "Missing type uint16_t"
#error "Missing type uint16_t"
^~~~~
./src/common/torint.h:253:2: error: #error "Missing type int32_t"
#error "Missing type int32_t"
^~~~~
./src/common/torint.h:256:2: error: #error "Missing type uint32_t"
#error "Missing type uint32_t"
^~~~~
./src/common/torint.h:259:2: error: #error "Missing type int64_t"
#error "Missing type int64_t"
^~~~~
./src/common/torint.h:262:2: error: #error "Missing type uint64_t"
#error "Missing type uint64_t"
^~~~~
./src/common/torint.h:269:2: error: #error "Seems that your platform doesn't use 2's complement arithmetic. Argh."
#error "Seems that your platform doesn't use 2's complement arithmetic. Argh."
^~~~~
./src/common/torint.h:277:2: error: #error "Can't define LONG_MAX"
#error "Can't define LONG_MAX"
^~~~~
./src/common/torint.h:287:2: error: #error "Can't define INT_MAX"
#error "Can't define INT_MAX"
^~~~~
./src/common/torint.h:299:2: error: #error "Can't define UINT_MAX"
#error "Can't define UINT_MAX"
^~~~~
./src/common/torint.h:309:2: error: #error "Can't define SHORT_MAX"
#error "Can't define SHORT_MAX"
^~~~~
./src/common/torint.h:367:2: error: #error "Can't define SSIZE_MAX"
#error "Can't define SSIZE_MAX"
^~~~~
make[1]: *** [Makefile:6513: src/ext/ed25519/ref10/src_ext_ed25519_ref10_libed25519_ref10_a-fe_0.o] Error 1
make[1]: Leaving directory '/cygdrive/f/tor-0.3.3.6'
make: *** [Makefile:3409: all] Error 2

Child Tickets

TicketStatusOwnerSummaryComponent
#26459closednetinet/tcp.h autoconf test is missing u_int32_t on cygwinCore Tor/Tor
#26460reopenedSome? autoconf tests that include stdio.h fail with a missing ssp.h on cygwinCore Tor/Tor

Attachments (1)

config.log (1.5 MB) - added by rolex0815 17 months ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 18 months ago by nickm

Status: newneeds_information

That's usually a symptom that something has gone wrong with autoconf when they ran it. Having the full output of config.log would help resolve this.

Changed 17 months ago by rolex0815

Attachment: config.log added

comment:2 Changed 17 months ago by rolex0815

I had a try today with 0.3.3.7.
Same Probleme as above.

Last Version running under cygwin is:

Tor 0.3.2.9 (git-9e8b762fcecfece6) running on CYGWIN_NT-10.0 with Libevent 2.0.22-stable, OpenSSL 1.0.2o, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd N/A.

comment:3 Changed 17 months ago by teor

Keywords: regression 033-backport added
Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final
Status: needs_informationnew

I'm opening child tickets for the issues in the log.

comment:4 Changed 17 months ago by teor

Version: Tor: 0.3.3.1-alpha

It looks like #26460 causes most of the configure tests to fail.
We should fix #26460, then try compiling on cygwin again.

comment:5 Changed 17 months ago by teor

Status: newneeds_information

#26460 could be an issue with the environment: the preprocessor can't find ssp.h for some input files / command lines, but other similar command lines succeed.

comment:6 Changed 17 months ago by nickm

Is this new with 0.3.3, or did 0.3.2 have the same issue?

comment:7 in reply to:  6 ; Changed 17 months ago by teor

Replying to nickm:

Is this new with 0.3.3, or did 0.3.2 have the same issue?

Apparently it's new with 0.3.3, and 0.3.2 worked:

I try to build latest tor 0.3.3.6 from source under "x86_64 Cygwin".
Earlier versions did compile, I'm running now "Tor version 0.3.2.9 (git-9e8b762fcecfece6)."

But I'm wondering if a compiler upgrade could have caused this issue.

rolex0815, have you tried compiling 0.3.2 with your current Cygwin environment?

comment:8 in reply to:  7 Changed 17 months ago by rolex0815

Replying to teor:

rolex0815, have you tried compiling 0.3.2 with your current Cygwin environment?

Yes, see above.
Last Version I could compile was:

Tor 0.3.2.9 (git-9e8b762fcecfece6) running on CYGWIN_NT-10.0 with Libevent 2.0.22-stable, OpenSSL 1.0.2o, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd N/A.

And ssp.h file is present, only make doesn't find it.

comment:9 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

comment:10 Changed 9 months ago by teor

Keywords: 033-backport removed

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

comment:11 Changed 9 months ago by teor

Keywords: 033-backport-unreached added

Hmm, I guess they should still get 033-backport-unreached

comment:12 Changed 3 months ago by teor

Keywords: 033-unreached-backport added; 033-backport-unreached removed

Fix 033-unreached-backport spelling.

Note: See TracTickets for help on using tickets.