From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] CROSS_NASM dependency in gst-libav
Date: Thu, 1 Feb 2018 12:23:47 +0100 [thread overview]
Message-ID: <CABDcavY6Csba4FiJeYijP2DmzXTH9T-W9ykLQ-gRHfn0=iUUoA@mail.gmail.com> (raw)
In-Reply-To: <20180201111637.2hqitf46heqdqgtx@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]
Hi Michael,
2018-02-01 12:16 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> Hi,
>
> On Wed, Jan 31, 2018 at 05:14:11PM +0100, Guillermo Rodriguez Garcia wrote:
> > 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 ?
>
> It's needed for any x86 hardware (both 32 and 64 bit). It has nothing to do
> with OS X.
>
I see. From the documentation (
https://libav.org/documentation/platform.html#Unix_002dlike) I was under
the impression that GNU assembler was used on most Unix-like platforms.
> It's currently not possible to specify this dependency only for x86 and
> compared to gst-libav the cross-nasm packages is very small, so I never
> bothered to create some workaround for this.
>
OK, thank you for the information, this is helpful.
Best regards,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 1967 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-02-01 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:14 Guillermo Rodriguez Garcia
2018-02-01 11:16 ` Michael Olbrich
2018-02-01 11:23 ` Guillermo Rodriguez Garcia [this message]
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='CABDcavY6Csba4FiJeYijP2DmzXTH9T-W9ykLQ-gRHfn0=iUUoA@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