This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

bfd.h installation location


Hiya,

Today I noticed that bfd.h gets installed under $prefix/include instead
of $exec-prefix/include (or maybe $exec-prefix/target-prefix/include),
but includes some host/target-specific data.  In particular, the
default word size:

/* The word size used by BFD on the host.  This may be 64 with a 32
   bit target if the host is 64 bit, or if other 64 bit targets have
   been selected with --enable-targets, or if --enable-64-bit-bfd.  */
#define BFD_ARCH_SIZE 64

/* The word size of the default bfd target.  */
#define BFD_DEFAULT_TARGET_SIZE 64

This creates a bit of a conflict when there's two different hosts (a
32 bit and a 64 bit) sharing the same include directory.  Whichever
installs last gets its bfd.h and the other loses.  I don't know how
harmful this may be, but sure would like to know.  Can anybody comment?

-- 
-Brendan (blc@redhat.com)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]