public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Dennis.Herbrich@hytera.de
To: crossgcc@sourceware.org
Subject: Packaging OSELAS.Toolchain: How to set DESTDIR properly
Date: Thu, 14 Jun 2012 16:26:00 -0000	[thread overview]
Message-ID: <OF597DF045.2D0FA800-ONC1257A1D.00593526-C1257A1D.005A1F22@hytera.de> (raw)

Greetings!

I would like to build the current OSELAS.Toolchain-2011.11.1 with 
ptxdist-2011.11.0 as recommended, and package it for further distribution 
as an Arch Linux package. Building and installing normally as documented 
is not a problem, but I fail to fully grasp what settings are necessary to 
install the files to an arbitrarily prefixed location, ie. 
/tmp/makepkg/pkg/opt instead of /opt, without messing up GCC's sysroot, 
search-dirs and friends.

Exporting PTX_AUTOBUILD_DESTDIR=/tmp/makepkg/pkg before running ptxdist go 
seemed to install the toolchain where I wanted, but unfortunately also 
added my prefix to the compiled in defaults of GCC. Is there a 
configuration option to do what I want? Something similar to "make 
DESTDIR=/prefix" that is correctly used throughout the whole toolchain 
build and install process automagically?

If not, I'd be thankful for pointers to what would need to be patched to 
make this happen. I really want a cleanly buildable package of this 
toolchain. ;)

Thank you for your consideration,
Dennis Herbrich

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2012-06-14 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 16:26 Dennis.Herbrich [this message]
2012-06-18 21:46 ` Yann E. MORIN
2012-06-19  7:16   ` Dennis.Herbrich

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=OF597DF045.2D0FA800-ONC1257A1D.00593526-C1257A1D.005A1F22@hytera.de \
    --to=dennis.herbrich@hytera.de \
    --cc=crossgcc@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).