mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Erwin Rol <mailinglists@erwinrol.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] mono
Date: Mon, 14 Nov 2011 11:59:45 +0100	[thread overview]
Message-ID: <20111114105945.GH28900@pengutronix.de> (raw)
In-Reply-To: <4EC0F3C5.9070403@erwinrol.com>

On Mon, Nov 14, 2011 at 11:56:05AM +0100, Erwin Rol wrote:
> Yeah target is fine. And yes they are needed on the host to build
> libraries for the target.
> 
> >If you have pre/post scripts, you should use $DESTDIR; we set this
> >variable while installing the opkg packages and it is not set on
> >runtime.
> 
> Don't really understand how this will solve the problem ? The *.in
> versions of the scripts look like this. So they are created at
> "automake-time"
> 
> less mcs.in
> #!/bin/sh
> exec @bindir@/mono $MONO_OPTIONS @mono_instdir@/2.0/mcs.exe
> -lib:@mono_instdir@/2.0 -lib:@mono_instdir@/3.5 "$@"
> 
> My idea was to add a $MONO_PREFIX environment variable to the
> scripts and set that in the target build .make file. On the target
> itself the MONO_PREFIX variable would be not set and the path would
> be /usr/bin as expected.

Hmm, I suppose you should discuss this with the Mono developers. I mean,
if they agree on an acceptable solution, we can patch it into ptxdist.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-11-14 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 10:16 Erwin Rol
2011-11-14 10:35 ` Robert Schwebel
2011-11-14 10:56   ` Erwin Rol
2011-11-14 10:59     ` Robert Schwebel [this message]
2011-11-14 11:04       ` Alexander Stein
2011-11-14 11:10         ` Erwin Rol

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=20111114105945.GH28900@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=mailinglists@erwinrol.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