public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexis Murzeau <amubtdx@outlook.fr>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: crosstool-ng packaging for Debian
Date: Thu, 13 Jul 2017 00:17:00 -0000	[thread overview]
Message-ID: <AM4P190MB0179DBDA3648C565B09EC64EDAAC0@AM4P190MB0179.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAEUG-6j6hLoyqT8MhZmyM=OPEe=vzda_Dd7mRw8_M-ErzzzNCQ@mail.gmail.com>

I resend this mail in text-only format as the first one got rejected.

(by the way, sorry for the possible duplicates)


Alexis Murzeau


-------- Forwarded Message --------
Subject: 	crosstool-ng packaging for Debian
Date: 	Thu, 13 Jul 2017 01:53:53 +0200
From: 	Alexis Murzeau <amubtdx@outlook.fr>
To: 	Chris Packham <Chris.Packham@alliedtelesis.co.nz>, 
721430@bugs.debian.org
CC: 	crossgcc@sourceware.org



Hi,

This week I worked on packaging crosstool-ng 1.23 for Debian using 
existing work.

I found that some dependencies are missing from the binary package so 
`ct-ng build` works correctly with minimal base system (like m4, wget).

I also added patches:
- 0001-Disable-MAKELEVEL-check.patch:
    An alternative to setting MAKELEVEL=0 inside debian/rules.
    This patch comments out the check of MAKELEVEL inside `Makefile.in`.

- 0002-Makefile.in-remove-recursive-part.patch:
    This patch fix the infinite recursion issue. I should probably share 
this into crosstool-ng and put the following text into the patch 
description :).
    The issue is that Debian dh run `make -n` which give `nrR` inside 
MAKEFLAGS and the `filter` function only matches whole words.
    Using `findstring` replaces every occurrences of the given text, 
making the assumption that no long options will contain `rR` or `Rr`.

- 0003-Backport-commit-Fix-debuild-warnings-errors.patch:
    This patch backports the commit [1] to fix lintian warning and errors.

I added installation of the bash completion script into 
/usr/share/bash-completion/completions (which is the new directory 
replacing /etc/bash_completion.d/).

I've added a watch file which use [4] and checks the gpg signature 
against `debian/upstream/signing-key.asc`.
The signing-key.asc file contains public keys of Alexey Neyman and Bryan 
Hundven (not sure if they are all the needed signatures).

I added a autopkgtest test to build a `arm-unknown-eabi` toolchain to 
check that the built package is working properly.

I put my package sources on github [2] with a travis configuration to:
- Build on travis a schroot of unstable (as travis use old ubuntu releases)
- Use this schroot to run sbuild inside which also run lintian and 
autopkgtest.
- Not that relevant but travis-ci also upload the built package to 
bintray when building a tag.

I use git-buildpackage to manage the source package.
My workflow is documented at `debian/README.source`.

Due to the length of the toolchain building and limitation of travis 
build max duration, I only test one toolchain build (arm-unknown-eabi).
FYI, Travis sbuild logs are available here [3].

I'm not sure about my medium/long term availability to maintain this 
package, but I hope what I have done can help to get crosstool-ng into 
Debian :)

[1] 
https://github.com/crosstool-ng/crosstool-ng/commit/1b4e784a0ba636646def1db5ca012fd54ee7a81c
[2] https://github.com/amurzeau/crosstool-ng-debian/
[3] https://travis-ci.org/amurzeau/crosstool-ng-debian/builds/252979392
[4] http://crosstool-ng.org/download/crosstool-ng/

Alexis Murzeau

       reply	other threads:[~2017-07-13  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEUG-6j6hLoyqT8MhZmyM=OPEe=vzda_Dd7mRw8_M-ErzzzNCQ@mail.gmail.com>
2017-07-13  0:17 ` Alexis Murzeau [this message]
2017-07-17 15:44   ` Geert Stappers
     [not found]     ` <AM4P190MB0179FF1C5F01A494986EB730DAA00@AM4P190MB0179.EURP190.PROD.OUTLOOK.COM>
2017-07-18 19:57       ` Bug#721430: " Geert Stappers
2017-07-24  0:32         ` Chris Packham
2017-07-24  0:43           ` 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=AM4P190MB0179DBDA3648C565B09EC64EDAAC0@AM4P190MB0179.EURP190.PROD.OUTLOOK.COM \
    --to=amubtdx@outlook.fr \
    --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).