public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: install mpfr-dev package on sourceware
Date: Sat, 7 Jan 2023 17:45:00 +0400	[thread overview]
Message-ID: <Y7l3XHgsEtJz3MMp@adacore.com> (raw)
In-Reply-To: <Y7lwRbdr5mTcnrjV@elastic.org>

> > I finally took a look at the config.log, and it's about the mpfr.h
> > missing. [...]
> > Can we have that installed, please? Hopefully that'll restore the
> > daily snapshots on sourceware.
> 
> OK, installed.

Thank you! That fixed the problem. Let's hope there isn't a next
problem lurking :).

> These snapshots are sources rather than binaries,
> which is good because distributed binaries should not be built on
> sourceware at all.

Agreed.

> OTOH even running configure/make should not
> really be necessary: have y'all considered building the tarballs
> via "git archive" or such?

This is a good question. The current process is really aweful
and prone to breaking (all the time, actually). The problem
is that this process predates me, and I don't have information
on why it is what it is today. One of the reasons might be that
it allows pre-generating some files so users of the snapshot
don't have to.

-- 
Joel

  reply	other threads:[~2023-01-07 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 12:47 Joel Brobecker
2023-01-07 13:14 ` Frank Ch. Eigler
2023-01-07 13:45   ` Joel Brobecker [this message]
2023-01-07 15:05     ` Mark Wielaard

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=Y7l3XHgsEtJz3MMp@adacore.com \
    --to=brobecker@adacore.com \
    --cc=fche@elastic.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).