All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/2] xfsprogs: fix libtoolize issues
Date: Fri, 20 Jan 2023 10:39:04 +1100	[thread overview]
Message-ID: <20230119233906.2055062-1-david@fromorbit.com> (raw)

HI folks,

Just hit the problem fixed in the first patch trying to build a
6.1.1 release. I don't know when the problem started, or whether
it's caused by upgrading userspace on the build machine, but I don't
really feel inclined to spend hours trying to track down some whacky
environmental issue that we really shouldn't need to care about
because the code that is breaking is there to support 15+ year old
build tools.

The second patch is just cleaning up the libtoolize mess that MacOS
platform support required that is no longer necessary because I
noticed it at the same time....

-Dave.



             reply	other threads:[~2023-01-19 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 23:39 Dave Chinner [this message]
2023-01-19 23:39 ` [PATCH 1/2] progs: autoconf fails during debian package builds Dave Chinner
2023-01-20 14:15   ` Carlos Maiolino
2023-01-19 23:39 ` [PATCH 2/2] progs: just use libtoolize Dave Chinner
2023-01-20 14:16   ` Carlos Maiolino

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=20230119233906.2055062-1-david@fromorbit.com \
    --to=david@fromorbit.com \
    --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 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.