mainAutoconf - Support: sr #110300, configure >/dev/full does not...

 
 

sr #110300: configure >/dev/full does not fail promptly

Submitter:  Zack Weinberg <zackw>
Submitted:  Fri 28 Aug 2020 02:54:33 PM UTC
   
 
Priority:  * 2 - Eventually Severity:  3 - Normal
Status:  Confirmed Privacy:  Public
Assigned to:  None Open/Closed:  Open
Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 08 Dec 2023 01:51:48 PM UTC, comment #2: 

Using `set -e` in configure is abstractly desirable but will be an enormous amount of work. Not going to happen until someone signs up to do that work.

Zack Weinberg <zackw>
Group administrator
Fri 28 Aug 2020 02:56:23 PM UTC, comment #1: 

This is a long-standing issue.  Also, the cleanest way to detect these errors would be to turn on `set -e` mode, which would probably expose all kinds of other latent issues that we'd then have to fix.  So this is a post-2.70 project.

Zack Weinberg <zackw>
Group administrator
Fri 28 Aug 2020 02:54:33 PM UTC, original submission:  

If you run a configure script with stdout pointed to a data sink that fails all writes (e.g. `./configure > /dev/full` or `./configure 1< /dev/null`) you get a flood of "printf: write error" messages, but the script runs all the way to completion, and then it may or may not exit successfully depending on exactly what you did.

The script should instead exit unsuccessfully after the first write error.

Zack Weinberg <zackw>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by zackw (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-12-08 zackw Priority1 - Blocked 2 - Eventually
    2020-08-28 zackw Priority5 - Unprioritized 1 - Blocked

    Back to the top

    Powered by Savane 3.13-c373.
    Corresponding source code