It was my (perhaps ignorant?) understanding that GCC3.2 closed the gap (at least made the gap a lot smaller) between GCC and CCC. Am I wrong? (I have yet to test this, however, as I don't have GCC3.2 working on my alpha.)
Ted ----- Original Message ----- From: "Colin Watson" <[EMAIL PROTECTED]> To: <[email protected]>; <[email protected]> Sent: Wednesday, February 05, 2003 11:54 AM Subject: Re: (re)compiling debian packages with ccc > On Wed, Feb 05, 2003 at 11:11:31AM -0600, Bob McElrath wrote: > > Since everyone immediately gravitated to legal issues, I repost the > > technical piece. ;) > > > > I have joined the libtool mailing list and will add ccc as a recognized > > compiler to libtool. Are there other issues with > > apt-get source ... dpkg-buildpackage > > that anyone knows of? (aside from ccc failing to compile some files) > > You'll find that a lot of Debian source packages set CFLAGS themselves, > and may use gcc-specific flags. It's not obvious whether it's a bug that > they don't honour a user-set CFLAGS: I can see arguments on both sides > (autobuild consistency versus user overrides). Since as far as I know we > don't have any policy on this, you may well find yourself having to > change some debian/rules files. > > -- > Colin Watson [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
