From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] CROSS_NASM dependency in gst-libav
Date: Wed, 31 Jan 2018 17:14:11 +0100 [thread overview]
Message-ID: <CABDcavaVsawc0QvmYcZyewv9MWDDUVA_vz34kG-PZi92DHf_Dg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 440 bytes --]
Hi all,
I see that gst-libav.in selects CROSS_NASM.
Question: Is this a generic requirement? The documentation at [1] has a
section on "Unix-like platforms" and only mentions nasm for x86/AMD
hardware OS X. Am I correct in understanding that nasm is NOT required to
build for embedded Linux targets ?
[1]: https://libav.org/documentation/platform.html#Unix_002dlike
Best regards,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 789 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-01-31 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:14 Guillermo Rodriguez Garcia [this message]
2018-02-01 11:16 ` Michael Olbrich
2018-02-01 11:23 ` Guillermo Rodriguez Garcia
2018-02-02 16:20 ` Michael Olbrich
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=CABDcavaVsawc0QvmYcZyewv9MWDDUVA_vz34kG-PZi92DHf_Dg@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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