public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Dennis.Herbrich@hytera.de
To: yann.morin.1998@free.fr
Cc: crossgcc@sourceware.org
Subject: Re: Packaging OSELAS.Toolchain: How to set DESTDIR properly
Date: Tue, 19 Jun 2012 07:16:00 -0000	[thread overview]
Message-ID: <OFB40C6287.AF365C51-ONC1257A22.0026EF9A-C1257A22.0027C03A@hytera.de> (raw)
In-Reply-To: <201206182345.59246.yann.morin.1998@free.fr>

"Yann E. MORIN" <yann.morin.1998@free.fr> wrote on 18.06.2012 23:45:59:

> I guess you'd be better answered on the appropriate mailing list for 
either
> PTXdist and/or OSELAS.Toolchain.

Thank you for your suggestion, I'll go bother the ptxdist-mailinglist 
instead.

> This list is about generic questions about building gcc-based cross-
> toolchains and, incidentally, about crosstool-NG.

To be perfectly honest, I wasn't sure this was the right mailing list 
myself,
but http://www.pengutronix.de/oselas/toolchain/index_en.html
explicitly referred me to here:

| This project has no own mailing list. Please use the crossgcc mailing 
list for
| all OSELAS.Toolchain() related questions, which has historically been a 
major
| resource for community discussion about cross toolchain building. 

If this wording is inaccurate and causing a bothersome influx of off-topic 
mails
to this list, someone may want to ask Pengutronics to reword this 
paragraph.

However, I'll carry this ptxdist issue of mine elsewhere, and come back if
there's an actual cross-related issue of interest. Thank you for your 
time!

Best regards,
  Dennis

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

      reply	other threads:[~2012-06-19  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 16:26 Dennis.Herbrich
2012-06-18 21:46 ` Yann E. MORIN
2012-06-19  7:16   ` Dennis.Herbrich [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=OFB40C6287.AF365C51-ONC1257A22.0026EF9A-C1257A22.0027C03A@hytera.de \
    --to=dennis.herbrich@hytera.de \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@free.fr \
    /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).