portsdb -U-Error
checking out ports with: cd /usr/ports; svn update --accept theirs-full portsdb -U leads to following error (see on FreeBSD-CURRENT, FreeBSD-10beta4, FreeBSD-9, FreeBSD-8): Updating the ports index ... Generating INDEX.tmp - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- [...] --- describe.vietnamese --- --- describe.www --- make[5]: /usr/ports/www/links/Makefile line 5: Need an operator make[5]: /usr/ports/www/links/Makefile line 7: Need an operator make[5]: /usr/ports/www/links/Makefile line 12: Need an operator make[5]: /usr/ports/www/links/Makefile line 42: Need an operator make[5]: /usr/ports/www/links/Makefile line 44: Need an operator make[5]: /usr/ports/www/links/Makefile line 48: Need an operator make[5]: Fatal errors encountered -- cannot continue=== www/links failed *** [describe.www] Error code 1 make[2]: stopped in /usr/ports 1 error make[2]: stopped in /usr/ports [...] *** Error code 1 Stop. make[1]: stopped in /usr/ports *** Error code 1 Stop. make: stopped in /usr/ports failed to generate INDEX! portsdb: index generation error -- Thomas ___ 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
multimedia/ffmpeg0: opencv-core not found
I followed on FreebSD 11.0-CURRENT this morning the UPDATING instructions on that particular machine and receive the below shown error message. graphics/opencv-core has been deleted as instructed in UPDATING 20131203: and it has been reinstalled via portmaster -da, issued later. I also reinstalled opencv-core manually - with no success, this error is sticky. === Configuring for ffmpeg0-0.7.16_1,1 === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found Regards, O. Hartmann signature.asc Description: PGP signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ audio/quimup| 1.3.0 | 1.3.1 +-+ math/asir2000 | 20110810| 20131129 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org Thanks. ___ 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
pkg upgrade trouble with dependences
I have installed KDE4 and Gnome. (FreeBSD 10-beta4) When I update pkg upgrade I see: [some skipped] Conflict found on path /usr/local/share/xscreensaver/config/xmatrix.xml between xscreensaver-5.22_3(x11/xscreensaver) and xscreensaver-gnome-hacks-5.12_1(x11/xs creensaver-gnome-hacks) Conflict found on path /usr/local/share/xscreensaver/config/xrayswarm.xml betwee n xscreensaver-5.22_3(x11/xscreensaver) and xscreensaver-gnome-hacks-5.12_1(x11/ xscreensaver-gnome-hacks) Conflict found on path /usr/local/share/xscreensaver/config/xspirograph.xml betw een xscreensaver-5.22_3(x11/xscreensaver) and xscreensaver-gnome-hacks-5.12_1(x1 1/xscreensaver-gnome-hacks) Conflict found on path /usr/local/share/xscreensaver/config/zoom.xml between xsc reensaver-5.22_3(x11/xscreensaver) and xscreensaver-gnome-hacks-5.12_1(x11/xscre ensaver-gnome-hacks) How to solve the problem? -- -- Alex V. Petrov ___ 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
opencv update
I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file config.log produced by configure as this will help solving the problem. === Script configure failed unexpectedly. Please report the problem to w...@freebsd.org [maintainer] and attach the /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/config.err including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/ffmpeg0 *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/ffmpeg0 === make failed for multimedia/ffmpeg0 === Aborting update === Update for multimedia/ffmpeg0 failed === Aborting update === Killing background jobs Terminated === The following actions were performed: Installation of graphics/opencv-core (opencv-core-2.4.7) Upgrade of ffmpeg-2.1.1,1 to ffmpeg-2.1.1_1,1 === You can restart from the point of failure with this command line: portmaster flags multimedia/ffmpeg0 graphics/gstreamer-plugins-opencv graphics/opencv graphics/openimageio x11/xterm Thank you. -- Mitja --- http://www.redbubble.com/people/lumiwa ___ 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: Ports via svn, make fetchindex and make compatibility with NetBSD
Building ports on NetBSD is a whole other kettle of fish. It's not going to work without a lot of effort to add compatibility changes. (Getting the ports working on DFly which is much more closely related to FBSD has been a fairly recent achievement, and that took quite a lot of local patches.) Cheers, Matthew I noticed on the DFly site that Dfly was switching from NetBSD pkgsrc to dports, which is a port of FreeBSD ports. I guess they like FreeBSD ports better than NetBSD pkgsrc. NetBSD pkgsrc has been ported to many other OSes including some non-Unixoid, but I don't really want to use pkgsrc for Linux. DFly is rather incompatible with my system; I tried their live USB including the latest release 3.6.0 amd64 and i386. So is OpenBSD. Tom ___ 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: opencv update
On Wed, Dec 4, 2013 at 2:10 PM, Ajtim lum...@gmail.com wrote: I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file config.log produced by configure as this will help solving the problem. === Script configure failed unexpectedly. Please report the problem to w...@freebsd.org [maintainer] and attach the /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/config.err including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/ffmpeg0 *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/ffmpeg0 === make failed for multimedia/ffmpeg0 === Aborting update === Update for multimedia/ffmpeg0 failed === Aborting update === Killing background jobs Terminated === The following actions were performed: Installation of graphics/opencv-core (opencv-core-2.4.7) Upgrade of ffmpeg-2.1.1,1 to ffmpeg-2.1.1_1,1 === You can restart from the point of failure with this command line: portmaster flags multimedia/ffmpeg0 graphics/gstreamer-plugins-opencv graphics/opencv graphics/openimageio x11/xterm Thank you. -- Mitja --- http://www.redbubble.com/people/lumiwa I ran into something like that when the relevant files were installed, but didn't work (missing symbols in something it was linked to, I believe). What does the config.err file say? -- Daniel Nebdal ___ 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: Ports via svn, make fetchindex and make compatibility with NetBSD
On Tue, Dec 03, 2013 at 04:41:17AM -0800, Thomas Mueller wrote: Is it necessary to make fetchindex after downloading or updating the ports tree using svn? I have new installations of head and 10-stable where I so far can't connect to the Internet, though I can from Linux and NetBSD-current amd64. So I use subversion, built on NetBSD from pkgsrc, to checkout and update ports tree as well as system source tree. But I believe I can't run make fetchindex without Internet connection. Now I read that FreeBSD make has switched to bmake in the 10-stable and head branches. So could I run make fetchindex from NetBSD even if I don't attempt to actually build ports from NetBSD? I would have to point the MAKECONF to FreeBSD's /etc/make.conf rather than use NetBSD's /etc/mk.conf which is specific to NetBSD. Or is it safe to skip make fetchindex entirely? It is safe :) regards, Bapt pgpCNLtcUvqFA.pgp Description: PGP signature
Re: Ports via svn, make fetchindex and make compatibility with NetBSD
On Tue, 03 Dec 2013 13:27:57 + Matthew Seaman wrote: If you do need a copy of the index, then you have two choices * build your own. 'make index' will thrash your machine for upwards of twenty minutes, That's pessimistic, on my low-end i5 with low-performance disks, it takes between 2.25 and 3.5 minutes (depending on how many files are already cached) with no noticeable impact on performance. ___ 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: opencv update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2013 05:33, Daniel Nebdal wrote:
On Wed, Dec 4, 2013 at 2:10 PM, Ajtim lum...@gmail.com wrote:
I did what is in /usr/ports/UPDATING and looks like I am in
trouble now. My system is FreeBSD 10.0-BETA4 (amd64):
=== FreeBSD 10 autotools fix applied to
/usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR:
opencv-core not found
If you think configure made a mistake, make sure you are using
the latest version from Git. If the latest version fails, report
the problem to the ffmpeg-u...@ffmpeg.org mailing list or IRC
#ffmpeg on irc.freenode.net. Include the log file config.log
produced by configure as this will help solving the problem. ===
Script configure failed unexpectedly. Please report the problem
to w...@freebsd.org [maintainer] and attach the
/usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/config.err
including the output of the failure of your make command. Also,
it might be a good idea to provide an overview of all packages
installed on your system (e.g. a /usr/local/sbin/pkg-static info
-g -Ea). *** Error code 1
Stop. make[1]: stopped in /usr/ports/multimedia/ffmpeg0 *** Error
code 1
Stop. make: stopped in /usr/ports/multimedia/ffmpeg0
=== make failed for multimedia/ffmpeg0 === Aborting update
=== Update for multimedia/ffmpeg0 failed === Aborting
update
=== Killing background jobs Terminated === The following
actions were performed: Installation of graphics/opencv-core
(opencv-core-2.4.7) Upgrade of ffmpeg-2.1.1,1 to
ffmpeg-2.1.1_1,1
=== You can restart from the point of failure with this
command line: portmaster flags multimedia/ffmpeg0
graphics/gstreamer-plugins-opencv graphics/opencv
graphics/openimageio x11/xterm
Thank you. -- Mitja ---
http://www.redbubble.com/people/lumiwa
I ran into something like that when the relevant files were
installed, but didn't work (missing symbols in something it was
linked to, I believe). What does the config.err file say?
BEGIN /tmp/ffconf.h5eweeVe.c
1 #include opencv2/core/core_c.h
2 long check_cvCreateImageHeader(void) { return (long)
cvCreateImageHeader; }
3 int main(void) { return 0; }
END /tmp/ffconf.h5eweeVe.c
cc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC
- -O2 -pipe -march=native -msse -fno-strict-aliasing
- -I/usr/local/include/vorbis -I/usr/local/include -std=c99
- -fomit-frame-pointer -fPIC -I/usr/local/include/freetype2
- -I/usr/local/include -I/usr/local/include/opencv -I/usr/local/include
/usr/local/lib/libopencv_core.so /usr/local/lib/libopencv_imgproc.so
- -c -o /tmp/ffconf.KAxUBGTa.o /tmp/ffconf.h5eweeVe.c
cc: warning: /usr/local/lib/libopencv_core.so: 'linker' input unused
cc: warning: /usr/local/lib/libopencv_imgproc.so: 'linker' input unused
cc -L/usr/local/lib -Wl,--as-needed -I/usr/local/include/opencv
- -I/usr/local/include /usr/local/lib/libopencv_core.so
/usr/local/lib/libopencv_imgproc.so -o /tmp/ffconf.OA02kgLA
/tmp/ffconf.KAxUBGTa.o -L/usr/local/lib -lfreetype -lm -lbz2 -lz -pthread
/tmp/ffconf.KAxUBGTa.o: In function `check_cvCreateImageHeader':
/tmp/ffconf.h5eweeVe.c:(.text+0x3): undefined reference to
`cvCreateImageHeader'
cc: error: linker command failed with exit code 1 (use -v to see
invocation)
$ nm -a /usr/local/lib/libopencv_core.so.2
nm: /usr/local/lib/libopencv_core.so.2: no symbols
$ nm -a /usr/local/lib/libopencv_imgproc.so.2
nm: /usr/local/lib/libopencv_imgproc.so.2: no symbols
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlKfWgQACgkQrDN5kXnx8yZkPwCfTIIT5UzopcSi2K5CuYyAU/SM
ly8AnjwJXvn9OcHVq6MwbFIBFN1A12ab
=dX+E
-END PGP SIGNATURE-
___
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: tcl tk ports on FreeBSD 10 amd64
On Tue, 03 Dec 2013 21:32:56 -0800 Cy Schubert cy.schub...@komquats.com wrote: Hi, Sorry for cross posting but this concerns both lists. Over the last month or so I've been upgrading my prod infrastructure from 9 to 10. It's mostly complete except for a number of issues. One issue, just solved today (circumvented is a better word), is exmh crashing 10.0 on amd64 while on i386 there are no issues with exmh. It appears that the tcl and tk ports (all three of them, 8.4, 8.5, and 8.6) will panic 10.0 on amd64 (but not i386) when the ports are built with threading support. I haven't had a chance to look at the dump yet but I had a hunch to test the ports without threading support enabled, making the panic go away. If I don't get to it in time, here is what I haveFatal trap 9: general protection fault while in kernel mode cpuid = 2; apic id = 02 instruction pointer = 0x20:0x80957aeb stack pointer = 0x28:0xfe00f17f9980 frame pointer = 0x28:0xfe00f17f99a0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 11 (idle: cpu2) trap number = 9 timeout stopping cpus panic: general protection fault cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00f17f9510 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe00f17f95c0 panic() at panic+0x153/frame 0xfe00f17f9640 trap_fatal() at trap_fatal+0x3a2/frame 0xfe00f17f96a0 trap() at trap+0x7bf/frame 0xfe00f17f98c0 calltrap() at calltrap+0x8/frame 0xfe00f17f98c0 --- trap 0x9, rip = 0x80957aeb, rsp = 0xfe00f17f9980, rbp = 0xfe 00f17f99a0 --- cpu_idle_hlt() at cpu_idle_hlt+0x2b/frame 0xfe00f17f99a0 cpu_idle() at cpu_idle+0x93/frame 0xfe00f17f99c0 sched_idletd() at sched_idletd+0x1ee/frame 0xfe00f17f9a70 fork_exit() at fork_exit+0x9a/frame 0xfe00f17f9ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe00f17f9ab0 --- trap 0, rip = 0, rsp = 0xfe00f17f9b70, rbp = 0 --- Uptime: 4m42s Dumping 522 out of 5932 MB:..4%..13%..22%..31%..43%..53%..62%..71%..83%..92% so far, Tcl/tk are tickling some bug somewhere. Before anyone suggests memory, I've been able to reproduce this on an Intel Core i3 machine with 6 GB and an AMD X2 5000+, also with 6 GB, both in amd64 mode. Both systems are dual (or multi) boot. The bug does not exhibit itself in i386 mode. It also doesn't exhibit itself when tcl/tk are built without thread support. The only application I know of which tickles the bug is mail/exmh2 (I'm the maintainer) when using a threaded tcl/tk. My 11-CURRENT partition on my laptop is still i386 so I haven't been able to reproduce it under 11 with amd64. I used to use exmh all the time but then I started having problems with it so I switched to claws-mail. Anyway, I just installed exmh2 with threaded tcl/tk on FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #9 r258676: Wed Nov 27 09:57:24 CET 2013 amd64 CPU is a AMD Phenom(tm) II X6 1090T with 8GB of memory. Didn't have any crashes doing some cursory tests - mostly reading some e-mails downloaded with getmail. Didn't try editing or sending any mails. -- Gary Jennejohn ___ 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
security/trousers build failing on -current
My poudriere (from last night current and ports tree) reported the failure: full logs: http://bpaste.net/show/155463/ cheers, Hiren ___ 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: opencv update
Ajtim lum...@gmail.com writes: I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found Looks like ffmpeg0's opencv support should now depend on graphics/opencv rather than graphics/opencv-core. I'm testing this theory now... ___ 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: security/trousers build failing on -current
hiren panchasara hiren.panchas...@gmail.com wrote in calcpeufneryvopoq7fccynwmlvashfftnbplimqath58nov...@mail.gmail.com: hi My poudriere (from last night current and ports tree) reported the failure: hi hi full logs: hi hi http://bpaste.net/show/155463/ Thank you for your report. It should be fixed in r335632. -- Hiroki pgpFhStiIJ94l.pgp Description: PGP signature
Re: opencv update
Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes: Ajtim lum...@gmail.com writes: I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found Looks like ffmpeg0's opencv support should now depend on graphics/opencv rather than graphics/opencv-core. I'm testing this theory now... No, that's not right. There's some configure-script editing in the port that I hadn't noticed. It's probably a minor fix, but in the meantime turning off ffmpeg0's option for opencv should get you around it. ___ 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: security/trousers build failing on -current
On Wed, Dec 4, 2013 at 12:47 PM, Hiroki Sato h...@freebsd.org wrote: hiren panchasara hiren.panchas...@gmail.com wrote in calcpeufneryvopoq7fccynwmlvashfftnbplimqath58nov...@mail.gmail.com: hi My poudriere (from last night current and ports tree) reported the failure: hi hi full logs: hi hi http://bpaste.net/show/155463/ Thank you for your report. It should be fixed in r335632. Upgraded my ports tree and it failed at a later stage. full logs: http://bpaste.net/show/17/ cheers, Hiren ___ 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: security/trousers build failing on -current
hiren panchasara hiren.panchas...@gmail.com wrote in CALCpEUF=lx7evcvk9_hafepbgevzhrjwheywecnxfqr5cpc...@mail.gmail.com: hi On Wed, Dec 4, 2013 at 12:47 PM, Hiroki Sato h...@freebsd.org wrote: hi hiren panchasara hiren.panchas...@gmail.com wrote hiin calcpeufneryvopoq7fccynwmlvashfftnbplimqath58nov...@mail.gmail.com: hi hi hi My poudriere (from last night current and ports tree) reported the failure: hi hi hi hi full logs: hi hi hi hi http://bpaste.net/show/155463/ hi hi Thank you for your report. It should be fixed in r335632. hi hi Upgraded my ports tree and it failed at a later stage. hi hi full logs: hi http://bpaste.net/show/17/ Gr, please try r335650. I misunderstood how to handle empty directories when !NO_STAGE. -- Hiroki pgpxqI0_DY9QY.pgp Description: PGP signature
editors/vim failing to build on -current
With last night's -head and most updated ports tree. Full logs: http://bpaste.net/show/155572/ cheers, Hiren ___ 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: security/trousers build failing on -current
On Wed, Dec 4, 2013 at 4:24 PM, Hiroki Sato h...@freebsd.org wrote: hiren panchasara hiren.panchas...@gmail.com wrote in CALCpEUF=lx7evcvk9_hafepbgevzhrjwheywecnxfqr5cpc...@mail.gmail.com: hi On Wed, Dec 4, 2013 at 12:47 PM, Hiroki Sato h...@freebsd.org wrote: hi hiren panchasara hiren.panchas...@gmail.com wrote hiin calcpeufneryvopoq7fccynwmlvashfftnbplimqath58nov...@mail.gmail.com: hi hi hi My poudriere (from last night current and ports tree) reported the failure: hi hi hi hi full logs: hi hi hi hi http://bpaste.net/show/155463/ hi hi Thank you for your report. It should be fixed in r335632. hi hi Upgraded my ports tree and it failed at a later stage. hi hi full logs: hi http://bpaste.net/show/17/ Gr, please try r335650. I misunderstood how to handle empty directories when !NO_STAGE. It worked. Thanks a ton for prompt response and fix. Cheers, Hiren ___ 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: opencv update
On Thu, Dec 5, 2013 at 12:07 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes: Ajtim lum...@gmail.com writes: I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found Looks like ffmpeg0's opencv support should now depend on graphics/opencv rather than graphics/opencv-core. I'm testing this theory now... No, that's not right. There's some configure-script editing in the port that I hadn't noticed. It's probably a minor fix, but in the meantime turning off ffmpeg0's option for opencv should get you around it. I didn't verified it yet, but my assumption that it's combination of wrong order of linker parameters and --as-needed option. Libraries placed before object file, which uses them (wrong order), so at the time of theirs occurrence they are unneeded and therefore skipped. Similar problem would to occur independently of --as-needed if static libraries would be used instead of dynamic, or linker occur more strict/conservative. PS. @Mark: cvCreateImageHeader, symbol, which test program tries to find in opencv-core.so library, exists there and exported indeed. It absent in the output of plain nm (or 'nm -a' in your case) just because library is heavy stripped (removed anything unneeded for ld.so). If use 'nm -D', you will see that symbol. -- Andrew W. Nosenko andrew.w.nose...@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: [CFT] TPM(Trusted Platform Modules) replated ports
On Thu, Dec 5, 2013 at 5:10 AM, hiren panchasara hiren.panchas...@gmail.com wrote: On Wed, Dec 4, 2013 at 5:01 PM, Andrey Fesenko f0and...@gmail.com wrote: security/trousers - need add user in comand line and remove path var directory pkg-plist hrs@ just fixed this port a few mins back. Yes, install not error :) security/opencryptoki - checking for csulincl.h... no configure: error: tpm token build requested but TSS development files not found === Script configure failed unexpectedly. Try sending this report on ports@ ? cheers, Hiren No, make cc this message. ports revision 335651 configure: error: tpm token build requested but TSS development files not found === Script configure failed unexpectedly. Please report the problem to h...@freebsd.org [maintainer] and attach the /usr/ports/security/opencryptoki/work/opencryptoki-2.3.2/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). ___ 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: opencv update
On Thu, Dec 5, 2013 at 3:38 AM, Andrew W. Nosenko andrew.w.nose...@gmail.com wrote: On Thu, Dec 5, 2013 at 12:07 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org writes: Ajtim lum...@gmail.com writes: I did what is in /usr/ports/UPDATING and looks like I am in trouble now. My system is FreeBSD 10.0-BETA4 (amd64): === FreeBSD 10 autotools fix applied to /usr/ports/multimedia/ffmpeg0/work/ffmpeg-0.7.16/configure ERROR: opencv-core not found Looks like ffmpeg0's opencv support should now depend on graphics/opencv rather than graphics/opencv-core. I'm testing this theory now... No, that's not right. There's some configure-script editing in the port that I hadn't noticed. It's probably a minor fix, but in the meantime turning off ffmpeg0's option for opencv should get you around it. I didn't verified it yet, but my assumption that it's combination of wrong order of linker parameters and --as-needed option. Libraries placed before object file, which uses them (wrong order), so at the time of theirs occurrence they are unneeded and therefore skipped. Similar problem would to occur independently of --as-needed if static libraries would be used instead of dynamic, or linker occur more strict/conservative. PS. @Mark: cvCreateImageHeader, symbol, which test program tries to find in opencv-core.so library, exists there and exported indeed. It absent in the output of plain nm (or 'nm -a' in your case) just because library is heavy stripped (removed anything unneeded for ld.so). If use 'nm -D', you will see that symbol. ffmpeg0 configure script considers as libraries only parameters started with '-l'. See check_ld() functions. But opencv-core pkg-config file (opencv-core.pc) reports absolute library filenames /usr/local/lib/libopencv_core.so /usr/local/lib/libopencv_imgproc.so instead of expected by configure -L/usr/local/lib -lopencv_core -lopencv_imgproc. It results in treating these .so as CFLAGS with all consequences. There are two ways to cure: 1. patch ffmpeg0 configure to detect libraries without -l 2. patch opencv-core .pc file to report libraries as -lname instead of /path/to/libname.so Patch for ffmpeg0 configure is attached. -- Andrew W. Nosenko andrew.w.nose...@gmail.com patch-configure-check-ld Description: Binary data ___ 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
