From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/asterisk: fix host build
Date: Sun, 24 Sep 2017 19:08:50 +0200 [thread overview]
Message-ID: <20170924170850.GC2660@scaer> (raw)
In-Reply-To: <20170924170405.GB2660@scaer>
Arnout, All,
On 2017-09-24 19:04 +0200, Yann E. MORIN spake thusly:
> On 2017-09-24 18:51 +0200, Arnout Vandecappelle spake thusly:
> > On 24-09-17 18:33, Yann E. MORIN wrote:
[--SNIP--]
> > > +# Even though menuselect is an autotools package, it is not an automake
> > > +# package and does not have an 'install' rule, as asterisk does expect
> > > +# it to be in a sub-directory of its source tree. We do so by copying
> > > +# the full menuselect build tree as a pre-configure hook in the target
> > > +# variant.
> > > +# However, the sanity checks on host packages are not run on menuselect.
> > > +# But we still want to catch that menuselect has the proper rpath set,
> > > +# for example, as it uses host libraries that we do build, like
> > > +# host-libxml2.
> > > +# So we do manually install the menuselect tool.
> > > define HOST_ASTERISK_INSTALL_CMDS
> > > - @:
> > > + $(INSTALL) -D -m 0755 $(@D)/menuselect/menuselect \
> > > + $(HOST_DIR)/bin/asterisk-menuselect
> >
> > So then could you symlink to this instead of copying the entire tree?
>
> Nope, because all the intermediate object files would missing, so the
> Makefile would try to build them, and would then rebuild menuseclect as
> well, and all those efforts would have been in vain...
Oh, and I forgot: it needs a file, makeopts, generated by configure, but
running menuselect's configure in the target variant is the things we
want to avoid in the first place.
And to be sure, I tried what you suggest, and it does not work (build
failure).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-09-24 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 16:33 [Buildroot] [PATCH] package/asterisk: fix host build Yann E. MORIN
2017-09-24 16:51 ` Arnout Vandecappelle
2017-09-24 17:04 ` Yann E. MORIN
2017-09-24 17:08 ` Yann E. MORIN [this message]
2017-09-26 22:41 ` Arnout Vandecappelle
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=20170924170850.GC2660@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.