From: John L. <le...@cs...> - 2006-03-22 02:52:46
|
On Tue, March 21, 2006 6:39 pm, William S Fulton said: > felix winkelmann wrote: >> On 3/10/06, William S Fulton <ws...@fu...> wrote: >>>Hi John >>> >>>I've backed out that patch until the detection of the chicken compiler >>>is verified in configure.in. >>> >>>Not sure what to do if both C# and chicken are both installed, as >>>unlikely as it may be. Perhaps we can do something using the full path >>>to one or the other csc programs. >> >> Well, wouldn't it be sufficient to check for the "chicken" executable >> and >> assume csc is chicken's csc, and C#'s csc otherwise? I'm rather helpless >> with autoconf/shell/makefile hacking, so I better don't supply a patch >> (But if you need anything, I will try my best, of course). >> >> If chicken is installed, csc will have the same path, BTW. >> > That is a big assumption and not necessarily true. With soft links and > most applications being installed in one of the bin directories, and > people moving binaries around it isn't a robust approach. Doesn't > chicken's csc produce anything to positively identify it with --version > or --help or some other command line? All we need to do is grep for some > text in the output that will identify it. If you send me the exact > output of something like this, I'll modify configure.in to identify it. > > William > > I still have an old version of chicken installed, but here is my output. Note that is a capital "V", or -version $ csc -V _______ _ __ / ___/ / (_)___/ /_____ ___ / /__/ _ \/ / __/ '_/ -_) _ \ \___/_//_/_/\__/_/\_\\__/_//_/ Version 2, Build 2 - linux-unix-gnu-x86-64 - [ 64bit dload ] (c)2000-2005 Felix L. Winkelmann Enter "chicken -help" for information on how to use it. $ csc -version _______ _ __ / ___/ / (_)___/ /_____ ___ / /__/ _ \/ / __/ '_/ -_) _ \ \___/_//_/_/\__/_/\_\\__/_//_/ Version 2, Build 2 - linux-unix-gnu-x86-64 - [ 64bit dload ] (c)2000-2005 Felix L. Winkelmann Enter "chicken -help" for information on how to use it. |