Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Libreoffice fails to build on aarch64 (pinebook pro)
Date: Thu, 19 Mar 2020 01:32:50 +0100	[thread overview]
Message-ID: <20200319003250.09ws1WhXP6ImCvRyY8oYb1K5jBDcXKnCMDN8Ru9vRAY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19642@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/19642#issuecomment-600925313

Comment:
Did you run this command inside chroot?


On 19 March 2020 04:26:18 GMT+07:00, Anjan Momi <notifications@github.com> wrote:
>`grep -r /usr/aarch64 /usr/lib/pkgconfig` returns nothing.
>
>-- 
>You are receiving this because you were mentioned.
>Reply to this email directly or view it on GitHub:
>https://github.com/void-linux/void-packages/issues/19642#issuecomment-600866998

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  parent reply	other threads:[~2020-03-19  0:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 22:36 [ISSUE] " anjandev
2020-03-15 14:35 ` pullmoll
2020-03-16  4:45 ` anjandev
2020-03-18 10:34 ` sgn
2020-03-18 10:35 ` sgn
2020-03-18 11:43 ` pullmoll
2020-03-18 21:26 ` anjandev
2020-03-19  0:32 ` sgn [this message]
2020-03-19 22:36 ` anjandev
2020-04-09  4:35 ` sgn
2020-04-10  5:35 ` anjandev
2020-04-14  9:51 ` sgn
2020-04-14 10:26 ` anjandev
2020-05-15 21:15 ` pullmoll
2020-05-16  1:43 ` sgn
2020-05-19 14:44 ` sgn
2020-05-19 14:59 ` sgn
2020-05-21 15:27 ` sgn
2020-05-21 17:48 ` anjandev
2020-09-15  1:46 ` KeepBotting
2020-09-15  1:48 ` ericonr
2020-09-15  1:49 ` ericonr
2020-09-15  1:49 ` ericonr
2020-09-15 13:44 ` KeepBotting
2020-09-15 13:47 ` KeepBotting
2020-09-15 14:10 ` [ISSUE] [CLOSED] " q66

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=20200319003250.09ws1WhXP6ImCvRyY8oYb1K5jBDcXKnCMDN8Ru9vRAY@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).