Home Original page

Enable top-level recursive 'autoreconf'

Thomas Schwinge thomas@codesourcery.com
Thu Oct 19 10:42:26 GMT 2023 
Hi!

On 2023-10-19T11:57:33+0200, Andreas Schwab <schwab@suse.de> wrote:
> On Okt 19 2023, Thomas Schwinge wrote:
>> On 2023-10-18T15:42:18+0100, R jd <3246251196ryan@gmail.com> wrote:
>>> I guess I can ask, why there is not a recursive approach for configuring
>>> GCC. e.g. AC_SUBDIRS in the top level?
>>
>> ('AC_CONFIG_SUBDIRS' you mean.)  You know, often it just takes someone to
>> ask the right questions...  ;-)
>>
>> What do people think about the attached
>> "Enable top-level recursive 'autoreconf'"?  Only lightly tested, so far.
>
> The top-level files are shared with binutils-gdb, which has a different
> set of subdirs.

Good point, thanks!  Fortunately, the failure mode for non-existing
directories is non-fatal (skipped with 'subdirectory [...] not present'
diagnostic); with my original "Enable top-level recursive 'autoreconf'"
(also re-attached) applied to Binutils/GDB Git master branch, we get:

    $ PATH=[...] autoreconf -v
    autoreconf: Entering directory `.'
    autoreconf: configure.ac: not using Gettext
    autoreconf: running: aclocal
    autoreconf: configure.ac: tracing
    autoreconf: configure.ac: subdirectory c++tools not present
    autoreconf: configure.ac: subdirectory fixincludes not present
    autoreconf: configure.ac: subdirectory gcc not present
    autoreconf: configure.ac: subdirectory gcc/m2 not present
    autoreconf: configure.ac: subdirectory gnattools not present
    autoreconf: configure.ac: subdirectory gotools not present
    autoreconf: configure.ac: adding subdirectory intl to autoreconf
    autoreconf: Entering directory `intl'
    [...]
    autoreconf: Leaving directory `intl'
    autoreconf: configure.ac: subdirectory libada not present
    autoreconf: configure.ac: subdirectory libatomic not present
    autoreconf: configure.ac: adding subdirectory libbacktrace to autoreconf
    autoreconf: Entering directory `libbacktrace'
    [...]

So we could (a) simply list *all* directories in the shared top-level
'configure.ac', or (b) configure GCC vs. other projrcts via a non-shared
file ('m4_include([config/AC_CONFIG_SUBDIRS.m4])' or similar -- is there
an established procedure for non-shared top-level files)?  (I don't have
a strong preference either way.)

It's just GCC and Binutils/GDB, or are the top-level files also shared
with additional projects?


Grüße
 Thomas


-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Enable-top-level-recursive-autoreconf.patch
Type: text/x-diff
Size: 4234 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20231019/d619248d/attachment-0001.bin>
More information about the Binutils mailing list