After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 787587 - Add support for e2k architecture
Add support for e2k architecture
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.12.2
Other Linux
: Normal enhancement
: 1.13.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
http://altlinux.org/ports/e2k
Depends on:
Blocks:
 
 
Reported: 2017-09-12 14:15 UTC by Michael Shigorin
Modified: 2017-09-12 18:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gstreamer-1.12.2-alt-e2k.patch (1.60 KB, patch)
2017-09-12 14:15 UTC, Michael Shigorin
none Details | Review
the same as a git commit (1.83 KB, patch)
2017-09-12 15:32 UTC, Michael Shigorin
committed Details | Review

Description Michael Shigorin 2017-09-12 14:15:45 UTC
Created attachment 359637 [details] [review]
gstreamer-1.12.2-alt-e2k.patch

The attached patch makes it possible to build gstreamer 1.12.2 on e2k architecture; there's another issue with the current lcc (1.21.x) that gets worked around with "export LIBS=-lcxa" but it's to be fixed there.
Comment 1 Nicolas Dufresne (ndufresne) 2017-09-12 15:21:07 UTC
Patches should first be submitted against current git master and then backported. Please, provide a patch against master first.
Comment 2 Nicolas Dufresne (ndufresne) 2017-09-12 15:22:23 UTC
Also, patches should be in git-format form. For this. checkout the git repository, make your modification and commit them. The run "git format-pacth -1) and attach the resulting file to this bug.
Comment 3 Michael Shigorin 2017-09-12 15:32:07 UTC
Created attachment 359642 [details] [review]
the same as a git commit

(In reply to Nicolas Dufresne (stormer) from comment #1)
> Patches should first be submitted against current git master and then
> backported. Please, provide a patch against master first.
Thanks for replying but if you actually bothered applying it you'd find out
that there's not even fuzz, architecture lists aren't that agile usually. :]

(In reply to Nicolas Dufresne (stormer) from comment #2)
> Also, patches should be in git-format form.
Rather as a git commit, that is; no problem.

> "git format-pacth -1)
Get some rest, mate!
Comment 4 Nicolas Dufresne (ndufresne) 2017-09-12 18:01:16 UTC
Review of attachment 359642 [details] [review]:

Don't be so frustrated, it's the same rule for everyone, regardless if you patch is trivial or not.
Comment 5 Nicolas Dufresne (ndufresne) 2017-09-12 18:03:09 UTC
In master as 9cd8fae44da4b238fb0c26350c1efb99f31cf913