Re: [SOLVED] multimedia/x264 build failure, linker error
On Monday 24 November 2014 23:33:44 Albert Shih wrote: > Le 24/11/2014 à 17:02:35+, Dave a écrit > > Hi, > > > Sorry but I got the same issue. But I'm not sure I understand your answer. > > > pkg delete x264 lists the installed dependances > > So you deinstall all package depends on x264-0.136.2358_4 ? Sorry, for not getting back sooner. Real life intervened. I used pkg delete simply to confirm the list of installed dependencies on x264 > > make deinstall in multimedia/x264 > > why you need that ? If you use > > pkg delete x264-0.136.2358_4 Because saying "Yes" to that would deinstall the dependencies too, which I didn't want to do. > > > make install in mulimedia/libx264 > > > > make deinstall reinstall clean in the dependant ports, eg mencoder, > > mplayer, ffmpeg, gstreamer-plugins-x264 > > and those ports don't take automatically the « new » multimedia/libx264 ? Maybe. I rebuilt them to be sure they took the correct dependencies. Anyway, explanations of my workaround aside I see the UPDATING file has the correct information now :-) > Thanks. > > Regards. > > JAS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On Tue, 25 Nov 2014, Christian Weisgerber wrote: On 2014-11-25, Andrew Berg wrote: > As I have stated already in this thread, I am trying to get an UPDATING entry > committed: > > x264 was split into the application and its library. If an application > that uses libx264 is updated before x264 itself, multimedia/libx264 will > conflict with the old x264 package. > > Delete the existing x264: > # pkg delete x264 You can't. This will also require deleting all installed ports that depend on x264... It was pointed out to me a couple of days ago that 'pkg delete -f' will not delete dependencies. I have only tried it with -n so far. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On 2014-11-25, Andrew Berg wrote: > As I have stated already in this thread, I am trying to get an UPDATING entry > committed: > > x264 was split into the application and its library. If an application > that uses libx264 is updated before x264 itself, multimedia/libx264 will > conflict with the old x264 package. > > Delete the existing x264: > # pkg delete x264 You can't. This will also require deleting all installed ports that depend on x264... > And then install the updated x264 and/or upgrade the other applications that > depend on libx264. ... and then reinstall all the other applications that depend on libx264. -- Christian "naddy" Weisgerber na...@mips.inka.de ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On 2014.11.25 08:56, Gary Palmer wrote: > On Tue, Nov 25, 2014 at 08:35:12AM -0600, Andrew Berg wrote: >> On 2014.11.25 08:26, Gary Palmer wrote: >> > Since I assume most of the packages that depend on the old >> > x264-0.136.2358_4 >> > depend on the library rather than the CLI command, is there any harm in >> > doing >> > >> > portmaster -o multimedia/libx264 x264-0.136.2358_4 >> > >> > instead? That way the dependancies are kept (mostly) correct >> Don't do that. The dependency change has been properly handled, and those >> ports >> know to use multimedia/libx264. > > If you followed the instructions in the mail I replied to, the installed > packages are left with a dependency on x264 and not libx264. > > The real problem is that the few times I tried to use automated update > methods ran into problems because x264 was already installed and libx264 > couldn't be installed because they conflicted. Nothing seems to be > in UPDATING or MOVED so the upgrades break. There needs to be a better > way of handling these cases. As I have stated already in this thread, I am trying to get an UPDATING entry committed: x264 was split into the application and its library. If an application that uses libx264 is updated before x264 itself, multimedia/libx264 will conflict with the old x264 package. Delete the existing x264: # pkg delete x264 And then install the updated x264 and/or upgrade the other applications that depend on libx264. This is my fault for not testing upgrades via ports when creating the patch. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On Tue, Nov 25, 2014 at 08:35:12AM -0600, Andrew Berg wrote: > On 2014.11.25 08:26, Gary Palmer wrote: > > Since I assume most of the packages that depend on the old x264-0.136.2358_4 > > depend on the library rather than the CLI command, is there any harm in > > doing > > > > portmaster -o multimedia/libx264 x264-0.136.2358_4 > > > > instead? That way the dependancies are kept (mostly) correct > Don't do that. The dependency change has been properly handled, and those > ports > know to use multimedia/libx264. If you followed the instructions in the mail I replied to, the installed packages are left with a dependency on x264 and not libx264. The real problem is that the few times I tried to use automated update methods ran into problems because x264 was already installed and libx264 couldn't be installed because they conflicted. Nothing seems to be in UPDATING or MOVED so the upgrades break. There needs to be a better way of handling these cases. Regards, Gary ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On Mon, Nov 24, 2014 at 07:22:50PM -0800, Kevin Oberman wrote: > On Mon, Nov 24, 2014 at 2:33 PM, Albert Shih wrote: > > > Le 24/11/2014 ?? 17:02:35+, Dave a ??crit > > > > Hi, > > > > > > Sorry but I got the same issue. But I'm not sure I understand your answer. > > > > > > > > pkg delete x264 lists the installed dependances > > > > So you deinstall all package depends on x264-0.136.2358_4 ? > > > > Better to do: > pkg delete -f x264-0.136.2358_4 > portmaster multimedia/libx264 multimedia/x264 > > This assumes that you use portmaster. You can use portupgrade or the basic > 'make' commands. Since I assume most of the packages that depend on the old x264-0.136.2358_4 depend on the library rather than the CLI command, is there any harm in doing portmaster -o multimedia/libx264 x264-0.136.2358_4 instead? That way the dependancies are kept (mostly) correct Thanks, Gary ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
On Mon, Nov 24, 2014 at 2:33 PM, Albert Shih wrote: > Le 24/11/2014 à 17:02:35+, Dave a écrit > > Hi, > > > Sorry but I got the same issue. But I'm not sure I understand your answer. > > > > > pkg delete x264 lists the installed dependances > > So you deinstall all package depends on x264-0.136.2358_4 ? > > Better to do: pkg delete -f x264-0.136.2358_4 portmaster multimedia/libx264 multimedia/x264 This assumes that you use portmaster. You can use portupgrade or the basic 'make' commands. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
Le 24/11/2014 à 17:02:35+, Dave a écrit Hi, Sorry but I got the same issue. But I'm not sure I understand your answer. > > pkg delete x264 lists the installed dependances So you deinstall all package depends on x264-0.136.2358_4 ? > make deinstall in multimedia/x264 why you need that ? If you use pkg delete x264-0.136.2358_4 > > make install in mulimedia/libx264 > > make deinstall reinstall clean in the dependant ports, eg mencoder, mplayer, > ffmpeg, gstreamer-plugins-x264 and those ports don't take automatically the « new » multimedia/libx264 ? Thanks. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: lun 24 nov 2014 23:31:40 CET ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [SOLVED] multimedia/x264 build failure, linker error
It appears I may have missed an announcement somewhere. pkg delete x264 lists the installed dependances make deinstall in multimedia/x264 make install in mulimedia/libx264 make deinstall reinstall clean in the dependant ports, eg mencoder, mplayer, ffmpeg, gstreamer-plugins-x264 So, is multimedia/x264 deprecated now in favour of multimedia/libx264? There's nothing in /usr/ports/UPDATING On Saturday 22 November 2014 21:18:50 Dave wrote: > Sorry, forgot to mention, did a portsnap fetch update first and uname -a > gives > > Box 1 > FreeBSD amd.asgard.uk 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #0: Mon Nov 3 > 22:38:58 UTC 2014 root@amd64- > builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Box 2 > FreeBSD webmaker.asgard.uk 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #0: Mon Nov > 3 22:02:57 UTC 2014 root@amd64- > builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 > > On Saturday 22 November 2014 20:42:55 Dave wrote: > > portupgrade -c x264 > > [Reading data from pkg(8) ... - 1031 packages found - done] > > [Gathering depends for multimedia/x264 > > . done] > > ---> Upgrading 'x264-0.136.2358_4' to 'x264-0.142.2455' (multimedia/x264) > > ---> Building '/usr/ports/multimedia/x264' > > ===> Cleaning for x264-0.142.2455 > > ===> License GPLv2 accepted by the user > > ===> Found saved configuration for x264-0.142.2455 > > ===> x264-0.142.2455 depends on file: /usr/local/sbin/pkg - found > > ===> Fetching all distfiles required by x264-0.142.2455 for building > > ===> Extracting for x264-0.142.2455 > > => SHA256 Checksum OK for x264/x264-snapshot-20140827-2245-stable.tar.bz2. > > ===> Patching for x264-0.142.2455 > > ===> Applying FreeBSD patches for x264-0.142.2455 > > ===> x264-0.142.2455 depends on package: yasm>=0.6.0 - found > > ===> x264-0.142.2455 depends on file: /usr/local/bin/bash - found > > ===> x264-0.142.2455 depends on executable: gmake - found > > ===> x264-0.142.2455 depends on executable: pkgconf - found > > ===> x264-0.142.2455 depends on shared library: libx264.so - found > > (/usr/local/lib/libx264.so.136) > > ===> x264-0.142.2455 depends on shared library: libgpac.so - found > > (/usr/local/lib/libgpac.so.2.0.0) > > ===> Configuring for x264-0.142.2455 > > platform: X86_64 > > system:FREEBSD > > cli: yes > > libx264: system > > shared:no > > static:no > > asm: yes > > interlaced:yes > > avs: no > > lavf: no > > ffms: no > > mp4: gpac > > gpl: yes > > thread:posix > > opencl:no > > filters: crop select_every > > debug: no > > gprof: no > > strip: no > > PIC: no > > bit depth: 8 > > chroma format: all > > > > You can run 'make' or 'make fprofiled' now. > > ===> Building for x264-0.142.2455 > > dependency file generation... > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o x264.o x264.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o input/input.o > > input/input.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o > > input/timecode.o input/timecode.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o input/raw.o > > input/raw.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o input/y4m.o > > input/y4m.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o output/raw.o > > output/raw.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o > > output/matroska.o output/matroska.c > > cc -Wshadow -O3 -ffast-math -m64 -O2 -pipe -fstack-protector -fno-strict- > > aliasing -Wall -I. -I. -I/usr/local/include -std=gnu99 -mpreferred-stack- > > boundary=5 -fomit-frame-pointer -fno-tree-vectorize -c -o > > output/matroska_ebml.o output/matroska_ebml.c > > cc -Ws
