Gnash-devel not working with firefox
Greetings For some reason gnash-devel is no longer showing as a plugin in firefox. I am not sure but it may have started with the last firefox upgrade (7.0.1,1). I have rebuilt gnash-devel and firefox to no avail. This is happening on i386 8.2 stable, amd64 8.2 stable and i386 9.0 beta 3. Does anyone know if there has been a change? I never had to do any softlinks or anything else. I previously just installed gnash-devel and check the plugin option and it worked. Anyone else seeing this? Thanks in advance. Robert ___ 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: Still can't build libreoffice
on 04/10/2011 07:10 Doug Barton said the following:
For libreoffice the only option I have enabled is GTK. With that
configuration it fails like this:
--
- start unit test #1 on library ../../unxfbsd.pro/lib/libcppu_ifcontainer.so
--
:
LD_LIBRARY_PATH=/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/clone/ure/cppuhelper/unxfbsd.pro/lib:/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/solver/340/unxfbsd.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/solver/340/unxfbsd.pro/bin/cppunit/cppunittester
../../unxfbsd.pro/lib/libcppu_ifcontainer.so
OK (5)
---
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development
internal build errors:
ERROR: error 65280 occurred while making
/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/cppuhelper/qa/unourl
it seems that the error is inside 'cppuhelper', please re-run build
inside this module to isolate the error and/or test your fix:
---
It looks like this excerpt doesn't contain the actual error.
It does contain the start of the instructions to isolate the error, though.
--
Andriy Gapon
___
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: Still can't build libreoffice
On Tue, Oct 4, 2011 at 7:10 AM, Doug Barton do...@freebsd.org wrote: ERROR: error 65280 occurred while making /home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/cppuhelper/qa/unourl it seems that the error is inside 'cppuhelper', please re-run build inside this module to isolate the error and/or test your fix: --- The project's wiki is very helpful on how to debug build errors. [1] You need to rerun build / gmake inside the failing module to get the actual error. [1] http://wiki.documentfoundation.org/Development/Native_Build#Partial_build Regards, George ___ 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: Gnash-devel not working with firefox
On Tue, Oct 04, 2011 at 05:27:39AM -0700, Robert wrote: Greetings For some reason gnash-devel is no longer showing as a plugin in firefox. I am not sure but it may have started with the last firefox upgrade (7.0.1,1). I have rebuilt gnash-devel and firefox to no avail. This is happening on i386 8.2 stable, amd64 8.2 stable and i386 9.0 beta 3. Does anyone know if there has been a change? I never had to do any softlinks or anything else. I previously just installed gnash-devel and check the plugin option and it worked. Anyone else seeing this? Thanks in advance. I'm seeing this with all plugins installed in the global directories. Looks like Firefox 7 modified something in the search path for plugins. Truss shows it's not looking in /usr/local/lib/browser_plugins/symlinks/gecko19 anymore. It does look in /usr/local/lib/firefox/plugins. I made the following symlink in there to have it work again: lrwxr-xr-x 1 root wheel35 Sep 29 14:12 plugins - ../browser_plugins/symlinks/gecko19 I'm not sure if this one needs to be fixed in the plugin ports or in the firefox port. -- Guido Falsi m...@madpilot.net ___ 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: Gnash-devel not working with firefox
On Tue, 4 Oct 2011 16:22:42 +0200 Guido Falsi m...@madpilot.net wrote: On Tue, Oct 04, 2011 at 05:27:39AM -0700, Robert wrote: Greetings For some reason gnash-devel is no longer showing as a plugin in firefox. I am not sure but it may have started with the last firefox upgrade (7.0.1,1). I have rebuilt gnash-devel and firefox to no avail. This is happening on i386 8.2 stable, amd64 8.2 stable and i386 9.0 beta 3. Does anyone know if there has been a change? I never had to do any softlinks or anything else. I previously just installed gnash-devel and check the plugin option and it worked. Anyone else seeing this? Thanks in advance. I'm seeing this with all plugins installed in the global directories. Looks like Firefox 7 modified something in the search path for plugins. Truss shows it's not looking in /usr/local/lib/browser_plugins/symlinks/gecko19 anymore. It does look in /usr/local/lib/firefox/plugins. I made the following symlink in there to have it work again: lrwxr-xr-x 1 root wheel35 Sep 29 14:12 plugins - ../browser_plugins/symlinks/gecko19 I'm not sure if this one needs to be fixed in the plugin ports or in the firefox port. Thanks Guido I was able to get gnash-devel to work with this symlink: libgnashplugin.so - ../browser_plugins/gnash-devel/libgnashplugin.so in /usr/local/lib/firefox Robert ___ 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: Gnash-devel not working with firefox
On Tue, 4 Oct 2011 11:29:28 -0700 Robert travelin...@cox.net wrote: On Tue, 4 Oct 2011 16:22:42 +0200 Guido Falsi m...@madpilot.net wrote: On Tue, Oct 04, 2011 at 05:27:39AM -0700, Robert wrote: Greetings For some reason gnash-devel is no longer showing as a plugin in firefox. I am not sure but it may have started with the last firefox upgrade (7.0.1,1). I have rebuilt gnash-devel and firefox to no avail. This is happening on i386 8.2 stable, amd64 8.2 stable and i386 9.0 beta 3. Does anyone know if there has been a change? I never had to do any softlinks or anything else. I previously just installed gnash-devel and check the plugin option and it worked. Anyone else seeing this? Thanks in advance. I'm seeing this with all plugins installed in the global directories. Looks like Firefox 7 modified something in the search path for plugins. Truss shows it's not looking in /usr/local/lib/browser_plugins/symlinks/gecko19 anymore. It does look in /usr/local/lib/firefox/plugins. I made the following symlink in there to have it work again: lrwxr-xr-x 1 root wheel35 Sep 29 14:12 plugins - ../browser_plugins/symlinks/gecko19 I'm not sure if this one needs to be fixed in the plugin ports or in the firefox port. Thanks Guido I was able to get gnash-devel to work with this symlink: libgnashplugin.so - ../browser_plugins/gnash-devel/libgnashplugin.so Doh! Ignore that. Your symlink was all that was needed. I failed to restart firefox after creating the symlink. Robert ___ 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: Still can't build libreoffice
On Tue, Oct 04, 2011 at 09:12:31PM +0200, Oliver Heesakkers wrote: On 04.10.2011 06:10, Doug Barton wrote: On 10/03/2011 07:32, Oliver Heesakkers wrote: I have the same problem (9.0 BETA3 amd64) When I set libreoffice's DEBUG option, the build (`make`) does complete. Thanks, that gave me some new places to look. I had the following in make.conf: CFLAGS+= -g DEBUG_FLAGS+= -g Commenting those out avoids the cppunittest error, but now it fails in various random locations depending on the options I choose. I still have the following in make.conf in case that's relevant: (...) I tried enabling the DEBUG option and that just caused it to fail somewhere else. That makes no sense to me, as enabling DEBUG for libreoffice lets me complete the build. I moved my entire portstree to /home and was able to build, install, package and run a debug build of libreoffice (30G to build, 1.2G as a package) I have nothing in make.conf but perl / ruby / python version declarations, LOCALIZED_LANG=nl and now of course PORTSDIR=home/ports Running a debug build is far from ideal, so I'm still looking for a solution. Comparing my script-output with Nikolov's tb-log I note that Nikolov: - has more dependencies - uses nawk instead of gawk - uses tar instead of gtar - uses OSVERSION=900039 instead of OSVERSION=900044 - uses gtk instead of kde4 VCLplug - - (I also get a configure: WARNING: unrecognized options: --with-qt-includes, --with-qt-libraries, --with-extra-libs, --with-extra-includes) - uses en-US instead of nl (I have LOCALIZED_LANG=nl in make.conf) - has 1 instead of 2 processors to use This last one seems interesting to me, looking futher I notice that modules are delivered in a different order. Comparing the three builds, all three have a different order, i.e.: testautomation is delivered first in Nikolov's build and my DEBUG build, but in my failing non-DEBUG build it gets delivered third. Is the order in which modules are delivered relevant? Can I force my build process to run on one processor to see if this makes a difference? add --with-num-cpus=1 and --with-max-jobs=1 to the configure args. regards, Bapt pgpJDXmOH2ld2.pgp Description: PGP signature
shells/ksh93 segfaults on suspend
The version of ksh93 currently in ports suffers from a bug that causes it to segfault on suspend: $ pkg_info -I ksh\* ksh93-20110208_1Official ATT release of KornShell 93 $ su - Password: # echo $KSH_VERSION Version JM 93u 2011-02-08 # ps -p $$ PID TT STAT TIME COMMAND 60190 4 S 0:00.01 -su (ksh) # suspend $ jobs $ dmesg | tail -1 pid 60190 (ksh), uid 0: exited on signal 11 (core dumped) $ A bit of searching turned up that this is a known bug[1] that was fixed by Red Hat last April. I don't know if they pushed their fix upstream. Should I file a PR for this, or are there plans to update the ksh93 port soon anyway? [1] https://bugzilla.redhat.com/show_bug.cgi?id=691077 -- Greg Rivers ___ 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
