From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Paul <paul_c@tuxcnc.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] debuild of xenomai failing: Directory nonexistent
Date: Mon, 03 Feb 2014 21:42:19 +0100 [thread overview]
Message-ID: <52EFFF2B.1080509@xenomai.org> (raw)
In-Reply-To: <201402022350.08460.paul_c@tuxcnc.org>
On 02/03/2014 12:50 AM, Paul wrote:
> On Friday 31 January 2014, Paul wrote:
>> On Friday 31 January 2014, Huub Van Niekerk wrote:
>>> Despite starting all over (tar jxf xenomai), downloading and
>>> patching again, debuild stops at exactly the same place. I still
>>> wonder why debuild on x86 (Ubuntu 10.04) worked great instantly and
>>> on armhf (Ubuntu 12.04) keeps ending in error. I just ran a test
>>> with standard "debuild -uc -us" on Ubuntu 12.04 x86 and it delivers
>>> the expected xenomai deb files without a problem. So why doesn't it
>>> do the same on armhf ?
>>
>> This is sounding more like a bug either in Ubuntu 12.04 or some
>> peculiarities with this particular armhf flavour rather than a
>> Xenomai issue.
>
> The reason dh_installdirs is not working for this particular build is
> because armhf is not listed as a supported architecture - This would
> prevent all architecture dependant packages from being built and just
> produce xenomai-kernel-source and xenomai-doc.
>
> Attached are two patches, the first should have been part of an earlier
> patch that included static devices in libxenomai1.
>
> The second patch adds armhf support to the list of binary packages
> generated.
>
> Need to rework debian/rules to give a cleaner split between arch
> dependant and common packages - Will work on this later in the week.
Merged, thanks.
--
Gilles.
next prev parent reply other threads:[~2014-02-03 20:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:36 [Xenomai] debuild of xenomai failing: Directory nonexistent Huub Van Niekerk
2014-01-29 19:05 ` Gilles Chanteperdrix
2014-01-29 20:02 ` Gilles Chanteperdrix
2014-01-30 7:31 ` Huub Van Niekerk
2014-01-30 8:39 ` Gilles Chanteperdrix
2014-01-30 9:05 ` Huub Van Niekerk
2014-01-30 9:24 ` Gilles Chanteperdrix
2014-01-30 9:41 ` Huub Van Niekerk
2014-01-30 10:52 ` Gilles Chanteperdrix
2014-01-30 12:07 ` Huub Van Niekerk
2014-01-30 12:53 ` Gilles Chanteperdrix
2014-01-30 13:23 ` Huub Van Niekerk
2014-01-30 16:45 ` Gilles Chanteperdrix
2014-01-30 19:12 ` Gilles Chanteperdrix
2014-01-31 6:58 ` Huub Van Niekerk
2014-01-31 9:27 ` Gilles Chanteperdrix
2014-01-30 12:07 ` Huub Van Niekerk
2014-01-30 12:12 ` Gilles Chanteperdrix
2014-01-30 16:24 ` Paul
2014-01-30 16:44 ` Gilles Chanteperdrix
2014-01-30 19:57 ` Paul
2014-01-30 20:30 ` Gilles Chanteperdrix
2014-01-31 7:00 ` Huub Van Niekerk
2014-01-31 9:30 ` Gilles Chanteperdrix
2014-01-31 9:37 ` Huub Van Niekerk
2014-01-31 9:18 ` Huub Van Niekerk
2014-01-31 9:39 ` Gilles Chanteperdrix
2014-01-31 14:12 ` Paul
2014-01-31 14:13 ` Gilles Chanteperdrix
2014-02-02 23:50 ` Paul
2014-02-03 20:42 ` Gilles Chanteperdrix [this message]
2014-01-31 12:22 ` Gilles Chanteperdrix
2014-01-31 14:08 ` Huub Van Niekerk
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=52EFFF2B.1080509@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=paul_c@tuxcnc.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.