Opened 8 years ago

Closed 6 years ago

#4664 closed enhancement (fixed)

./autogen.sh puts stuff on stderr

Reported by: Sebastian Owned by:
Priority: Low Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: easy tor-client
Cc: onizuka.xxxx@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

inside autogen.sh, we call autoreconf -ivf. The -v flag means verbose reports, which are basically just "going to dir x, calling application y" on stderr. This is pretty useless, and for some scripts I'd like to be able to silence the output except for error conditions. Can we simply take out the -v here without bad stuff happening?

Child Tickets

Attachments (2)

0001-disable-verbose-flag-when-calling-autoreconf-in-auto.patch (612 bytes) - added by stewart 7 years ago.
4667_autogen_args_handling.patch (1.1 KB) - added by onizuka 7 years ago.
Updated the patch so as to have the full verbosity control with '-v'. Nota : it is not a _full_ verbosity output.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 8 years ago by Sebastian

Priority: normalminor

ah, hrm. This doesn't help when the dir is clean, because we still get some output. I guess it might not be worth it to track it all down

comment:2 Changed 7 years ago by nickm

Keywords: easy added

comment:3 Changed 7 years ago by nickm

Keywords: tor-client added

comment:4 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:5 Changed 7 years ago by onizuka

Cc: onizuka.xxxx@… added
Status: newneeds_review
Type: defectenhancement

Added a patch which allows to handle the command line arguments. By default the behavior would be not to be verbose.

comment:6 Changed 7 years ago by nickm

Status: needs_reviewnew

Applied; leaving this ticket open until we solve the issue where autogen.sh says stuff when starting with a clean checkout.

Changed 7 years ago by onizuka

Updated the patch so as to have the full verbosity control with '-v'. Nota : it is not a _full_ verbosity output.

comment:7 Changed 7 years ago by onizuka

Status: newneeds_review

comment:8 Changed 7 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.5.x-final

Marking this for 0.2.5; it looks probably-good, but we can survive in 0.2.4 with the current behavior.

comment:9 Changed 7 years ago by nickm

Status: needs_reviewnew

Oh hey ; this should no longer be in needs_review: we merged all the code we had.

comment:10 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.4.x-final
Resolution: fixed
Status: newclosed

I don't think there's more to do here that we know how to do, and the priority isn't high. Closing as fixed-in-0.2.4.

Note: See TracTickets for help on using tickets.