Bug#344446: [klibc] Don't hardcode paths in klcc
* 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, generated Perl script, so portability is not an issue. It would be nice if people could specify whether they want this during build time. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344446: [klibc] Don't hardcode paths in klcc
* 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. Specifically, klcc in Debian is broken right now because it has /usr/local/bin/ as path for CC - even though I still need to investigate how this happened since there shouldn't be a gcc in /usr/local/bin. So while I'm aware we need to fix that on our side, I still think putting hardcoded paths in the script is generally a bad idea. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344446: [klibc] Don't hardcode paths in klcc
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 installation-specific, generated Perl script, so portability is not an issue. It would be nice if people could specify whether they want this during build time. Perhaps you could clarify why you *wouldn't*. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344446: [klibc] Don't hardcode paths in klcc
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 you make it less portable. 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, generated Perl script, so portability is not an issue. -hpa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
