Mark H Weaver skribis:
> I wrote:
>
>> I restarted [the yasm build] again. Maybe it will work on the third
>> try.
>
> Indeed, the it worked on the third try, and the 'gdm' build on x86_64
> worked on the second try. I'm restarting all dependency failures now.
Weird. Thanks
I wrote:
> I restarted [the yasm build] again. Maybe it will work on the third
> try.
Indeed, the it worked on the third try, and the 'gdm' build on x86_64
worked on the second try. I'm restarting all dependency failures now.
Mark
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> yasm was apparently broken on i686 on the 'python-build-system' branch,
>> which was then subsequently merged into master. As a result, many
>> important package are dependency-failures on i686,
Mark H Weaver skribis:
> yasm was apparently broken on i686 on the 'python-build-system' branch,
> which was then subsequently merged into master. As a result, many
> important package are dependency-failures on i686, including all
> gstreamer plugins, and thus all media
Am 01.12.2016 um 11:06 schrieb Mark H Weaver:
> yasm was apparently broken on i686 on the 'python-build-system' branch,
This error is not related to the python build system - until you proof
me wrong.
I've spend some time now for seeking the error (see below), until i
discovered that yasm is nor
Am 01.12.2016 um 11:06 schrieb Mark H Weaver:
> yasm was apparently broken on i686 on the 'python-build-system' branch,
Can you please send me the ./test-suite.log. Given only the information
in the build log it is very hard to find the reason.
--
Regards
Hartmut Goebel
| Hartmut Goebel
Hi,
yasm was apparently broken on i686 on the 'python-build-system' branch,
which was then subsequently merged into master. As a result, many
important package are dependency-failures on i686, including all
gstreamer plugins, and thus all media players and web browsers.
This branch should not