Moving the home directory should be OK--that's how I'm running right now.
I'm not sure why you should get that setenv error, but I'll leave that
aside for now. One perennial source of build problems is having files
installed in /usr/local/bin that override the standard ones in /usr/bin.
Just for verification, what do you get by typing 'which cc' in a terminal
window?
--
Alexander K. Hansen
Associate Research Scientist, Columbia University
Levitated Dipole Experiment
MIT Plasma Science and Fusion Center, 175 Albany Street, NW17-219
Cambridge, MA 02139-4213
Phone: 617-252-1818 Fax: 208-988-4057
On Fri, 5 Apr 2002, Jason Knight wrote:
> This may be beyond the beginners list, but I thought I'd start here
> before escalating to the users list...
>
> I just installed fink 0.3.2a, dselected a handfull of stuff (gimp, dia,
> pine, and associated dependencies, maybe a few others). Then I did a
> fink selfupdate and a fink update all in order to get the latest stable
> versions, and the process chokes on libtiff with:
> Configuring TIFF Software v3.5.7
>
> If configure does the wrong thing, check the file config.log for
> information that may help you understand what went wrong.
>
> Reading site-wide parameters from ./config.site.
> Oh no, not another powerpc-apple-darwin5.3 system...
>
> Cannot locate a working ANSI C compiler.
>
> We attempted to compile the following test program:
>
> ----------------------------------------------------------
> main(int argc, char* argv) { exit(0); }
> ----------------------------------------------------------
>
> with these compilers:
>
> gcc cc
>
> but none of them were successful.
>
> If your compiler is in a non-standard location, you can specify its
> location in several ways:
>
> o set the environment variable CC
> o create a config.local or config.site file that includes a
> definition for CC
> o supply it on the command line using -with-CC=<pathname>
>
> If command line options are required for ANSI C compilation, set the
> ENVOPTS parameter to these options in a similar way (either through
> an environment variable or config.local/config.site) and then rerun
> this script.
> configure:
> configure: Unrecoverable error! Once you've corrected the problem rerun
> this script.
> ### failed, exit code 1
> Failed: compiling libtiff-3.5.7-7 failed
> Now, I am a bear of very little brain when it comes to programming, but
> it doesn't make sense that all those other packages found cc just fine,
> but this one doesn't.
> Possibly relevant information: 400mhz g3 (b&w) 512mb ram, 10.1.3, dec
> 2001 dev tools, only thing "non standard" is that I used netinfo manager
> to relocate my home directory to a separate drive. One result that may
> be related is that after moving the home directory, I am greeted by
> "setenv: too many arguments" when I start up Terminal. But this only
> happens if I have the "source /sw/bin/init.csh" in .cshrc. Thoughts?
> Opinions? Words of encouragement?
>
> Thanks,
> Jason
>
>
> _______________________________________________
> Fink-beginners mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/fink-beginners
>
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
