Re: Why doesn't Autotools makefile update Bash hash cache after install?

On 6/13/2017 9:47 AM, Zack Weinberg wrote: > On Tue, Jun 13, 2017 at 9:45 AM, Jeffrey Walton wrote: >> On Tue, Jun 13, 2017 at 8:40 AM, Zack Weinberg wrote: >>> On Tue, Jun 13, 2017 at 8:29 AM, Jeffrey Walton wrote: Why does

Re: Why doesn't Autotools makefile update Bash hash cache after install?

On Tue, Jun 13, 2017 at 8:40 AM, Zack Weinberg wrote: > On Tue, Jun 13, 2017 at 8:29 AM, Jeffrey Walton wrote: >> >> Why does Autotools produce a makefile which does _not_ update the >> cache under Bash shells? > > It can't. The rehash operation has to be

Re: Why doesn't Autotools makefile update Bash hash cache after install?

On Tue, Jun 13, 2017 at 9:45 AM, Jeffrey Walton wrote: > On Tue, Jun 13, 2017 at 8:40 AM, Zack Weinberg wrote: >> On Tue, Jun 13, 2017 at 8:29 AM, Jeffrey Walton wrote: >>> >>> Why does Autotools produce a makefile which does _not_ update

Re: Timeline for 2.70 (hit issue fixed in e17a30e9)

On 19 December 2016 at 15:03, Eric Blake wrote: > On 12/18/2016 09:22 PM, Andrei Borzenkov wrote: >> We got report that GRUB build fails under glibc 2.25 due to issue fixed >> in commit e17a30e9 (warnings about using major() etc from sys/types.h >> with -Werror). It was

Re: Why doesn't Autotools makefile update Bash hash cache after install?

On Tue, Jun 13, 2017 at 8:29 AM, Jeffrey Walton wrote: > > Why does Autotools produce a makefile which does _not_ update the > cache under Bash shells? It can't. The rehash operation has to be done in the shell that is the parent process of 'make install' (and any other

Why doesn't Autotools makefile update Bash hash cache after install?

Hi Everyone, After performing a 'make install', the Bash shell could still use the old program because the Bash hash cache was not updated for the program. 'which' will show the expected program (say /usr/local/bin/foo), but running 'foo' will result in the old program (say /usr/bin/foo). The