From: Alan W. I. <ir...@be...> - 2002-12-28 07:14:41
|
On Fri, 27 Dec 2002, Maurice LeBrun wrote: > [...]So I took your advice and tried using cc > instead of gcc by inserting the following line in configure.ac: > > AC_PROG_CC(cc cl egcs gcc) > > which overrides the default search order, like AC_PROG_CXX. > Then the build went: > > ... > cc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../libltdl -g -c plcont.c -KPIC -DPIC -o plcont.o > mv -f plcont.o .libs/plcont.lo > ... > > So you see, there is logic in there to build the object then move it, use it > in the new location, and clean up appropriately. And I notice the correct -KPIC flag is in there as well. > > The question is, how can I trigger this behavior for KCC? That is a tough one. Sorry I cannot be any help on that. My only real suggestion is to try an extremely simple example to see if the correct behaviour is triggered. If that is no go, then it is probably time to take the results of that simple example to the libtool list to get the definitive answers about KCC support. But you also might find that the simple example works fine. Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |