On Thu, Sep 10, 2009 at 10:33:02PM +0100, Stephen Gran wrote: > This one time, at band camp, Kurt Roeckx said: > > This is perfectly expected behaviour for a compiler libtool does > > not know about. Either you need to tell it what CC is during > > configure, or use --tag=CC. > > I'm not sure what the bug is, then - configure picks up a compiler (on > my sid amd64 system, it picks it up as 'gcc', and in the case of the > submitter, it picks it up as '/usr/bin/gcc'). Not that it is > necessarily a libtool bug, but a) why should that make a difference to > libtool, and b) what is freeradius supposed to do differently?
The log file shows it using /usr/bin/libtool. This is a preconfigured libtool, so not one that is normally generated by the configure script of the package you're trying to build. So it doesn't know that you set CC to something else. If you want to avoid any problems when using /usr/bin/libtool, you have to use --tag=CC to tell it that it's a C compiler. You could argue that it can try and strip off the path to see if it matches any of the compilers it's configured for. If you think that's useful, file a wishlist bug. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
