From: Christopher Degawa <ccom@randomderp.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] duplicate symbol '_dec_init' in: fftools/ffmpeg_dec.o
Date: Sat, 16 Mar 2024 09:26:41 -0500
Message-ID: <CABDPGrxwM5QBNqA_EWPBtvxRRKq6+C7HJ2mjrf3GVUbn2r_96Q@mail.gmail.com> (raw)
In-Reply-To: <941BFC58-C890-4900-98E2-2EB53B4E05C1@me.com>
On Sat, Mar 16, 2024 at 09:08 Gnattu OC via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> If you are using Xcode >= 15 then you will need to add `-Wl,-ld_classic`
> to LDFLAGS. During configure you will also need to set
> `--host-ldflags='-Wl,-ld_classic’`.
>
> > On Mar 16, 2024, at 09:04, Helmut K. C. Tessarek <tessarek@evermeet.cx>
> wrote:
> >
> > Hello,
> >
> > It's me again - the dude who compiles ffmpeg for macOS... ;-)
> >
> > I haven't updated the referenced libbluray, but only compiled ffmpeg the
> way I always do. The last time was about 3 days ago and all was good.
> >
> > This is the git hash of ffmpeg I tried to compile: b47abd5737
> >
> > duplicate symbol '_dec_init' in:
> > fftools/ffmpeg_dec.o
> > /Users/Shared/ffmpeg/sw/lib/libbluray.a(libbluray_la-dec.o)
> > ld: 1 duplicate symbol for architecture x86_64
> > clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> >
> > The only code that changed was ffmpeg and libx265, thus I suspect it was
> a change to ffmpeg. I can't really do a git bisect, because this error only
> happens after ffmpeg is compiled at the linker stage, so that would take me
> forever....
> >
> > However, the dev who did a change related to this would probably know
> right away.
> >
> > 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.
> > */
> > _______________________________________________
> > 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".
>
> _______________________________________________
> 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".
Seems the conflict comes from
https://code.videolan.org/videolan/libbluray/-/blob/master/src/libbluray/disc/dec.c?ref_type=heads#L287
and
https://github.com/FFmpeg/FFmpeg/commit/c4de5778bceab3c15f1239f1f16816749a7fd3b6
Perhaps you could also try asking libbluray if they could use an internal
prefix. Otherwise you might need to do a rename of that function on
ffmpeg's side.
_______________________________________________
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:[~2024-03-16 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 1:04 Helmut K. C. Tessarek
2024-03-16 14:07 ` Gnattu OC via ffmpeg-devel
2024-03-16 14:26 ` Christopher Degawa [this message]
2024-03-16 20:58 ` James Almer
2024-03-17 17:26 ` Rémi Denis-Courmont
2024-03-17 17:29 ` Andreas Rheinhardt
2024-03-17 17:37 ` Rémi Denis-Courmont
2024-03-17 21:13 ` Timo Rothenpieler
2024-03-18 0:32 ` Rémi Denis-Courmont
2024-03-18 1:21 ` Timo Rothenpieler
2024-03-18 2:31 ` Rémi Denis-Courmont
2024-03-18 7:32 ` Martin Storsjö
2024-03-18 10:52 ` Andreas Rheinhardt
2024-03-16 21:09 ` Helmut K. C. Tessarek
2024-03-17 8:05 ` Gnattu OC via ffmpeg-devel
2024-03-17 12:10 ` Timo Rothenpieler
2024-03-17 19:45 ` Helmut K. C. Tessarek
2024-03-16 20:55 ` Helmut K. C. Tessarek
2024-03-17 21:19 ` Helmut K. C. Tessarek
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=CABDPGrxwM5QBNqA_EWPBtvxRRKq6+C7HJ2mjrf3GVUbn2r_96Q@mail.gmail.com \
--to=ccom@randomderp.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