Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	"Helmut K. C. Tessarek" <tessarek@evermeet.cx>
Subject: Re: [FFmpeg-devel] linker error
Date: Thu, 20 Oct 2022 11:00:01 +0300
Message-ID: <8B5294CB-E12A-4A2B-ADC0-43915D21AE07@remlab.net> (raw)
In-Reply-To: <7a770bdb-7ec0-e57b-c664-c1cb2a0e3776@evermeet.cx>

Le 20 octobre 2022 10:29:47 GMT+03:00, "Helmut K. C. Tessarek" <tessarek@evermeet.cx> a écrit :
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>On 2022-10-20 02:48, Nicolas George wrote:
>> Possibly. But between a library and a final program, the one who is at 
>> fault when a non-namespaced symbol conflicts is the library.
>
>In theory I agree with you. However, libass has been using the same
>non-static read_file function for many, many years.
>
>Cheers,
>  K. C.
>
>- -- 
>regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
>Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
>
>/*
>   Thou shalt not follow the NULL pointer for chaos and madness
>   await thee at its end.
>*/
>-----BEGIN PGP SIGNATURE-----
>
>iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmNQ+OsACgkQvgmFNJ1E
>3QAOLQ/9F8d7myiHryjRti5U2+29vx8ExZM79JLM8wuz8U2Ba+EcszHec5FNFFAL
>Fs7r9zqTy4CcOO6/mTmnZGXOrCNQDSnCD/Z7mDpTCGyPfjcJ+SVvwvugvazuduig
>7PQ7pAj1rOGzcaRvRrY5gvS5WP/g58uxZNtxNp6t2sGfHmdx9RCSz3rDgp01jDzj
>5KJSbP8JAz7/jQnlhRMP3ol3nf0AQpbdZKQ9FfBJLKpCEd4C7qLNI9wQ77c5f4F6
>uJiZKFcg8KY4IWTYVVggH7eLqTOeoFCwuCfvut0v5izBFFvY0JILHWqe8HofwHwq
>IcffmHA5lI/18w9zG0jgzToA90WiCrAYQbii0RHfm0yqXvpyDlqOvugfN08fMqUd
>R9j7s4FR3GZy6DhLvSeI+z9/1sk8XbtKGEZ06riD22NaXIdZkb40hcCeKoUH1iqK
>M8ADf90Zt8iVmw56uStVW33j30TsE8CHlTORo1Fjzl7pViyqwuue31Ty5ipHFY7l
>JchFRTRIpvPS9rE62LWnE9sDORL4oYZKfPDjgTR7byc8OL2q1Jh/S5wFhW23g+g7
>1yV2/1KIIHtB315sRm9Tk4nLJxsmlGjKC/TIt0l/QNyXIeWC/dRnwQoRqnTVaIk1
>NUtXLIjAZX/xDyyd0nIX4Spx3lIWU6+9u9WngIsXLzObYhOv82g=
>=JFAH
>-----END PGP SIGNATURE-----
>_______________________________________________
>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".
>

Hi,

However long libass has been doing this, it is wrong. If anything you are lucky that your setup detects the bug early on, during the build.

In other setups, duplicate symbols won't cause a build time errors. This bug will cause a program symbol to be overridden silently and trigger really weird and hard to debug side effects.

AFAICT, the question is not how long libass has been doing this. The question is why couldn't you fix your libass instance, and would you need to put a kludge into FFmpeg.
_______________________________________________
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".

      reply	other threads:[~2022-10-20  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  4:33 Helmut K. C. Tessarek
2022-10-20  6:48 ` Nicolas George
2022-10-20  7:01   ` Andreas Rheinhardt
2022-10-20  7:29   ` Helmut K. C. Tessarek
2022-10-20  8:00     ` Rémi Denis-Courmont [this message]

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=8B5294CB-E12A-4A2B-ADC0-43915D21AE07@remlab.net \
    --to=remi@remlab.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=tessarek@evermeet.cx \
    /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