Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] linker error
Date: Thu, 20 Oct 2022 08:48:54 +0200
Message-ID: <Y1DvVsVb6IOH4Qhn@phare.normalesup.org> (raw)
In-Reply-To: <89f9a4ea-6752-5230-7bc9-127924ae3166@evermeet.cx>

Helmut K. C. Tessarek (12022-10-20):
> I compile the static ffmpeg binaries for macOS and I have noticed just now
> the following error:
> 
> duplicate symbol '_read_file' in:
>     fftools/ffmpeg_opt.o
>     /Users/Shared/ffmpeg/sw/lib/libass.a(ass.o)
> ld: 1 duplicate symbol for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see invocation
> )
> make: *** [ffmpeg_g] Error 1
> 
> I believe it has something to do with commit
> 18d6c07267994398f99b2241f577f8e7118af099
> fftools/ffmpeg_opt: move opening output files into a new file

Possibly. But between a library and a final program, the one who is at
fault when a non-namespaced symbol conflicts is the library.

So please report this to libass before considering a mitigation in
FFmpeg.

Regards,

-- 
  Nicolas George
_______________________________________________
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  6:49 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 [this message]
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

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=Y1DvVsVb6IOH4Qhn@phare.normalesup.org \
    --to=george@nsup.org \
    --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