From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Adam Duskett <aduskett@gmail.com>
Cc: Alexander Egorenkov <egorenar@linux.ibm.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Buildroot, S390X, and gobject-introspection build error help
Date: Tue, 10 Aug 2021 21:16:24 +0200 [thread overview]
Message-ID: <20210810191624.GS27036@scaer> (raw)
In-Reply-To: <CAFSsvmqHjEoN4r5Atj0jDMLr-CcY8SyQ1C=FYg1hywKrrn=2GQ@mail.gmail.com>
Adam, All,
On 2021-08-09 09:22 -0700, Adam Duskett spake thusly:
> On Sat, Aug 7, 2021 at 5:04 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > If I look at the git history (ellided for brevity):
[--SNIP--]
> > There are only 10 commits between a853a5d7..f9975537, and only 2
> > non-code commits on master after the merge.
> >
> > Adam: would you test that we update the prelink-cross version in
> > Buildroot? At least updating to the version as used by OE would seem
> > like the minimal, and then maybe check if we can update to master.
> >
> Yes, we can update to the latest in OE.
> No, we can't update to the latest in master, as it doesn't build prelink-rtld,
> which is super weird.
I have to admit that I did not understand this latest part... So, Had a
look at the history for prelink-cross, and it seems that master is very
close to the old svn tree from before Mark Hatle adopted the
then-orphaned prelink project.
So, the branch that we are interested in for cross-compilation is really
not the master branch, but the cross_prelink branch.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-10 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFSsvmpnjAFHs6SxcgLe1=smtJes=4f=qm2wi7W9D8qcC+kYEg@mail.gmail.com>
[not found] ` <878s1ezzle.fsf@oc8242746057.ibm.com>
[not found] ` <CAFSsvmpxdF3s-OBcPwMJw8Fp=6wGNib+7YddWoWELCKztEVn_Q@mail.gmail.com>
2021-08-07 12:04 ` [Buildroot] Buildroot, S390X, and gobject-introspection build error help Yann E. MORIN
2021-08-09 16:22 ` Adam Duskett
2021-08-10 19:16 ` Yann E. MORIN [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=20210810191624.GS27036@scaer \
--to=yann.morin.1998@free.fr \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=egorenar@linux.ibm.com \
--cc=thomas.petazzoni@bootlin.com \
/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.