This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: importing another file into top-level include directory?
- From: Zack Weinberg <zack at codesourcery dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, binutils at sources dot redhat dot com
- Date: Mon, 23 Jun 2003 11:25:49 -0700
- Subject: Re: importing another file into top-level include directory?
- References: <200306231029.47712.bwilson@tensilica.com><200306231742.h5NHgIU02837@greed.delorie.com><200306231053.38779.bwilson@tensilica.com><200306231758.h5NHwg203175@greed.delorie.com>
DJ Delorie <dj@redhat.com> writes:
> libiberty/; libiberty's part of include/
> gcc: http://gcc.gnu.org
> Changes need to be done in tandem with the official GCC
> sources or submitted to the master file maintainer and brought
> in via a merge. Note: approved patches in gcc's libiberty
> are automatically approved in this libiberty also; feel free
> to merge them yourself if needed sooner than the next merge.
> Otherwise, changes are automatically merged, usually within
> a day.
>
> ("libiberty's part of include" means any file there common between gcc
> and src)
This discussion reminds me that I'd like to import include/filenames.h
into the gcc CVS. It would replace a bunch of xm-*.h gunk. That file
is listed as "part of BFD, the Binary File Descriptor library" -- does
that raise any issues? I don't anticipate needing to make any changes
to the file; gcc already uses all the same macro names.
zw