> > I don't see why not. chicken should be using /usr/bin as its binary > directory, and so when xcode-select changes the install location, it will > still work. (I think the shims just look up the actual XCode location and > then exec() it -- they're not symlinks nor are they physically updated in > place, AFAIK.) Am I missing something?
If I compile the base chicken system using toolchain/xcode-version A with the c-compiler in some default location, xcode-select to another toolchain/xcode-version and then install an egg using the base chicken system, that calls whatever c-compiler is currently in /usr/bin, then we surely might get into trouble regarding binary-compatibility or c-compiler version differences, ABIs, or whatnot, right? felix _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
