This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: makeinfo with gdb.texinfo
- From: "Eli Zaretskii" <eliz at elta dot co dot il>
- To: bje at wasabisystems dot com
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 02 Apr 2003 06:18:00 +0200
- Subject: Re: makeinfo with gdb.texinfo
- References: <20030331172211.GB10233@white> <20030331174222.GA30182@nevyn.them.org> <20030331175248.GC10233@white> <16008.34076.442297.792987@casey.transmeta.com> <m28yutwzhj.fsf@sashimi.local.>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> From: Ben Elliston <bje at wasabisystems dot com>
> Date: 02 Apr 2003 09:48:40 +1000
>
> > Yep. If it's like the "info" command
> > bash$ info -f gdb.info
> > gives you the installed version whereas
> > bash$ info -f ./gdb.info
> > gives you the version in the current directory.
>
> It's annoying behaviour and, IMHO, a bug.
Actually, it's a deliberately programmed feature. It's even described
in the manual: relative file names are interpreted as being relative
to one of the directories mentioned in the INFOPATH environment
variable (or in the default Info search path if INFOPATH is
undefined).
> Shouldn't info use copies in the local directory if they can be
> found, otherwise search the info path?
It mimics the behavior of a Unix shell when searching for executable
programs: the current directory is never searched, unless you have "."
in your PATH.