From: Matthew Brooks <matthewfbrooks@mailbox.org>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: mariadb build fails "Failing test(s): main.mysqldump"
Date: Sun, 6 Jan 2019 20:43:37 -0600 [thread overview]
Message-ID: <20190106203542.0c1b2d9a@mailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Not sure why stuff like sdl2 and ffmpeg end up trying to pull in a database manager, but the build is failing for me.
This seems to be different from the mariadb issues posted in the bug list a few months ago, as I've got ~40GB of free space, and the build wasn't getting OOM killed like python was a while back, so I don't expect it's available RAM either.
Weirdly, mariadb seems to have built fine on my desktop several weeks ago, but fails on my laptop. Not sure if that was just lucky timing or the greater specs.
Anyway,the guix version used is:
e4be1faa43eb9897e62eefd234ab3a98f324e898
which should be from only a week or two ago.
I'm also on standard x86_64 GNU/Linux.
If needed, I can try a guix pull and try again, though mariadb has been failing consistently for a while now, and I've pulled guix at least once since then to check if that was the problem, so I suspect the problem isn't guix unless a fix was applied only very recently.
I've attached the bzipped log instead of inserting it as text, since it's very long.
Anyway, thanks for your time everyone, and hopefully somebody knows what's going wrong here.
Matthew Brooks
[-- Attachment #2: id9xv4prjx1iqrx0m4zc7grplpm162-mariadb-10.1.37.drv.bz2 --]
[-- Type: application/x-bzip, Size: 338537 bytes --]
next reply other threads:[~2019-01-07 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 2:43 Matthew Brooks [this message]
2019-01-08 5:00 ` mariadb build fails "Failing test(s): main.mysqldump" Matthew Brooks
2019-01-09 3:12 ` Matthew Brooks
2019-01-14 4:26 ` Matthew Brooks
2019-01-23 2:06 ` Matthew Brooks
2019-01-24 2:19 ` Matthew Brooks
-- strict thread matches above, loose matches on Subject: below --
2019-02-07 8:13 Nikolai Merinov
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190106203542.0c1b2d9a@mailbox.org \
--to=matthewfbrooks@mailbox.org \
--cc=help-guix@gnu.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).