From: Kacper Michajlow <kasper93@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] configure: don't force specific C++ standard library linking
Date: Fri, 8 Sep 2023 20:59:57 +0200
Message-ID: <CABPLASRv7vaQcD4VDbecKroTOeRkmV4zCYF2RA6x+V0UWaiokA@mail.gmail.com> (raw)
In-Reply-To: <CAK+ULv4SQPdqw7qxRKsay0ZFU3jYSH5CYnGzF6dZLzwKgeUakw@mail.gmail.com>
On Fri, 8 Sept 2023 at 20:46, Kieran Kunhya <kierank@obe.tv> wrote:
>
> On Fri, 8 Sept 2023 at 19:42, Kacper Michajlow <kasper93@gmail.com> wrote:
>
> > On Fri, 8 Sept 2023 at 00:11, Kieran Kunhya <kierank@obe.tv> wrote:
> > >
> > > On Thu, 7 Sept 2023 at 22:39, Kacper Michajlow <kasper93@gmail.com>
> > wrote:
> > >
> > > > On Thu, 7 Sept 2023 at 15:12, Derek Buitenhuis
> > > > <derek.buitenhuis@gmail.com> wrote:
> > > > >
> > > > > On 9/6/2023 6:31 PM, Kacper Michajlow wrote:
> > > > > > What would be a downside of preferring CXX always if it exists?
> > > > >
> > > > > FFmpeg runs in a multitude of environments with a multitude of
> > > > portability
> > > > > requirements. Needlessly linking a C++ runtime is not OK.
> > > >
> > > > This does not answer my question. Let me rephrase. Do we know the case
> > > > where using C++ compiler driver rather than C would degrade the
> > > > quality of the resulting build?
> > > >
> > >
> > > The machine that ffmpeg is being compiled on is not necessarily the one
> > > that ffmpeg is going to be run on.
> >
> > Not sure how this is relevant to the discussion?
> >
>
> > > > > What would be a downside of preferring CXX always if it exists?
>
> Because it forces a dependency on libstdc++ even if another machine does
> not have it.
On all "affected" platforms, configure already adds -Wl,--as-needed,
so the resulting library has exactly the same dependencies. Unless
something references symbols from stdlib, but then it would just not
link with clang anyway.
~ clang++ m.o -Wl,--as-needed && ldd a.out
linux-vdso.so.1 (0x00007ffeeb912000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f64050a7000)
/lib64/ld-linux-x86-64.so.2 (0x00007f64052ad000)
~ clang m.o -Wl,--as-needed && ldd a.out
linux-vdso.so.1 (0x00007ffe1fb36000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5e7a3c2000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5e7a5c8000)
- Kacper
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-09-08 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 23:26 Kacper Michajłow
2023-09-06 10:15 ` Timo Rothenpieler
2023-09-06 16:54 ` Kacper Michajlow
2023-09-06 17:09 ` Timo Rothenpieler
2023-09-06 17:31 ` Kacper Michajlow
2023-09-07 13:12 ` Derek Buitenhuis
2023-09-07 21:38 ` Kacper Michajlow
2023-09-07 22:10 ` Kieran Kunhya
2023-09-08 18:41 ` Kacper Michajlow
2023-09-08 18:46 ` Kieran Kunhya
2023-09-08 18:59 ` Kacper Michajlow [this message]
2023-09-07 23:34 ` Timo Rothenpieler via ffmpeg-devel
2023-09-08 18:55 ` Kacper Michajlow
2023-09-08 18:58 ` Timo Rothenpieler
2023-09-09 13:29 ` Rémi Denis-Courmont
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=CABPLASRv7vaQcD4VDbecKroTOeRkmV4zCYF2RA6x+V0UWaiokA@mail.gmail.com \
--to=kasper93@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git