From: "Arsen Arsenović" <arsen@aarsen.me>
To: jacob navia <jacob@jacob.remcomp.fr>
Cc: binutils@sourceware.org
Subject: Re: Compiling binutils: .bootstrap doesn't work
Date: Tue, 26 Sep 2023 23:52:15 +0200 [thread overview]
Message-ID: <86il7wppk4.fsf@aarsen.me> (raw)
In-Reply-To: <F58BBB3E-A18D-43C7-B5AF-005F2464534C@jacob.remcomp.fr>
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
jacob navia <jacob@jacob.remcomp.fr> writes:
> After downloading automate and autoconf (see my previous message) I invoked « .bootstrap » again, as specified in the documentation.
>
> I obtained:
> configure.ac:2535: warning: The macro `AC_PROG_CC_C99' is obsolete.
> configure.ac:2535: You should run autoupdate.
> ./lib/autoconf/c.m4:1659: AC_PROG_CC_C99 is expanded from...
> configure.ac:2535: the top level
> configure.ac:3846: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but not m4_defun'd
> acinclude.m4:2363: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...
> configure.ac:3846: the top level
> configure.ac:3849: warning: AC_ENABLE_SHARED is m4_require'd but not m4_defun'd
> acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
> configure.ac:3849: the top level
> configure.ac:3849: warning: LT_INIT is m4_require'd but not m4_defun'd
> acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
> configure.ac:3849: the top level
> configure.ac:4052: warning: AC_PROG_LEX without either yywrap or noyywrap is obsolete
> ./lib/autoconf/programs.m4:716: _AC_PROG_LEX is expanded from...
> ./lib/autoconf/programs.m4:709: AC_PROG_LEX is expanded from...
> aclocal.m4:411: AM_PROG_LEX is expanded from...
> configure.ac:4052: the top level
> configure.ac:2730: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure:16286: error: possibly undefined macro: AC_LIBTOOL_PROG_COMPILER_PIC
> configure:16383: error: possibly undefined macro: AC_ENABLE_SHARED
> autoreconf: error: /usr/bin/autoconf failed with exit status: 1
>
> What scares me is all those « X86 » and « WIN32_DLL » , since I am running in a riscv machine. GMP is completely lost!
These are macro expansions. They happen on any platform
> OK, I can’t compile binutils any more
Please just use generated files, or follow README-maintainer-mode to
fetch the right versions of tools. Note that autoreconf also won't
handle everything in the toolchain case, since there are many build
systems, rather than just one, when building the toolchain.
I recommend that you either fetch GMP from gmplib.org and extract and
rename it to 'gmp', or a binutils distribution from
https://ftp.gnu.org/gnu/binutils/ and configure that (as it should not
require GMP), or to --disable-gdb.
Do not regenerate any files.
Hope that helps, have a lovely night :-)
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
prev parent reply other threads:[~2023-09-26 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:06 jacob navia
2023-09-26 21:52 ` Arsen Arsenović [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86il7wppk4.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=jacob@jacob.remcomp.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).