l = @INTL_LIBTOOL_SUFFIX_PREFIX@
transform = @program_transform_name@
From gettext.
I'm guessing that the idea was that you could link with a different version
of the library outside the build tree (and outside the source tree), but is
that actually used anywhere?
Yes, of course. Distros link bash against a system readline all the time.
There is lots of machinery in configure to make this work.
If it *is* used, I'd ideally like to see all the variables that reference
build directories have trailing slashes, unless they're completely empty
(meaning the current directory). This would probably need some adjustment
to the ‘configure’ script, or to autoconf.
What purpose would this serve?
Otherwise I'd rather just hard-code them as relative paths; I have a patch
to that effect if you're interested.
You'd be removing a documented feature that lots of people and distros use.
At least look at `configure --help' for what's available.
Secondly, where targets are built by running a command in another
directory, that secondary build process can inherit paths that no longer
point to the correct place.
Provide an example so I can fix it if it's a problem.
The tricky part is that this may or may not affect variables that point to
the source, depending on how ‘configure’ was invoked:
- when run in the source tree as ‘./configure’ it sets ‘BUILD_DIR=.’
(which I would like to see changed to ‘./’ or empty);
- when run as ‘../bash-source/configure’ it sets
‘BUILD_DIR=../bash-source’
- when run as ‘/home/me/src/bash/configure’ it sets
‘BUILD_DIR=/home/me/src/bash’
No, it doesn't. BUILD_DIR is always set using `pwd`. You might be thinking
of srcdir or topdir.
It might be tempting to thing "always use absolute paths", but that causes
its own problems:
- it won't work in a sandpit where the current user does not have
permission to reach $PWD from ‘/’;
If this were an issue affecting people who build bash, someone would have
reported it by now. I don't think this is a big deal right now.
- some of the paths wind up being embedded in the resulting executable,
and they may contain sensitive information such as a personal username or
home directory;
Like what? Show an example. I don't see any paths from the source or
build directories in the executable.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/