Bug#344446: [klibc] Don't hardcode paths in klcc

2006-01-26 Thread H. Peter Anvin
Martin Michlmayr wrote: * H. Peter Anvin <[EMAIL PROTECTED]> [2006-01-25 20:46]: In this case, though, it's probably required, since otherwise you could end up with some very strange results when cross-compiling. I'm not sure what the ideal answer is, but I think this is wrong. klcc is a insta

Bug#344446: [klibc] Don't hardcode paths in klcc

2006-01-26 Thread Martin Michlmayr
* H. Peter Anvin <[EMAIL PROTECTED]> [2006-01-26 08:53]: > >It would be nice if people could specify whether they want this during > >build time. > > Perhaps you could clarify why you *wouldn't*. Because the machine I build klibc on might be different to the one where I want to run klcc. Specifi

Bug#344446: [klibc] Don't hardcode paths in klcc

2006-01-26 Thread Martin Michlmayr
* H. Peter Anvin <[EMAIL PROTECTED]> [2006-01-25 20:46]: > In this case, though, it's probably required, since otherwise you > could end up with some very strange results when cross-compiling. > I'm not sure what the ideal answer is, but I think this is wrong. > > klcc is a installation-specific,

Bug#344446: [klibc] Don't hardcode paths in klcc

2006-01-25 Thread H. Peter Anvin
Martin Michlmayr wrote: Stop makeklcc.pl from hardcoding paths of cc, ld and strip in the klcc script it generates. Using hardcoded paths is generally a bad idea. First, the whole idea of $PATH is that you don't need to hardcode paths. Second, klcc is a Perl script but my hardcoding the paths y