From: Dave Chinner <david@fromorbit.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs list <linux-xfs@vger.kernel.org>
Subject: Re: xfsprogs 4.17.0 error building xfs_repair
Date: Wed, 1 Aug 2018 14:21:46 +1000 [thread overview]
Message-ID: <20180801042146.GI2234@dastard> (raw)
In-Reply-To: <CAJCQCtSpiPiG1S0tq4j+D4DsGf0caTtQCHWyVJJxrT2P5MxPNQ@mail.gmail.com>
On Tue, Jul 31, 2018 at 08:02:17PM -0600, Chris Murphy wrote:
> Hi,
> I'm doing this on Fedora 28, I'm including the entire output from
> exporting environment variables from doc/INSTALL so it's kinda long...
>
> [chris@f28s xfsprogs-dev]$ git reset --hard origin/master
> HEAD is now at 0821de47 xfsprogs: Release v4.17.0
>
> [chris@f28s xfsprogs-dev]$ export TAR=/usr/bin/tar
> [chris@f28s xfsprogs-dev]$ export LIBTOOL=/usr/bin/libtool
> [chris@f28s xfsprogs-dev]$ export INSTALL_GROUP=wheel
> [chris@f28s xfsprogs-dev]$ export
> LOCAL_CONFIGURE_OPTIONS="--enable-gettext=no --enable-blkid=no
> --enable-librt=no"
You shot yourself in the foot.
....
> [CC] versions.o
> [CC] xfs_repair.o
> [LD] xfs_repair
> /tmp/cc95QLol.ltrans8.ltrans.o: In function `progress_rpt_thread.lto_priv.352':
> <artificial>:(.text+0xa2c9): undefined reference to `timer_create'
> <artificial>:(.text+0xa2e4): undefined reference to `timer_settime'
> <artificial>:(.text+0xa570): undefined reference to `timer_delete'
These functions are in librt, and you told the build not to use it...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-08-01 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 2:02 xfsprogs 4.17.0 error building xfs_repair Chris Murphy
2018-08-01 4:21 ` Dave Chinner [this message]
2018-08-01 4:37 ` Chris Murphy
2018-08-01 4:39 ` Eric Sandeen
2018-08-01 5:06 ` Chris Murphy
2018-08-01 5:09 ` Eric Sandeen
2018-08-01 11:49 ` Carlos Maiolino
2018-08-01 13:18 ` Eric Sandeen
2018-08-01 18:43 ` Chris Murphy
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=20180801042146.GI2234@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.