On 19 Jun 2005, at 10:15, Peter O'Gorman wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevin Horton wrote:
| Maybe there is a very good explanation for this, but it has me
| baffled. I've created a new package that won't build with gcc
4. So,
| I put a GCC: 3.3 line in the info file, thinking that this would
allow
| fink to tell the user he needed to run gcc_select 3.3. But, I
| discovered that if you have gcc_select 3.3, and there is a GCC: 3.3
| line in the .info file, fink tells you to run gcc_select 4.0. Why?
| This seems very backwards to me.
Please ignore the GCC field, go read the packaging manual, and use the
SetCC, SetCXX fields instead.
I am not sure if the GCC field has changed recently, but previously
it was
simply meant to be informative that the package used g++ of a certain
version and thus had ABI issues. Fink never used to look at the
field, don't
know if current versions do.
I've read the packaging manual, looked at man gcc, and finally found
the answer by doing a global search of info files for "setcc", now
that you've pointed me to it.
It would be useful if the packaging manual could provide specific
instructions on how to make a package use gcc 3.3, rather than just
having a vague instruction to set the cc flag. That might be enough
info for someone who already knows how to specify that fink use gcc
3.3, but it sure wasn't enough for me.
Thanks for the hint, and thanks for fink.
Kevin Horton
Ottawa, Canada
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
