[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Buildbot failure
|
From: |
Martin Schanzenbach |
|
Subject: |
Re: Buildbot failure |
|
Date: |
Fri, 13 Nov 2020 05:45:50 +0900 |
|
User-agent: |
Evolution 3.38.1 (3.38.1-1.fc33) |
You forgot a linker flag for gnunet-messenger.
(https://git.gnunet.org/gnunet.git/commit/?id=96d7027e6b31acca9106a61d0495c88829dc4c85
)
Note that if you have installed (make install) a library (in this case
libgnunetidentity), the linker is able to "automagically" resolve/find
and link it.
Buildbot does not do "make install". So the linked libraries must be
provided explicitly. This is a good check to find missing linker flags.
BR
On Fri, 2020-11-13 at 04:52 +0900, Martin Schanzenbach wrote:
> Just merge it again. It may be a fragment due to buildbot's
> incremental
> builds. We might want to switch to full rebuilds anyway at some
> point.
>
> BR
>
> On Thu, 2020-11-12 at 17:48 +0100, TheJackiMonster wrote:
> > Hi,
> >
> > so I squashed all commits from my branch, merged into master,
> > tested
> > compilation again with experimental and without it. Then I pushed
> > it
> > to
> > the repository but the buildbot failed.
> >
> > https://buildbot.gnunet.org/#/builders/6/builds/266
> >
> > Now I panically reverted the merge and it failed again. Can anyone
> > explain me what I did wrong? Is there a way to reverse the commits
> > completely if they really break compilation?
> >
> > https://buildbot.gnunet.org/#/builders/6/builds/267
> >
> > Sorry for everone.
> > Jacki
>
signature.asc
Description: This is a digitally signed message part