Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [PATCH v2] p7zip: New package
Date: Tue, 31 May 2016 23:56:51 +0200	[thread overview]
Message-ID: <574E08A3.3070204@dawncrow.de> (raw)
In-Reply-To: <20160530152042.5acb6bb0@free-electrons.com>

Am 30.05.2016 um 15:20 schrieb Thomas Petazzoni:
> Hello,
> 
> On Sun, 29 May 2016 19:22:50 +0200, Andr? Hentschel wrote:
> 
>>>> +config BR2_PACKAGE_P7ZIP
>>>> +	bool "p7zip"
>>>> +	depends on BR2_INSTALL_LIBSTDCPP
>>>> +	depends on BR2_i386 || BR2_x86_64 || \
>>>> +		BR2_aarch64 || BR2_arm || BR2_armeb  
>>>
>>> Please explain why this is limited to those architectures.
>>>
>>> You can put it in the commit log, or you may add a terse comment just
>>> above the depends-on line. If the explanations is not straightforward,
>>> prefer the commit log.
>>>
>>> (Yes, I read the previous reply that it was broken on NIOSII. Limiting
>>> to a small set of architectures wihtout an explanation is not enough.)
>>>
>>> Thanks! :-)  
>>
>> Can I start with a small set of archs until it is tested on more?
>> (with a comment then anyway of course)
> 
> I will disagree with Yann here. We typically do not limit the
> architectures based simply on what has been tested or not.
> 
> A dependency on specific architectures should only be added if the
> package is either 1/ contains some architecture-specific code or 2/ is
> known to not build/work properly on some architectures.
> 
> In any case,  the fact that you could only test on i386/AArch64/ARM is
> not a proper reason to restrict the package to those architectures only.

I simply used my autobuild machine now to test on almost all archs, bfin is the only troublemaker.

> Building p7zip for blackfin using
> 
> http://autobuild.buildroot.net/toolchains/configs/bfin-uclinux.config
> 
> as defconfig fails with
> 
> ../../../../CPP/myWindows/mySplitCommandLine.cpp:99:8: error: #error ENDIANNESS
> 
> Regards, Bernd

I tried it, the compiler doesn't expose ENDIANess defines... reason unknown...

  reply	other threads:[~2016-05-31 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 16:28 [Buildroot] [PATCH] [PATCH v2] p7zip: New package André Hentschel
2016-05-29 17:14 ` Yann E. MORIN
2016-05-29 17:22   ` André Hentschel
2016-05-29 17:29     ` Yann E. MORIN
2016-05-30 13:20     ` Thomas Petazzoni
2016-05-31 21:56       ` André Hentschel [this message]
2016-05-29 17:44 ` Bernd Kuhls

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=574E08A3.3070204@dawncrow.de \
    --to=nerv@dawncrow.de \
    --cc=buildroot@busybox.net \
    /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