mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: Jakov Simunic <jakovsimunic@live.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ISC DHCP 4.3.6-P1
Date: Fri, 27 Apr 2018 12:22:08 +0200	[thread overview]
Message-ID: <20180427102208.gh3shtb74hdkkj3g@pengutronix.de> (raw)
In-Reply-To: <VI1PR0201MB21104FB077FC66602AAC8EA5BC8E0@VI1PR0201MB2110.eurprd02.prod.outlook.com>

Hi,

On Thu, Apr 26, 2018 at 08:14:03AM +0000, Jakov Simunic wrote:
> Hello,
> 
> we are using ISC DHCP in our ptxdist project and I have the task to
> upgrade it from the currently used version 4.1-ESV-R10 to the newer
> 4.3.6-P1 version. Much has changed in the build of the ISC DHCP from
> the last used version in our project, and since we are cross compiling
> from our build server (x86_64) to the targets (one target is a 32 bit
> PowerPC architecture and the other is a 32 bit ARM target) we need the
> cross compilation to work properly. The build always fails due to the
> improper setting of the BUILD_CC and CC environment variables which
> are required to build a rule called gen in the
> dhcp-4.3.6-P1/bind/bind-9.9.11-P1/export/dns/Makefile (that rule
> builds some stuff using the host compiler set through the BUILD_CC
> environment variable), I have tried to set those variables through the
> ptxdist/rules/dhcp.make file (adding those environment variables to
> the DHCP_ENV variable), that doesn't work. Also I have tried to set
> them through the ptxdist/patches (tried to patch the
> dhcp-4.3.6-P1/Makefile.in and the dhcp-4.3.6-P1/bind/Makefile.in) the
> patches get applied and the Makefile prints out the correct compilers,
> but it still fails in the same gen rule with the same error saying
> that the BUILD_CC environment variable isn't set. Tried to cross
> compile it outside of ptxdist on an Debian machine and it finishes
> normally, so I think that something inside of ptxdist is causing the
> error.
> 
> Could you offer any help/advice/suggestions on this matter, any help
> would be greatly appreciated?

If there is no other way to make the Makefile take the cross compiler,
the normal way would be to patch that Makefile so it uses the supplied
*_CC environment variables by ptxdist. (If there is no such way, this
issue alone should be worth an issue in the ISC bug tracker, as it
hinders any sort of cross-compiling.)

But apparently isc-dhcp bundles a version of isc-bind, and only unpacks
it during the build from bind/bind.tar.gz.  So this problem cannot be
easily worked around by a patch in ptxdist, because we cannot patch
non-existing files.

I guess you either have to figure out how to get rid of the bind
dependency, or unpack bind.tar.gz in the dhcp.extract stage, and then
you can use the usual patch magic of ptxdist, which gets applied after
the extract stage.

 - Roland

-- 
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:[~2018-04-27 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  8:14 Jakov Simunic
2018-04-27 10:22 ` Roland Hieber [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=20180427102208.gh3shtb74hdkkj3g@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=jakovsimunic@live.com \
    --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