On Fri, Mar 08, 2013 at 12:03:15AM +0800, Peter Maydell wrote:
> Earlier in this thread it's been stated that this often produces
> subtly broken blobs...
I think there have been some far reaching conclusions in this thread
based on incorrect premises.
SeaBIOS has had problems with mis-compilatio
> In general having blobs in our allegedly source tarball is pretty ugly.
> Either it's a
> source release or it isn't. We can do a release-of-blobs tarball too if we
> want,
> but it doesn't need to be in the source tarball and it doesn't need to be in
> git
> either IMHO.
I think it is very c
On Fri, Mar 08, 2013 at 12:03:15AM +0800, Peter Maydell wrote:
> On 7 March 2013 23:56, Gerd Hoffmann wrote:
> > Peter Maydell wrote:
> >> In general having blobs in our allegedly source tarball is pretty
> >> ugly. Either it's a source release or it isn't. We can do a
> >> release-of-blobs tarbal
On 7 March 2013 23:56, Gerd Hoffmann wrote:
> Peter Maydell wrote:
>> In general having blobs in our allegedly source tarball is pretty
>> ugly. Either it's a source release or it isn't. We can do a
>> release-of-blobs tarball too if we want, but it doesn't need
>> to be in the source tarball
>
>
Hi,
> In general having blobs in our allegedly source tarball is pretty
> ugly. Either it's a source release or it isn't. We can do a
> release-of-blobs tarball too if we want, but it doesn't need
> to be in the source tarball
This is easily doable, just an update to scripts/make-release to spe
On 7 March 2013 19:56, Gerd Hoffmann wrote:
>> We don't even ship any upstream blobs in the debian qemu _source_
>> package: we repack upstream qemu.tar.gz by removing these blobs.
>
> That's a bit over the top for my taste as the release tarballs include
> both source and blobs.
qemu-linaro's s
07.03.2013 15:56, Gerd Hoffmann wrote:
>> Just a note, or an "alternative opinion", so to say. In Debian, we have
>> a social contract which, among other things, ensures that the binaries
>> you, as a user, get, comes with source which you can modify on the
>> system you installed. This requires
Hi,
>> Would qemu consider using those blobs rather than different developers
>> using their distro toolchain to build up a random commit ID. I say
>> random only because often qemu releases ship with a non-release
>> seabios.
It happened (well, the snapshot thing). But that isn't our preferre
07.03.2013 10:12, Doug Goldstein wrote:
> On Wed, Mar 6, 2013 at 7:58 PM, Peter Stuge wrote:
>> Yeah, it is very common. Lots of distributions patch their
>> toolchains such that they don't compile firmware code correctly.
>>
>> Firmware isn't a common target, so I understand that it happens.
>>
On 7 March 2013 14:12, Doug Goldstein wrote:
> On Wed, Mar 6, 2013 at 7:58 PM, Peter Stuge wrote:
>> For coreboot we recommend to build a vanilla toolchain using known
>> good versions. We also have a script to do that. (The script is at
>> util/crossgcc/buildgcc in the coreboot repo.)
> Would q
On Wed, Mar 6, 2013 at 7:58 PM, Peter Stuge wrote:
> Laszlo Ersek wrote:
>> Going out on a limb, I suspect qemu commit 5f876756 instead.
> ..
>> I think the gcc version Anthony was using miscompiled SeaBIOS
>
> Yeah, it is very common. Lots of distributions patch their
> toolchains such that they
11 matches
Mail list logo
