RangerRick at 01:31, 6 April 2006

2006-04-06T01:31:54Z

New page

{{Fink_Header}}

== The GCC field ==

A package needs a GCC field if anything in the package is compiled with c++ or g++.

This is a practical guide. For policy information see [http://fink.sourceforge.net/doc/packaging/compilers.php the packaging manual] and [http://www.mail-archive.com/fink-devel@lists.sourceforge.net/msg11877.html email to fink-devel] .

=== How to tell if a binary has been compiled with g++ ===

A good way to tell if a binary in your package was compiled with g++ is:

<pre>
nm -g $binary > symbols
c++filt3 < symbols > symbols.filt
diff symbols symbols.filt
</pre>

In most cases, if there is a difference it was compiled with g++ (some exceptions exist involving weirdly named C functions).

=== The script ===

The script [http://vasi.webhop.org/trac/browser/fink/trunk/scripts/gcc-field gcc-field] can check one or more packages to see if they need a GCC field.

To check one package, run it like this:

<pre>
gcc-field $package
</pre>

If it prints anything, the package doesn't have the right field (or is an exceptional case). If it doesn't print anything, you're ok!

You can also check all your packages:

<pre>
gcc-field --maintainer=Vasilevsky
</pre>

Or check a set of files:

<pre>
find ./root-foo | gcc-field -
</pre>

Please run <code>gcc-field --help</code> for details.

{{Fink_Header}}

[[Category: Fink|Policy:GCC]]
[[Category: GCC|Fink Policy]]
[[Category: Fink_Documentation|Policy:GCC]]
[[Category: Fink_Policy|GCC]]

Fink:Policy:GCC - Revision history

RangerRick at 01:31, 6 April 2006