From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: "andrew@ncrmnt.org" <andrew@ncrmnt.org>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>,
John Collis <John.Collis@alliedtelesis.co.nz>
Subject: Re: crosstool-NG Debian packaging
Date: Wed, 10 Feb 2016 21:05:00 -0000 [thread overview]
Message-ID: <7fbc897bb92d4580bd32d5d1f95d1d83@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: <31521E2D-D70B-4989-B424-38E0B66D7E9F@gmail.com>
On 02/11/2016 09:53 AM, Bryan Hundven wrote:
> Chris,
>
>> On Feb 10, 2016, at 12:49 PM, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
>>
>> On 02/11/2016 09:41 AM, Bryan Hundven wrote:
>>> Chris,
>>>
>>>> On Feb 10, 2016, at 12:31 PM, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
>>>>
>>>> Hi Bryan, Andrew,
>>>>
>>>> I see that there is some movement on packaging crosstool-NG for Debian.
>>>> This is relevant to my interests and I have subscribed to your mailing
>>>> list :).
>>>>
>>>> Is there an open Debian bug for this? I've found a few older ones but
>>>> they all seem to have timed out due to lack of interest.
>>>>
>>>> I'm also interested in the possibility of generating debian packages for
>>>> the toolchains themselves.
>>>
>>> I have no interests in adding package manager support in crosstool-NG for produced toolchains.
>>> If you need such support, create a wrapper script that calls crosstool-ng and creates a package.
>>>
>>
>> Yes that was my intention. We'd need to slip in our kernel headers and
>> libc so it would be custom regardless.
>
> Well, when 1.23 releases, custom location support has been greatly improved.
>
> So really, I would just focus on the creation of the custom package ;)
>
Cool will do.
>>>> We're in the process of updating our cross toolchain(s) and being able
>>>> to distribute .deb files to our developers is quite attractive. Is
>>>> anyone looking at such a capability? If not any pointers?
>>>>
>>>> Thanks,
>>>> Chris Packham.
>>>>
>>>
>>> Cheers,
>>>
>>> -Bryan
>>>
>>
>
> Cheers,
>
> -Bryan
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2016-02-10 21:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:32 Chris Packham
2016-02-10 20:41 ` Bryan Hundven
2016-02-10 20:49 ` Chris Packham
2016-02-10 20:52 ` Bryan Hundven
2016-02-10 21:05 ` Chris Packham [this message]
2016-02-10 21:43 ` andrew
2016-02-23 3:55 ` Chris Packham
2016-02-23 4:37 ` Bryan Hundven
2016-02-23 4:40 ` Bryan Hundven
2016-02-23 21:15 ` Chris Packham
2016-02-23 13:05 ` Thomas Petazzoni
2016-02-23 15:41 ` Bryan Hundven
2016-02-23 21:26 ` Github tags (was Re: crosstool-NG Debian packaging) Chris Packham
2016-02-12 4:20 ` crosstool-NG Debian packaging Chris Packham
2016-02-12 19:49 ` Bryan Hundven
2016-02-14 19:42 ` Chris Packham
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=7fbc897bb92d4580bd32d5d1f95d1d83@svr-chch-ex1.atlnz.lc \
--to=chris.packham@alliedtelesis.co.nz \
--cc=John.Collis@alliedtelesis.co.nz \
--cc=andrew@ncrmnt.org \
--cc=bryanhundven@gmail.com \
--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).