From: Thomas Deutschmann <whissi@gentoo.org>
To: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: xfsdump: Building inventory: gcc: fatal error: no input files
Date: Wed, 12 Feb 2020 16:26:05 +0100 [thread overview]
Message-ID: <ab3571df-40c1-dad8-800f-48c1a64355fe@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2365 bytes --]
Hi,
not sure if anybody has noticed yet but when building xfsdump, there
seems to be a non-fatal build error:
> Building inventory
> [LTDEP]
> gcc: fatal error: no input files
> compilation terminated.
With remake I see
> ~/sys-fs/xfsdump-3.1.9/work/xfsdump-3.1.9/inventory $ remake --trace=read
> Reading makefile 'Makefile'...
> Reading makefile '../include/builddefs' (search path) (no ~ expansion)...
> Reading makefile '../include/buildmacros' (search path) (no ~ expansion)...
> Reading makefile '../include/buildrules' (search path) (no ~ expansion)...
> Reading makefile '../include/builddefs' (search path) (no ~ expansion)...
> Reading makefile '.ltdep' (search path) (don't care) (no ~ expansion)...
> [LTDEP]
> x86_64-pc-linux-gnu-gcc -MM -O2 -pipe -march=ivybridge -mtune=ivybridge -mno-xsaveopt -Wno-error=clobbered -Wno-error=format-overflow -Wno-error=unused-function -Wno-error=implicit-function-declaration -Wno-error=maybe-uninitialized -frecord-gcc-switches -D_GNU_SOURCE -O2 -pipe -march=ivybridge -mtune=ivybridge -mno-xsaveopt -Wno-error=clobbered -Wno-error=format-overflow -Wno-error=unused-function -Wno-error=implicit-function-declaration -Wno-error=maybe-uninitialized -frecord-gcc-switches -DNDEBUG -DVERSION=\"3.1.9\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"xfsdump\" -I../include -DENABLE_GETTEXT -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -funsigned-char -fno-strict-aliasing -Wall | /bin/sed -e 's,^\([^:]*\)\.o,\1.lo,' > .ltdep
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> Reading makefile 'Makefile'...
> Reading makefile '../include/builddefs' (search path) (no ~ expansion)...
> Reading makefile '../include/buildmacros' (search path) (no ~ expansion)...
> Reading makefile '../include/buildrules' (search path) (no ~ expansion)...
> Reading makefile '../include/builddefs' (search path) (no ~ expansion)...
> Reading makefile '.ltdep' (search path) (don't care) (no ~ expansion)...
> remake: Nothing to be done for 'default'.
Seen in xfsdump-3.1.6-3.1.9.
Not just in Gentoo, it's also present in Debian, see
https://buildd.debian.org/status/fetch.php?pkg=xfsdump&arch=amd64&ver=3.1.6%2Bnmu2%2Bb2&stamp=1526577413&raw=0
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2020-02-12 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 15:26 Thomas Deutschmann [this message]
2020-10-02 17:44 ` xfsdump: Building inventory: gcc: fatal error: no input files Eric Sandeen
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=ab3571df-40c1-dad8-800f-48c1a64355fe@gentoo.org \
--to=whissi@gentoo.org \
--cc=linux-xfs@vger.kernel.org \
/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 NNTP newsgroup(s).