mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: "Chin You Wen (WMSC-HW)" <youwen@willowglen.asia>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Iteratively Make & Make Install Subpackages
Date: Tue, 12 Mar 2019 12:45:19 +0100	[thread overview]
Message-ID: <20190312114519.oydqai5vqajilymc@pengutronix.de> (raw)
In-Reply-To: <CAJ1upxe32baQsZfr27nPc9D+_3TFmxTeuhFdVk+4S8aRCTfmqw@mail.gmail.com>

Hi,

ptxdist respects the 'select' statements in Kconfig, so you should be
able to make ptxdist build libsepol before libselinux by adding a
"select LIBSEPOL" to your "config LIBSELINUX" entry in
rules/libselinux.in. You can look at many other packages as an example,
or at this section [1] in the docs. But make sure that the 'select' is
directly in the "config LIBSELINUX" option and not in a sub-option,
otherwise the dependency parser will not find it.

[1]: https://www.ptxdist.org/doc/dev_manual.html#managing-external-compile-time-dependencies

Hope that solves your problem?

 - Roland

On Tue, Mar 12, 2019 at 06:56:24PM +0800, Chin You Wen (WMSC-HW) wrote:
> Hello,
> 
> I am compiling the SELINUX userspace tools (
> https://github.com/SELinuxProject/selinux) and I encountered this error.
> 
> load_policy.c:15:25: fatal error: sepol/sepol.h: No such file or directory
> compilation terminated.
> 
> The sub-package libselinux depends on libsepol, but by default the PTXDist
> rule file does not run makefile sections in sequential order, i.e. it
> executes the compile section for all sub-packages first, followed by
> install section. This results in the required libsepol dependencies to not
> be found when libselinux needs it, and thus the above error.
> 
> Is there any way to accomplish this without splitting the sub-packages into
> separate rule files? I am thinking of calling something like this:
> 
> @$(call compile, libsepol)
> @$(call install, libsepol)
> @$(call compile, libselinux)
> @$(call install, libselinux)
> 
> but I am unsure if that is possible, or what the correct syntax is. Kindly
> advise. Thanks.
> 
> 
> Regards,
> You Wen

> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de


-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-03-12 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 10:56 Chin You Wen (WMSC-HW)
2019-03-12 11:45 ` Roland Hieber [this message]
2019-03-13  8:09 ` Michael Olbrich
2019-03-14  9:34   ` Chin You Wen (WMSC-HW)
2019-03-14 12:02     ` Michael Olbrich
2019-03-15 10:23       ` Chin You Wen (WMSC-HW)

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=20190312114519.oydqai5vqajilymc@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=youwen@willowglen.asia \
    /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