Re: CFT: vlc 2.0.3 - want to know where it works and where only partly
On Fri, 3 Aug 2012 18:36:33 +0200 Juergen Lock n...@jelal.kn-bremen.de wrote: On Fri, Aug 03, 2012 at 05:00:37PM +0200, Rainer Hurling wrote: On 03.08.2012 14:27 (UTC+2), Gary Jennejohn wrote: On Thu, 2 Aug 2012 22:56:26 +0200 Juergen Lock n...@jelal.kn-bremen.de wrote: [trimmed irrelevant content] Ok I added that check: http://people.freebsd.org/~nox/tmp/vlc-2.0.3-005.patch Enjoy, :) AMD64 on HEAD. I always get this error, no matter which patch I use: GEN../modules/plugins.dat gmake[2]: *** [../modules/plugins.dat] Segmentation fault: 11 (core dumped) gmake[2]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.0.3/bin' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.0.3' gmake: *** [all] Error 2 *** [do-build] Error code 1 I get exactly the same error with CURRENT amd64. Hm how old are both your installed src and ports? You two are the first to report this and I just tried to reproduce it on a head checkout from May 13 and ports from June 18, and couldn't. I update the ports and source trees almost every day. I do not install new ports binaries unless absolutely necessary, so the ports binaries are pretty much rather old. Just installed a new world/kernel today (updated yesterdya), r239006. BTW, mplayer from ports does not build with liveMedia-20120404 ... Stop in /usr/ports/multimedia/vlc. *** [build] Error code 1 and there's a work/vlc-2.0.3/bin/vlc-cache-gen.core generated. May be because I have a mix of old and new dependencies, although the vlc port never tries to update any of them. Well ports never update dependencies themselves, you need to use tools like portmaster for that. I avoid using tools whenever possible. Maybe I will have to try portmaster, but I dread seeing 50 ports updated just because I want to update one port. I turned on -g in make.conf and ran vlc-cache-gen in gdb. Here's the result. gdb /usr/ports/multimedia/vlc/work/vlc-2.0.3/bin/.libs/vlc-cache-gen GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... (gdb) r ../modules/ Starting program: /usr/ports/multimedia/vlc/work/vlc-2.0.3/bin/.libs/vlc-cache-gen ../modules/ [New LWP 100125] [New Thread 802406400 (LWP 100125/vlc-cache-gen)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 802406400 (LWP 100125/vlc-cache-gen)] 0x000800606588 in matched_symbol () from /libexec/ld-elf.so.1 (gdb) bt #0 0x000800606588 in matched_symbol () from /libexec/ld-elf.so.1 #1 0x0008006087e4 in symlook_obj () from /libexec/ld-elf.so.1 #2 0x000800608ae7 in symlook_list () from /libexec/ld-elf.so.1 #3 0x00080060911b in symlook_default () from /libexec/ld-elf.so.1 #4 0x00080060939d in find_symdef () from /libexec/ld-elf.so.1 #5 0x00080060375b in reloc_non_plt () from /libexec/ld-elf.so.1 #6 0x000800606ae8 in relocate_object () from /libexec/ld-elf.so.1 #7 0x0008006084a8 in dlopen_object () from /libexec/ld-elf.so.1 #8 0x000800608f67 in rtld_dlopen () from /libexec/ld-elf.so.1 #9 0x000800affe95 in module_Load (p_this=0x80244c198, psz_file=0x802472c00 ../modules//codec/.libs/libfluidsynth_plugin.so, p_handle=0x7fffd180, lazy=true) at posix/plugin.c:62 #10 0x000800adef4b in module_InitDynamic (obj=0x80244c198, path=0x802472c00 ../modules//codec/.libs/libfluidsynth_plugin.so, fast=true) at modules/bank.c:536 #11 0x000800adede2 in AllocatePluginFile (bank=0x7fffd490, abspath=0x802472c00 ../modules//codec/.libs/libfluidsynth_plugin.so, relpath=0x802472b80 codec/.libs/libfluidsynth_plugin.so, st=0x7fffd210) at modules/bank.c:479 #12 0x000800adeca3 in AllocatePluginDir (bank=0x7fffd490, maxdepth=2, absdir=0x802472b00 ../modules//codec/.libs, reldir=0x802472a80 codec/.libs) at modules/bank.c:440 #13 0x000800adecd7 in AllocatePluginDir (bank=0x7fffd490, maxdepth=3, absdir=0x802472a00 ../modules//codec, reldir=0x8024704f0 codec) at modules/bank.c:444 #14 0x000800adecd7 in AllocatePluginDir (bank=0x7fffd490, maxdepth=4, absdir=0x802452c20 ../modules/, reldir=0x0) at modules/bank.c:444 #15 0x000800ade9b8 in AllocatePluginPath (p_this=0x80244c198, path=0x802452c20 ../modules/, mode=CACHE_USE) at modules/bank.c:353 #16 0x000800ade823 in AllocateAllPlugins (p_this=0x80244c198) at modules/bank.c:298 #17 0x000800ade55d in module_LoadPlugins (obj=0x80244c198) at modules/bank.c:189 #18 0x000800a53e63 in libvlc_InternalInit (p_libvlc=0x80244c198,
Re: gam_server hitting 100% cpu
On Sat, 4 Aug 2012, the wise Kevin Oberman wrote: Do you have comms/usbmuxd installed? I seem to recall an issue where it could cause one of the Gnome related processes to go to 100%. I just don't recall if it was gamin, but I removed the usbmuxd port and those dependent on it, all of which involved iPod tools. If this is the case, it happens in Linux, too, so the maintainer my not be able to help as the problem is upstream Usbmuxd was installed and I deinstalled it (and also two dependencies for ipod stuff), but gam_server keeps going to 100% just after starting Gnome. Killing gam_server doesn't help either, it just keeps coming back. Regards, Marco -- Ever feel like you're the head pin on life's bowling alley, and everyone's rolling strikes? ___ 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: May I update www/linux-opera to 12.00?
Am 01.08.2012 04:19, schrieb Jeremy Messenger: May I commit the update of www/linux-opera to 12.00? Here's patch: http://people.freebsd.org/~mezz/diff/linux-opera.diff Not speaking on behalf of the maintainer, but no, because that would leave known security issues unsolved. Use 12.01 instead. ___ 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
FreeBSD Port: ffmpeg-0.7.13_4,1
Hello, ffmpeg requires the permission to execute files in /tmp which is rather odd, not to mention that users shouldn't be allowed to run things in /tmp. This is a problem on user systems because /tmp and ~/.. should be mounted nosuid noexec for obvious security reasons. When compiling or updating ffmpeg this imposes the need to go single-user which could be a problem in production environments. This is probably something that I could bring up with the development team, though you may be more able to appreciate and value my point towards them. Sincerely, Patrick Dorion ___ 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] [bsd.port.mk] ports ccache build support
On Fri, 03 Aug 2012 20:05:54 -0500
Bryan Drewery wrote:
Hi,
ports/169579 is currently tracking this.
This patch adds ccache support to ports (off by default). Other
patches have changed $CC to use ccache, which results in having a
space in $CC. This breaks many ports such as boost and libtool ports.
This patch however utilizes the symlinks in
/usr/local/libexec/ccache/{cc,gcc,etc...} by prefixing that directory
into $PATH in the $MAKE_ENV.
But if you've read the ccache documentation you probably already have
that directory in PATH anyway. Does this patch provide a significant
advantage?
The cache directory CCACHE_DIR defaults to /usr/obj/ccache
...
To use ccache(1) from the command line to configure the size or view
stats: CCACHE_DIR=/usr/obj/ccache ccache -s
Having a default ccache directory in the makefile that's different from
the default documented in the ccache man page seems needlessly
confusing to me.
And see hier(7) and section 25.7.6 of the handbook for
why /usr/obj/ccache is a poor choice.
___
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] [bsd.port.mk] ports ccache build support
On 8/4/2012 8:16 AM, RW wrote:
On Fri, 03 Aug 2012 20:05:54 -0500
Bryan Drewery wrote:
Hi,
ports/169579 is currently tracking this.
This patch adds ccache support to ports (off by default). Other
patches have changed $CC to use ccache, which results in having a
space in $CC. This breaks many ports such as boost and libtool ports.
This patch however utilizes the symlinks in
/usr/local/libexec/ccache/{cc,gcc,etc...} by prefixing that directory
into $PATH in the $MAKE_ENV.
But if you've read the ccache documentation you probably already have
that directory in PATH anyway. Does this patch provide a significant
advantage?
That requires needless customization. The purpose here is easy, safe and
native support.
The included ccache-howto-freebsd.txt with devel/ccache is quite long
for something that is straight forward.
I've seen many incorrect guides that suggest changing $CC. There's forum
posts and sysutils/bsdadminscripts that do this. This leads to broken
builds and needing to define which ports support ccache via $CC and
which do not.
The cache directory CCACHE_DIR defaults to /usr/obj/ccache
...
To use ccache(1) from the command line to configure the size or view
stats: CCACHE_DIR=/usr/obj/ccache ccache -s
Having a default ccache directory in the makefile that's different from
the default documented in the ccache man page seems needlessly
confusing to me.
The default being $HOME/.ccache makes even less sense for port building.
And see hier(7) and section 25.7.6 of the handbook for
why /usr/obj/ccache is a poor choice.
I think /usr/obj makes sense. There is /var/cache now, but /var is
typically a smaller partition.
Do you have a better suggestion?
--
Regards,
Bryan Drewery
bdrewery@freenode/EFNet
___
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: gam_server hitting 100% cpu
On Sat, 4 Aug 2012, the wise Kevin Oberman wrote: Finally found this one. Gamin needs some files that aren't there by default: ~/.gaminrc and /usr/local/etc/gamin/gaminrc. In these files you need to put two lines: fsset ufs poll 10 fsset zfs poll 10 to prevent gam_server from polling constantly. Regards, Marco NB: don't know if this mail is making it to the ports mailing list. My ISP is blocking freebsd.org for some reason. -- Leibowitz's Rule: When hammering a nail, you will never hit your finger if you hold the hammer with both hands. ___ 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] [bsd.port.mk] ports ccache build support
On Sat, Aug 4, 2012 at 5:42 PM, Bryan Drewery bdrew...@freebsd.org wrote:
On 8/4/2012 8:16 AM, RW wrote:
On Fri, 03 Aug 2012 20:05:54 -0500
Bryan Drewery wrote:
Hi,
ports/169579 is currently tracking this.
This patch adds ccache support to ports (off by default). Other
patches have changed $CC to use ccache, which results in having a
space in $CC. This breaks many ports such as boost and libtool ports.
This patch however utilizes the symlinks in
/usr/local/libexec/ccache/{cc,gcc,etc...} by prefixing that directory
into $PATH in the $MAKE_ENV.
But if you've read the ccache documentation you probably already have
that directory in PATH anyway. Does this patch provide a significant
advantage?
That requires needless customization. The purpose here is easy, safe and
native support.
The included ccache-howto-freebsd.txt with devel/ccache is quite long
for something that is straight forward.
I've seen many incorrect guides that suggest changing $CC. There's forum
posts and sysutils/bsdadminscripts that do this. This leads to broken
builds and needing to define which ports support ccache via $CC and
which do not.
The cache directory CCACHE_DIR defaults to /usr/obj/ccache
...
To use ccache(1) from the command line to configure the size or view
stats: CCACHE_DIR=/usr/obj/ccache ccache -s
Having a default ccache directory in the makefile that's different from
the default documented in the ccache man page seems needlessly
confusing to me.
The default being $HOME/.ccache makes even less sense for port building.
And see hier(7) and section 25.7.6 of the handbook for
why /usr/obj/ccache is a poor choice.
I think /usr/obj makes sense. There is /var/cache now, but /var is
typically a smaller partition.
Do you have a better suggestion?
Based on what I've read on the subject I'd say it's better to leave
/usr/obj to just for stuff from /usr/src. I vote for /var/cache/ccache
as the default ccache directory.
-Kimmo
___
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: May I update www/linux-opera to 12.00?
On Sat, Aug 4, 2012 at 7:22 AM, Matthias Andree mand...@freebsd.org wrote: Am 01.08.2012 04:19, schrieb Jeremy Messenger: May I commit the update of www/linux-opera to 12.00? Here's patch: http://people.freebsd.org/~mezz/diff/linux-opera.diff Not speaking on behalf of the maintainer, but no, because that would leave known security issues unsolved. Use 12.01 instead. I know. It was before 12.01 out and I already have 12.01 here. The reason why I didn't commit it is that I found out that linux-opera will not exit, which I had to use the killall to kill it at the every time when I want to exit linux-opera. I haven't dig in it to figure why it will not exit yet. -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ 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: gam_server hitting 100% cpu
The file /usr/local/etc/gamin/gaminrc is not always necessary, and setting the time interval to 10 seconds may cause gamin to function improperly according to my experience. Hope someone could dig into the problem and find a solution. B.R. HU Dong On Sat, Aug 4, 2012 at 10:48 PM, Marco Beishuizen mb...@xs4all.nl wrote: On Sat, 4 Aug 2012, the wise Kevin Oberman wrote: Finally found this one. Gamin needs some files that aren't there by default: ~/.gaminrc and /usr/local/etc/gamin/gaminrc. In these files you need to put two lines: fsset ufs poll 10 fsset zfs poll 10 to prevent gam_server from polling constantly. Regards, Marco NB: don't know if this mail is making it to the ports mailing list. My ISP is blocking freebsd.org for some reason. -- Leibowitz's Rule: When hammering a nail, you will never hit your finger if you hold the hammer with both hands. ___ 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: VLC 2.0.3
On Fri, Aug 03, 2012 at 11:54:36PM +0200, Claude Buisson wrote: Hi, Hi! I have done a few tests with VLC 2.0.3 and your patch (005), on 9.0-STABLE (svn r236523) i386, with a port tree mainly from 2012/05/28 (of course this needed some tweaks, as this tree does not support options ng). The build was done with gcc 4.6.3 (lang/gcc). No fancy test, only listening some CDs and watching some DVDs. Everything tested was OK. For a build with SKINS, the compilation failed with: x11/x11_window.cpp: In constructor 'X11Window::X11Window(intf_thread_t*, \ GenericWindow, X11Display, bool, bool, X11Window*, \ GenericWindow::WindowType_t)': x11/x11_window.cpp:202:25: error: '_POSIX_HOST_NAME_MAX' was not declared in \ this scope which is corrected by the attached patch. See also: http://permalink.gmane.org/gmane.comp.video.videolan.vlc.scm/8740 Thanks for your work, Thanx for this fix, I posted a new patch with it added: http://people.freebsd.org/~nox/tmp/vlc-2.0.3-006.patch Enjoy, :) Juergen ___ 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: vlc 2.0.3 - want to know where it works and where only partly
On Fri, Aug 03, 2012 at 01:59:03PM -0700, Doug Barton wrote: On 08/03/2012 01:28 PM, Rainer Hurling wrote: I tried to first deinstall vlc-1.1.13 and install 2.0.3 after that with success. Obviously the build has a problem with files outside of WRKSRC? When I did my successful build on current-amd64 I just patched the port directory, and used portmaster to do the update ... meaning that the old port was still installed when I built the new one. However, I use a separate WRKDIRPREFIX, maybe that made a difference? When I tested this on head I did the same and didn't get a crash, and I don't set WRKDIRPREFIX on that installation, so at least it can't be that alone. I just did LD_LIBRARY_PATH=work/fake/usr/local/lib ldd work/fake/usr/local/lib/vlc/vlc-cache-gen and got: work/fake/usr/local/lib/vlc/vlc-cache-gen: libvlc.so.8 = work/fake/usr/local/lib/libvlc.so.8 (0x800647000) libvlccore.so.6 = work/fake/usr/local/lib/libvlccore.so.6 (0x80075f000) libdbus-1.so.3 = /usr/local/lib/libdbus-1.so.3 (0x80093d000) libthr.so.3 = /lib/libthr.so.3 (0x800a8b000) libintl.so.9 = /usr/local/lib/libintl.so.9 (0x800ba3000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x800cac000) libm.so.5 = /lib/libm.so.5 (0x800ea6000) libc.so.7 = /lib/libc.so.7 (0x800fc5000) so it's not picking up wrong libs either... I guess unless someone can figure out the real cause and a proper fix we'll have to add a note to UPDATING to the effect if your vlc build dies try removing the old version first. :/, Juergen ___ 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] [bsd.port.mk] ports ccache build support
On 08/04/2012 08:03, Kimmo Paasiala wrote: Based on what I've read on the subject I'd say it's better to leave /usr/obj to just for stuff from /usr/src. Yes please. :) -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ 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] [bsd.port.mk] ports ccache build support
On 08/03/2012 18:05, Bryan Drewery wrote:
This patch however utilizes the symlinks in
/usr/local/libexec/ccache/{cc,gcc,etc...} by prefixing that directory
into $PATH in the $MAKE_ENV.
FWIW, when I was asked to add ccache support to portmaster this was the
method suggested to me. I added it years ago, and have never had a user
complain that it didn't work.
hth,
Doug
--
I am only one, but I am one. I cannot do everything, but I can do
something. And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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
Can't get gvim working
Hi, I enabled the WITH_OPTIONS in the editors/vim port, and installed with X11, GTK2 and GNOME2 options, but gvim stills says : E25: GUI cannot be used: Not enabled at compile time As you can see the output of make showconfig: === The following configuration options are available for vim-7.3.556_1: PERL=off: Enable Perl interpreter PYTHON=off: Enable Python interpreter RUBY=off: Enable Ruby interpreter TCL=off: Enable TCL interpreter LUA=off: Enable lua interpreter LANG=off: VIm Translations CSCOPE=off: Enable cscope EXUBERANT_CTAGS=off: Use exctags instead of ctags X11=on: X11 support (required for options below) X11_ONLY=off: CLI-only Vim, but with basic X11 support XTERM_SAVE=off: Restore xterm screen after exit ATHENA=off: Athena GUI GTK2=on: GTK2 GUI GNOME2=on: Gnome2 GUI MOTIF=off: Motif GUI === Use 'make config' to modify these settings Cheers, -- David Demelier ___ 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: Can't get gvim working
On 08/04/2012 14:02, David Demelier wrote: Hi, I enabled the WITH_OPTIONS in the editors/vim port, and installed with X11, GTK2 and GNOME2 options, but gvim stills says : E25: GUI cannot be used: Not enabled at compile time As you can see the output of make showconfig: === The following configuration options are available for vim-7.3.556_1: PERL=off: Enable Perl interpreter GNOME2=on: Gnome2 GUI Works fine for me, the only difference in settings is that I have these 2 knobs flipped. Unlikely the first matters, but the gnome option is probably relevant. hth, Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ 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: Can't get gvim working
On 04/08/2012 23:34, Doug Barton wrote: On 08/04/2012 14:02, David Demelier wrote: Hi, I enabled the WITH_OPTIONS in the editors/vim port, and installed with X11, GTK2 and GNOME2 options, but gvim stills says : E25: GUI cannot be used: Not enabled at compile time As you can see the output of make showconfig: === The following configuration options are available for vim-7.3.556_1: PERL=off: Enable Perl interpreter GNOME2=on: Gnome2 GUI Works fine for me, the only difference in settings is that I have these 2 knobs flipped. Unlikely the first matters, but the gnome option is probably relevant. hth, Doug I finally found the problem: at the configure target see, checking for GTK - version = 2.2.0... Package glproto was not found in the pkg-config search path. Perhaps you should add the directory containing `glproto.pc' to the PKG_CONFIG_PATH environment variable No package 'glproto' found no x11/glproto was not installed, I think we could add a dependency on it. Cheers, -- David Demelier ___ 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: Can't get gvim working
On 08/04/2012 14:56, David Demelier wrote:
I finally found the problem: at the configure target see,
checking for GTK - version = 2.2.0... Package glproto was not found in the
pkg-config search path.
Perhaps you should add the directory containing `glproto.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glproto' found
no
x11/glproto was not installed, I think we could add a dependency on it.
Seems to apply only to the gnome define, as I can build and run gvim
without it.
David, what do you think of the attached?
Doug
--
I am only one, but I am one. I cannot do everything, but I can do
something. And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
Index: Makefile
===
--- Makefile(revision 302028)
+++ Makefile(working copy)
@@ -156,7 +156,7 @@
PKGNAMESUFFIX= -gnome2
MAKE_ARGS+=CONF_OPT_GUI=--enable-gui=gnome2 ${I18N}
MAKE_ARGS+=X_LIBS=$(X_LIBS) -lXt
-USE_XORG+= xt
+USE_XORG+= glproto xt
. elif defined(WITH_MOTIF)
USE_MOTIF= yes
MAKE_ARGS+=CONF_OPT_GUI=--enable-gui=motif
--with-motif-lib=\${MOTIFLIB}\ MOTIFHOME=${LOCALBASE} ${I18N}
___
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] [bsd.port.mk] ports ccache build support
On Sat, 04 Aug 2012 09:42:39 -0500 Bryan Drewery wrote: But if you've read the ccache documentation you probably already have that directory in PATH anyway. Does this patch provide a significant advantage? That requires needless customization. The purpose here is easy, safe and native support. The included ccache-howto-freebsd.txt with devel/ccache is quite long for something that is straight forward. I think that's an exaggeration. I'd say it's quite short and most of it is easily skipped over. Having a default ccache directory in the makefile that's different from the default documented in the ccache man page seems needlessly confusing to me. The default being $HOME/.ccache makes even less sense for port building. No, but it has the merit of being documented as being the default in the first place one is likely to look. And since large root file-systems seem to be increasingly popular, /root/.ccache may seem reasonable, and people may run cache -M on that. ___ 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: php53-pdo_mysql fail with MYSQLND
On 3/8/2012 23:44, Michael Ranner wrote: Hello! I have trouble with upgrading php53-pdo_mysql (5.3.14 to 5.3.15) on several systems, where I try to upgrade with portmaser. Build works without option MYSQLND but breaks with MYSQLND. Probably this have something to do with ports/169959. poudriere builds php53-pdo_mysql without problems from scratch, but I have no idea why it breaks ob my production systems. Hello, I had the same problem and managed to get around it by deinstalling php53-pdo_mysql 5.3.14 and then installing php53-pdo_mysql 5.3.15. MYSQLND was not defined, but in my case the problem seemed to be the definition #define HAVE_MYSQL_STMT_PREPARE 1 in /usr/local/include/php/ext/pdo_mysql/config.h of the php53-pdo_mysql 5.3.14 installation. Regards, Panagiotis -- Panagiotis J. ChristiasNetwork Management Center p.christ...@noc.ntua.grNational Technical Univ. of Athens, GREECE ___ 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] [bsd.port.mk] ports ccache build support
On 4 August 2012 15:21, RW rwmailli...@googlemail.com wrote: On Sat, 04 Aug 2012 09:42:39 -0500 Bryan Drewery wrote: Having a default ccache directory in the makefile that's different from the default documented in the ccache man page seems needlessly confusing to me. +1 for /var/cache And since large root file-systems seem to be increasingly popular, /root/.ccache may seem reasonable, and people may run cache -M on that. remember that its possible to build as a non-root user, but install as root, or similar. Using $HOME for any aspect of the build isn't a good idea. -- Eitan Adler ___ 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
Here's unfinish LightDM port.
Hello all, I have promised about that I will clean up and post the unfinished LightDM port for anyone that who want to finish it. When I discovered about x11/slim and I have lost interest to work more on LightDM as I have enough stuff on my plate. Keep in mind, it only will taking you to the log in screen but you can't enter the password at all. I haven't dig in it for why it doesn't work. I am a bit stupid on PAM stuff, so probably it has wrong configuration in the /usr/local/etc/pam.d/lightdm* or something else. The rc start up script is also incomplete, but it works. It will needs to have options for any users can do something like lightdm-greeters=lightdm-gtk-greeter in /etc/rc.conf instead of have to edit the /usr/local/etc/lightdm.conf to allow use lightdm-gtk-greeter. There are a few of different greeters like KDE greeter, XFCE and etc. Here's two shar files: http://people.freebsd.org/~mezz/shar/lightdm.shar http://people.freebsd.org/~mezz/shar/lightdm-gtk-greeter.shar I have the user/group (/usr/ports/GIDs and /usr/ports//UIDs) look like this: # grep lightdm /etc/group lightdm:*:959: # grep lightdm /etc/passwd lightdm:*:959:959:LightDM Display Manager:/usr/local/etc/lightdm/home:/usr/sbin/nologin Oh yeah, I total forgot about that I have found a patch from somewhere mailing list to add 'X -novtswitch' support in the x11-servers/xorg-server. The LightDM will need it unless you know the another way. Put this file in the x11-servers/xorg-server/files/. Although, I don't know if it's 100% works, but at least it got me to the log in screen. *chuckles* http://people.freebsd.org/~mezz/patch/patch-hw__xfree86__os-support__bsd__bsd_init.c Cheers, Mezz -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ 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
