On 02/17/2016 04:20 AM, David Howells wrote:
Hi,
Do the macro_list and fixinc.sh files need to be installed? Does anything
outside of gcc actually use them? If macro_list is a zero length file, can it
be left out of the installation (fixinc.sh seems to test for its presence
before trying to use it) or given a blank line?
The reason I ask is that rpmlint gives an error on empty files, and macro_list
is empty at least for h8300 and sh64.
fixinc.sh should depend on your deployment model.
Typically fixinc.sh is run during the build process to address certain
deficiencies in the system header files. THe fixed includes would be
then installed into a gcc private directory.
You could have a deployment model where RPMs provide the compilers, but
fixinc is run during rpm installation. This would make more sense for
cross compilers or when the rpms provide binaries which run on many
different systems which might have slight differences in their header files.
macro_list, I believe is used by the fixinc procedure. So if you have a
deployment model where you're running fixincludes at rpm installation
time, then you'll want to include macro_list.
Frankly these rpmlint things seem like more trouble then they're worth.
There's good reasons why a package might ship empty files.
jeff
