From: <jon.bird@gd-ms.uk>
To: ptxdist@pengutronix.de
Subject: [ptxdist] dependencies not working in ptxdist-2017.01.0
Date: Mon, 27 Feb 2017 09:42:12 +0000 [thread overview]
Message-ID: <94D4A88F8AC34646A5288D11318F5D5B0D9E5960@GDUKADH841.uk1.r-org.net> (raw)
Hi,
I'm attempting to perform an update from a project based around ptxdist-2012.12.1 to the latest (2017.01.0) and am encountering a problem with package dependencies.
In essence I've performed 'ptxdist migrate' with the new version, worked through the questions then:
ptxdist clean
ptxdist go
One of the first packages to build is 'audit', which I created and has the following:
cat rules/audit.in
## SECTION=shell_and_console
config AUDIT
tristate
select LIBCAP_NG
select OPENLDAP
prompt "audit"
The compilation phase fails as follows:
In file included from zos-remote-log.h:27:0,
from zos-remote-config.c:35:
zos-remote-ldap.h:27:18: fatal error: lber.h: No such file or directory
#include <lber.h>
lber.h is from OpenLDAP, when I check the logfile, this package has not been built - neither has libcap-ng.
Executing the following:
grep audit platform-i586/state/ptx_dgen_deps.post
$(STATEDIR)/audit.get: | $(AUDIT_SOURCES)
$(foreach src,$(AUDIT_SOURCES),$(eval $(STATEDIR)/audit.get:$(STATEDIR)/audit.$(notdir $(src)).stamp))
$(STATEDIR)/audit.extract: $(STATEDIR)/audit.get
$(STATEDIR)/audit.extract.post: $(STATEDIR)/audit.extract
$(STATEDIR)/audit.prepare: $(STATEDIR)/audit.extract.post
$(STATEDIR)/audit.tags: $(STATEDIR)/audit.prepare
$(STATEDIR)/audit.compile: $(STATEDIR)/audit.prepare
$(STATEDIR)/audit.install: $(STATEDIR)/audit.compile
$(STATEDIR)/audit.install.pack: $(STATEDIR)/audit.install
$(STATEDIR)/audit.install.post: $(STATEDIR)/audit.install.pack
$(STATEDIR)/audit.install.post: $(STATEDIR)/audit.install.unpack
$(STATEDIR)/audit.targetinstall: $(STATEDIR)/audit.install.post
$(STATEDIR)/audit.targetinstall.post: $(STATEDIR)/audit.targetinstall
$(STATEDIR)/audit.report: $(STATEDIR)/audit.extract
$(STATEDIR)/audit.release: $(STATEDIR)/audit.extract
$(STATEDIR)/audit.extract.post: $(STATEDIR)/autogen-tools
$(STATEDIR)/audit.extract: $(STATEDIR)/host-lndir.install.post
$(STATEDIR)/audit.extract.post: $(STATEDIR)/base.install
$(STATEDIR)/audit.install.unpack: $(STATEDIR)/base.install
Shows no mention of OpenLDAP, by contrast the same command with the project built under 2012:
$(STATEDIR)/audit.get: $(AUDIT_SOURCE)
$(STATEDIR)/audit.extract: $(STATEDIR)/audit.get
$(STATEDIR)/audit.extract.post: $(STATEDIR)/audit.extract
$(STATEDIR)/audit.prepare: $(STATEDIR)/audit.extract.post
$(STATEDIR)/audit.tags: $(STATEDIR)/audit.prepare
$(STATEDIR)/audit.compile: $(STATEDIR)/audit.prepare
$(STATEDIR)/audit.install: $(STATEDIR)/audit.compile
$(STATEDIR)/audit.install.pack: $(STATEDIR)/audit.install
$(STATEDIR)/audit.install.post: $(STATEDIR)/audit.install.pack
$(STATEDIR)/audit.install.post: $(STATEDIR)/audit.install.unpack
$(STATEDIR)/audit.targetinstall: $(STATEDIR)/audit.install.post
$(STATEDIR)/audit.targetinstall.post: $(STATEDIR)/audit.targetinstall
$(STATEDIR)/audit.extract.post: $(STATEDIR)/autogen-tools
$(STATEDIR)/audit.extract: $(STATEDIR)/host-lndir.install.post
$(STATEDIR)/audit.extract.post: $(STATEDIR)/libcap-ng.install.post
$(STATEDIR)/audit.install.unpack: $(STATEDIR)/libcap-ng.install.post
$(STATEDIR)/audit.extract.post: $(STATEDIR)/openldap.install.post
$(STATEDIR)/audit.install.unpack: $(STATEDIR)/openldap.install.post
$(STATEDIR)/audit.targetinstall: $(STATEDIR)/libcap-ng.targetinstall
$(STATEDIR)/audit.targetinstall: $(STATEDIR)/openldap.targetinstall
$(STATEDIR)/audit.extract.post: $(STATEDIR)/base.install
$(STATEDIR)/audit.install.unpack: $(STATEDIR)/base.install
Shows the dependencies correctly.
This isn't just a one off problem though, if I manually build the dependencies, the audit package will build ok but then fails building the x-org font components.
I'm guessing that I'm missing something from the upgrade process but not entirely sure what.
Thanks,
Jon.
--
Jon Bird, CEng MBCS
Software Engineer
Electronic Systems
General Dynamics United Kingdom Ltd.
Castleham Road, St Leonards on Sea, East Sussex, TN38 9NJ
Telephone: +441424798278
Email: jon.bird@gd-ms.uk
Website: www.generaldynamics.uk.com
------------------------------------------------------------------------------
This email and any files attached are intended for the addressee and may contain information of a confidential nature. If you are not the intended recipient, be aware that this email was sent to you in error and you should not disclose, distribute, print, copy or make other use of this email or its attachments. Such actions, in fact, may be unlawful. In compliance with the various Regulations and Acts, General Dynamics United Kingdom Limited reserves the right to monitor (and examine for viruses) all emails and email attachments, both inbound and outbound. Email communications and their attachments may not be secure or error- or virus-free and the company does not accept liability or responsibility for such matters or the consequences thereof. General Dynamics United Kingdom Limited, Registered Office: 21 Holborn Viaduct, London EC1A 2DY. Registered in England and Wales No: 1911653.
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2017-02-27 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 9:42 jon.bird [this message]
2017-03-01 11:31 ` jon.bird
2017-03-08 9:46 ` Michael Olbrich
2017-03-09 14:15 ` jon.bird
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=94D4A88F8AC34646A5288D11318F5D5B0D9E5960@GDUKADH841.uk1.r-org.net \
--to=jon.bird@gd-ms.uk \
--cc=ptxdist@pengutronix.de \
/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