| Commit message (Collapse) | Author | Age |
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We used to say things like:
case "$gccversion" in
1*) ...
but that was wrong because it now starts to catch version 10 as well,
for cases that only pertained to gcc version 1!
We now need to say:
case "$gccversion" in
1) ...
2) ...
etc. to handle versions 1 and 2 differently.
Thanks to Dmitry Butskoy for spotting this bug.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The actual programs were trying to load the exclusions file before reading
.package (or even, in one case, without trying to read it at all). I failed
to notice this because I had a "-X" option that duplicated the intended use
of the setting in my .package file.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's not only bfd_get_section_vma() which is impacted! The change in
the BFD library, starting with 2.34, is rather that:
- bfd_section_xxx() accessors now take only the BFD section as argument.
- bfd_get_section_xxx() accessors, which used 2 arguments, are removed.
The first argument in bfd_get_section_xxx() calls was the BFD descriptor
and it was purely ignored in recent versions of the library.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a private unit from gtk-gnutella that should not have been
made available to metaconfig as it is not of general purpose.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After generating config.sh, this is a place where optional generation
can happen, before going on with the .SH file extractions and
dependency computations.
Typically, this can be used to generate a revision.h file.
|
| | | |
| | | |
| | | |
| | | | |
Fixes issue #15.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The commenting scheme used in the man pages was three consecutive single
quotes (`'''') at the beginning of a line. his works, but `gtroff' gives
a warning about an undefined macro (namely `'''), which is harmless, but
irritating.
To avoid this, this commit changes the schema to start the line with
`.\"' which causes the line to be treated as an undefined request and
thus ignored completely.
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
[updated to current dist by Dominic Hargreaves <dom@earth.li>]
|
| | | |
| | | |
| | | |
| | | | |
This fixes syntax errors in makedist, patbase, patcil, patclean,
patcol, patdiff, patname, and patsnap.
|
| |\| |
| | | |
| | | |
| | | | |
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
|
| | |\|
| | | |
| | | |
| | | | |
Signed-off-by: Manoj Srivastava <srivasta@debian.org>
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Added "-X exclusions-file" to ignore symbols.
Symbols like "index" may be present in source files but only accidentally.
This may occur in a comment, and not because index() is used and needs
to be dealt-with by metaconfig.
The -X option provides the ability to list symbols like "index" that we do not
want processed by metaconfig (and metaxref).
To avoid having to always remember to supply -X when running metaconfig or
metaxref, packinit was improved to record the name of the file that is holding
the symbols we wish to exclude: when an exclusion file is recorded, it will be
automatically picked by metaconfig (and metaxref). It is still possible to use the
-X option on the command line to supersede any setting in the .package file.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Otherwise, when mconfig is run with that option, the metaxref would
confusingly refer to excluded symbols.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This usage has produced a depreaction warning since Perl 5.000, and was
finally removed in Perl 5.22.
|
| | | | | |
|
| | | |/
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Packages can use this option to list symbols that shouldn't bring in the
corresponding units. For example, Perl need not provide support for BSD
index(3) as an alternative to C89 strchr(3), but "index" is the name of a
Perl builtin, so that string in the source files is misunderstood by
metaconfig as an attempt to use the BSD function.
With this change, Perl can deal with this situation by adding "index" (and
"rindex") to an exclusion list.
|
| | | | |
|
| | | |
| | | |
| | | | |
qw(...) cannot contain comments. The previous "comment" was interpreted as part of the qw list.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The last argument of the pick command is the target, usually the current
unit name, or an explicit relative path. If it is the unit name, then
it is better represented by using the %< macro in case the unit file is
copied or renamed later.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In particular, validate the special "pick" command further to avoid
nasty surprises when running metaconfig.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
This is not complained about by mlint, but it just looks right to
declare what we use
|
| | | |
| | | |
| | | |
| | | | |
I cannot find the original commit message to this fix in the
perl tree, but - even if outdated - seems very legit
|