On Mar 13, 2007, Mark Mitchell <[EMAIL PROTECTED]> wrote:
> It treats only "/opt" as a common component of the two paths, rathe
> than "/opt/foo". If you use "/opt/foo/" (instead of "/opt/foo") for
> the last argument, the answer is as I expected. This seems odd to me;
> is it the intended behav
Daniel Jacobowitz wrote:
> On Mon, Mar 12, 2007 at 10:47:28PM -0700, Mark Mitchell wrote:
>> It treats only "/opt" as a common component of the two paths, rathe
>> than "/opt/foo". If you use "/opt/foo/" (instead of "/opt/foo") for
>> the last argument, the answer is as I expected. This seems odd
On Mon, Mar 12, 2007 at 10:47:28PM -0700, Mark Mitchell wrote:
> It treats only "/opt" as a common component of the two paths, rathe
> than "/opt/foo". If you use "/opt/foo/" (instead of "/opt/foo") for
> the last argument, the answer is as I expected. This seems odd to me;
> is it the intended b
I've noticed some behavior with make_relative_prefix that surprised
me. In particular, consider this program:
#include
extern char * make_relative_prefix (const char *progname,
const char *bin_prefix,
const char *p
