public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Petr Ovtchenkov" <ptr@void-ptr.info>,
	"Érico Nogueira" <ericonr@disroot.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 1/1] support cross compilation
Date: Wed, 21 Dec 2022 13:26:19 +0100	[thread overview]
Message-ID: <a9dab2c5f3f7dde1010b9dd3daf339fc908c45b9.camel@klomp.org> (raw)
In-Reply-To: <20210526163428.2888e7ef@void-ptr.info>

Hi,

It looks like I missed this. Sorry.

On Wed, 2021-05-26 at 19:34 +0300, Petr Ovtchenkov wrote:
> On Wed, 26 May 2021 12:41:51 -0300
> Érico Nogueira <ericonr@disroot.org> wrote:
> 
> > 
> > Yes, we really cross.
> 
> It doesn't matter because
> 
> > We always use the release tarballs, which already have the %_dis.h
> > files. This explains why we haven't hit any issues.
> 
> 
> > Anyway, couldn't you (re)use the distribution tarball generation
> > stuff
> > for cross setups from git master?
> 
> I can. But I haven't problems with building it "directly from VCS"
> too,
> as you see. Nevertheless there are opinion that code from VCS
> could be smoothly building without procedures behind scene.

Isn't it simpler to first do a local make dist and then build cross
from that?

Cheers,

Mark

      reply	other threads:[~2022-12-21 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210526073239.21270-1-ptr@void-ptr.info>
2021-05-26  7:32 ` Petr Ovtchenkov
2021-05-26 13:09   ` Érico Nogueira
2021-05-26 13:58     ` Petr Ovtchenkov
2021-05-26 15:41       ` Érico Nogueira
2021-05-26 16:34         ` Petr Ovtchenkov
2022-12-21 12:26           ` Mark Wielaard [this message]

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=a9dab2c5f3f7dde1010b9dd3daf339fc908c45b9.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ericonr@disroot.org \
    --cc=ptr@void-ptr.info \
    /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).