Re: svn update, then compilation fails (Reimar Döffinger)

"Rinaldi J. Montessi" <[email protected]>
Newsgroups gmane.comp.video.mplayer.user
Organization Red White and Blue
Message-ID <[email protected]>
On 2/24/21 4:00 AM, [email protected] wrote:
> -------
>
> Today's Topics:
>
>     1. svn update, then compilation fails (Antonio Olivares)
>     2. Re: svn update, then compilation fails (Reimar Döffinger)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 23 Feb 2021 19:21:37 +0000 (UTC)
> From: Antonio Olivares <[email protected]>
> ----------
> Dear mplayer users/developers,
>
> running fedora 33, I use mplayer compiled from source.
> I have run svn update and ran ./configure
> when running make, I get error message:
>
> /usr/bin/ld: ffmpeg/libavformat/movenc.o: warning: relocation against `ff_mp4_obj_type' in read-only section `.text'
<snip>
> [olivares@localhost mplayer]$
>
> How can I get it to work.  I want to update to latest.  I have updated ffmpeg to latest 4.3.2 version.
>
> Best Regards,
>
>
> Antonio
>
>
> ------------------------------
> /usr/bin/ld: warning: creating DT_TEXTREL in a PIE
> /usr/bin/ld: warning: creating DT_TEXTREL in a PIE
>
> Is this 32-bit x86?
> If so,  it sounds like your compiler has security features (PIC/PIE) enabled by default
> that we do not support for 32-bit x86 because the speed impact is too big.
> Though those might only be warnings.
>
>> /usr/bin/ld: ffmpeg/libavformat/mov.o: in function `mov_codec_id':
>> mov.c:(.text+0x54d): undefined reference to `ff_codec_movsubtitle_tags'
> No idea, but maybe do a “make distclean” first?

Exact same errors here.  Yes, make distclean done first.

This is an x86_64 running slackware-current with multilib.

Rinaldi

_______________________________________________
MPlayer-users mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.