[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11256: make check problems with coreutils 8.16 and earlier

From: Tim Mooney
Subject: bug#11256: make check problems with coreutils 8.16 and earlier
Date: Mon, 16 Apr 2012 15:20:12 -0500 (CDT)
User-agent: Alpine 2.02 (SOC 1266 2009-07-14)

In regard to: Re: bug#11256: make check problems with coreutils 8.16 and...:

On 04/16/2012 10:48 AM, Tim Mooney wrote:
I build my PATH from scratch in my .bashrc, rather than inheriting it from
the system defaults.  I'm guessing this is what's causing the test

Yes, that sounds like that's the problem.

In general, one cannot put arbitrary computation into .bashrc, as
that messes things up.  For example, it's a bad idea to put
'echo xxx' into .bashrc.

I absolutely understand that, and of course I do not have any commands
that generate output or mess with the terminal settings in .bashrc.  Those
belong in the interactive-login file.

Shouldn't PATH-building be in .profile, not in .bashrc?

You would know the rules better than I, but .bashrc is read in situations
where .profile is not, and PATH is important enough that I want it set
(correctly!) all the time.  The quintessential example of this is with

        ssh somehost some_obscure_command

I've been using the same environment setup for at least 15 years.
I build a lot of software and run make check or the logical equivalent
whenever I do.  coreutils is the first package I've encountered that
fails because of my environment.

Tim Mooney                                             address@hidden
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

reply via email to

[Prev in Thread] Current Thread [Next in Thread]