Re: Bug#730833: u-boot: FTBFS on kfreebsd
On 18/02/2014 21:54, Vagrant Cascadian wrote:
> On Tue, Feb 18, 2014 at 09:35:09PM +0000, Robert Millan wrote:
>> On 18/02/2014 19:11, Vagrant Cascadian wrote:
>>> Looking for help from the *bsd porters on this... We haven't seen a
>>> successful build of u-boot on kfreebsd since mid-2012...
>>>
>>> The short of it is a bunch of header files that aren't present on Debian
>>> GNU/kFreeBSD are required for building u-boot-tools. Upstream u-boot has
>>> essentially copied a bunch of header files from linux sources. The current
>>> best patch we have is to copy *more* header files, but this seems like a bad
>>> idea... Droppping u-boot-tools on kfreebsd-* would be a regression from wheezy.
>>
>> Are you sure u-boot is supposed to build on anything other than Linux? The kind
>> of software package that embeds copies of Linux headers is not generally
>> intended to be portable...
>
> Well, u-boot-tools could technically be useable on any architecture. Is it
> actually useful? Quite possibly not.
>
> If the best thing is to drop non-linux architectures, I'd be fine with that.
> I don't want to drop architectures from the packaging without asking porters
> first.
I think if upstream doesn't consider it a bug to copy non-portable declarations from
Linux headers, it's probably reasonable to consider u-boot as Linux-specific software.
Attempting to fight this kind of trend is tends to be very costly, but ultimately it's
your call as maintainer to decide whether it's worth it.
We can provide assistance if necessary. In this case, my advice would be to figure out
why are those headers being copied in, since this seems to be the root of the problem.
--
Robert Millan
Reply to: