From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EA055385828E; Fri, 15 Jul 2022 21:07:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EA055385828E From: "orbea at riseup dot net" To: gdb-prs@sourceware.org Subject: [Bug build/29372] New: slibtool build failure - make[2]: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'. Stop. Date: Fri, 15 Jul 2022 21:07:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: orbea at riseup dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2022 21:07:29 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29372 Bug ID: 29372 Summary: slibtool build failure - make[2]: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'. Stop. Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: orbea at riseup dot net Target Milestone: --- Created attachment 14213 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14213&action=3Ded= it Full Build Log When building gdb with slibtool the build fails because '../bfd/libbfd.a' is missing. This happens because of this earlier error. libtooldir=3D`rdlibtool --config | sed -n -e 's/^objdir=3D//p'`; \ if [ -f $libtooldir/libopcodes.a ]; then \ cp $libtooldir/libopcodes.a libopcodes.tmp; \ x86_64-pc-linux-gnu-ranlib --plugin /usr/libexec/gcc/x86_64-pc-linux-gnu/11.3.0/liblto_plugin.so libopcodes.tmp= ; \ /bin/sh ./../move-if-change libopcodes.tmp libopcodes.a; \ else true; fi rdlibtool: error: is missing. This is because of a hack as described in the code at 'bfd/Makefile.am'. # libtool will build .libs/libbfd.a. We create libbfd.a in the build # directory so that we don't have to convert all the programs that use # libbfd.a simultaneously. This is a hack which should be removed if # everything else starts using libtool. FIXME. https://sourceware.org/git/?p=3Dbinutils-gdb.git;a=3Dblob;f=3Dbfd/Makefile.= am;h=3D670e0598f55f29f3d5db4ffa18e40dcbc390f977;hb=3D13c3e10f98ff9b89c12161= e85bd576ea77460a83#l777 With slibtool --config works differently than with GNU libtool and peering = into the internal details for the libtool implementation is inherently not porta= ble. For example with slibtool I can get this output. $ slibtool --config gcc key value annotation --- ----- ---------- compiler gcc=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 target=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 host x86_64-unknown-linux-gnu native (cached in ccenv/host.mk) flavor linux derived from ar gcc-ar derived from ranlib x86_64-unknown-linux-gnu-ranlib derived from windres not applicable dlltool not applicable mdso not applicable Is there anything that can be done to remove this hack so that both slibtool and GNU libtool can be used to build gdb? This build system is intimidating= for someone not familiar with gdb. Also please see this Gentoo issue where it was first reported: https://bugs.gentoo.org/792969 --=20 You are receiving this mail because: You are on the CC list for the bug.=