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]

Re: Newbie maintainer's first commit


Hi Svein,

> I've gained write access to the binutils source tree, and I'd like
> to use my first opportunity to update the maintainers file. OK to
> commit?

> 2002-11-06  Svein E. Seldal  <Svein.Seldal@solidas.com>
> 
> 	* MAINTAINERS: Add self as TIC4X maintainer.

Approved - please apply.

> I have a pile of questions, as I've never done this before, so
> please guide me....
> 
> - How is the changelogs managed? Are they handled automatically by
> e.g. from the cvs ci log messages, or do I have to do a normal
> edit-then-"cvs ci" process on the appropriate changelog? (I think I
> know the answer, but I just wanna make sure.)

You have to create your own ChangeLog entries.  They are not generated
automatically.  If at all possible, always check in the changes to the
ChangeLog at the same time as you check in the patched files
themselves.  That way only a single email message is generated to the
binutils-cvs mailing list, and this message contains the details of
every modified file, including the ChangeLog(s).

> - When I am responsible for a specific target; What (specific)
> files/directories, if any, can I commit without getting prior
> approval?

You are responsible for any target-specific code that is directly
related to the target that you maintain (ie the TIC4X) in the binutils
source repository.  (Note - just because you are a binutils
target-specific maintainer this does not mean that you are
automatically a gdb or gcc target-specific maintainer).

> And if I change a top-level file, say config.sub, who
> performs the actual checkin (after approval), me or the responsible
> authority for this file?

That is decided between you.  When you submit a patch to a file that
you do not maintain, the approver of the patch will either check in
the patch (and say so) or else tell you that the patch is approved and
that you should then apply it and check it in.

> - Up until now, I have been using and testing binutils with "ordinary
> user" configure settings. I see that a special maintainer mode
> exists. What is the advantage of using this maintainer mode?

It causes autp-generated files to be automatically rebuilt each time
you run make in the relevant directories.  Of course to do this you
need the maintainer tools (autoconf, automake, etc) properly
installed.

> How can I enable and compile all targets?

Configure with:

        --enable-targets=all
or
        --enable-64-bit-bfd --enable-targets=all

The second form includes all the 64-bit targets as well as all the
32-bit targets, so you get everything.

> (Are there any other configure trick I should be aware of as a
> maintainer?)

If you add new files, remember to use "make dep-am" to rebuild the
dependencies in the Makefile.am files.

You can create what appears to be a combined FSF GCC and binutils
source tree through the creative use of symbolic links.  This allows
to you to configure and build an entire toolchain using the very
latest sources.

Cheers
        Nick


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