vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26
Hi, I tried to install the vsftpd-2.0.6 port on FreeBSD 4.11-p26, but failed with the following error message :- ## begin of error log ## gcc -c privops.c -O2 -Wall -W -Wshadow -idirafter dummyinc privops.c: In function `vsf_privop_get_ftp_port_sock': privops.c:58: syntax error before `double' privops.c:59: `sleep_for' undeclared (first use in this function) privops.c:59: (Each undeclared identifier is reported only once privops.c:59: for each function it appears in.) *** Error code 1 Stop in /usr/local/src/vsftpd-2.0.6. ## end of error log ## I hope someone can help to advise how I can install vsftpd-2.0.6 on FreeBSD 4.11 Thanks a lot. John Mok ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Sun, Apr 13, 2008 at 05:59:09PM +0200, Henrik Brix Andersen wrote: > On Tue, Apr 08, 2008 at 10:17:56PM -0400, Joe Marcus Clarke wrote: > > gio-fam-backend is a new piece of glib which provides a wrapper around > > FAM to allow applications to monitor file objects using a glib API. > > But this is optional, right? Any reason for making gio-fam-backend an > implicit dependency for all software, that depends on glib20? > > On my systems, this means I will get gio-fam-backend installed even > though I don't have FAM installed at all. > Hello! Just another vote against gio-fam-backend. I had have a quick look at mailing lists archives and hadn't found any discussion about it prior to commit. The point is thas gtk != gnome. Even more so glib != gnome. Introducing gio-fam-backend as a dependency to glib automatically adds it to the dependency lists of too many other (not gnome related) ports. Personally I don't use neither gnome nor kde but I use gtk apps (gqview, gimp, beep-media-player, mplayer, seamonkey, ...) and for now I have no FAM system installed and I don't want any at all. I had some experience with FAM some time ago when it was non-optional requirement for samba. Since then I don't like FAM systems due to their 'viral' nature: many ports will auto-detect and uncoditionally link with them. Sweeping FAM out of the system after that is not straightforward process. Another aspect is that FAM is not so critical for most apps (I believe). With samba it is clear: samba wants to monitor its conf files in order to apply changes immediately. And what is the use of FAM for typical gui-user-application? Any example of such app that really will not properly function without gio-fam-backend? (Well, I am sure there are such and gio-fam-backend was made a dependency for glib not just for fun. But some examples would not hurt anyone.) Joe Marcus Clarke at Mon Mar 24 20:27:23 PDT 2008: > Glib 2.16 (with GIO) was designed to support pluggable file monitor > backends. Without one such backend, any libgio consumer would be > severely handicapped. The only reason gio-fam-backend is broken out > as a separate port is that we have one FAM provider that requires glib. > If this was not the case, we'd just have glib20 depend on FAM. ^^^ why glib? > Recompiling alone is not sufficient. Ports will happily build > without this backend, but may not run correctly if they require libgio. > The cost of the FAM dependency > is minimal (most GNOME apps already had this as part of gnome-vfs), ^^^ ^^^ ^^^ Well, gnome-vfs can really need FAM support. But then why not to add gio-fam-backend as a dependency to gnome-vfs instead of glib? If I understand things correctly one can install gio-fam-backend (which is pluggable module) at any point provided glib is already installed. So moving gio from glib to gnome-vfs will not only make gio-fam-backend more gnome specific but also possibly remove the hack with _glib20. > and it just makes things easier for developers not to have > to worry about adding the gio-fam-backend dependency. IMHO gio-fam-backend should not be implicit dependency. Otherwise why not to install all existing non-conflicting libraries just to ease maintainer's life :-> FWIW x11-toolkits/gtkdatabox2 (PR 116120) do not need gio-fam-backend. Just my 0.02$, Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
error building java/jdk15
I'm trying to install openoffice.org-2, and it needs jdk15 which gives
this error for me:
/usr/local/linux-sun-jdk1.4.2/bin/jar tf
../../tools/crypto/jgss/jgss_kerberos.jar sun/security/jgss/spi \
>>
/usr/ports/java/jdk15/work/control/build/bsd-i586/tmp/java/.installed.files
rm -f -r
/usr/ports/java/jdk15/work/control/build/bsd-i586/classes/sun/security/krb5
/bin/cp ../../tools/crypto/jgss/jgss_kerberos.jar
/usr/ports/java/jdk15/work/control/build/bsd-i586/classes
cd /usr/ports/java/jdk15/work/control/build/bsd-i586/classes;
/usr/local/linux-sun-jdk1.4.2/bin/jar xf jgss_kerberos.jar
sun/security/krb5
cd /usr/ports/java/jdk15/work/control/build/bsd-i586/classes; rm -f
jgss_kerberos.jar
/usr/local/linux-sun-jdk1.4.2/bin/jar tf
../../tools/crypto/jgss/jgss_kerberos.jar sun/security/krb5 \
>>
/usr/ports/java/jdk15/work/control/build/bsd-i586/tmp/java/.installed.files
rm -f /usr/ports/java/jdk15/work/control/build/bsd-i586/lib/classlist
/usr/local/linux-sun-jdk1.4.2/bin/javac -d
/usr/ports/java/jdk15/work/control/build/bsd-i586/lib -target 1.5
../../tools/sharing/AddJsum.java
javac: invalid target release: 1.5
Usage: javac
where possible options include:
-gGenerate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source}Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated
APIs are used
-classpath Specify where to find user class files
-sourcepath Specify where to find input source files
-bootclasspath Override location of bootstrap class files
-extdirsOverride location of installed extensions
-d Specify where to place generated class files
-encoding Specify character encoding used by source files
-source Provide source compatibility with specified
release
-target Generate class files for specific VM version
-help Print a synopsis of standard options
gmake[4]: ***
[/usr/ports/java/jdk15/work/control/build/bsd-i586/lib/classlist] Error 2
gmake[4]: Leaving directory
`/usr/ports/java/jdk15/work/j2se/make/java/redist'
gmake[3]: *** [optimized] Error 2
gmake[3]: Leaving directory
`/usr/ports/java/jdk15/work/j2se/make/java/redist'
gmake[2]: *** [all] Error 1
gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java'
gmake[1]: *** [all] Error 1
gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make'
gmake: *** [j2se-build] Error 2
*** Error code 2
Stop in /usr/ports/java/jdk15.
*** Error code 1
Stop in /usr/ports/java/jdk15.
*** Error code 1
Stop in /usr/ports/editors/openoffice.org-2.
I'm thinking this could be related to another java already installed on
my system?
i have:
linux-sun-jdk-1.4.2.16 Sun Java Development Kit 1.4 for Linux
diablo-jre-1.5.0.07.01_9 Java Runtime Environment 1.5.0_07.01
installed already. This is 7.0-release. Not sure what other information
is relevant, just shoot me if I should have provided more:)
/Kim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems S Tracker Resp. Description f ports/122734www/Joomla prior to 1.0.15 security issues 1 problem total. Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode f ports/108077www/linux-flashplugin9 crashes linux-firefox o ports/108413[patch] net/vnc does not works. o ports/111832ports/lang/drscheme doesn't compile: foreign.c f ports/112921x11-wm/Beryl not loading focus and keybinding settings s ports/113144print/ghostscript-gnu dumps core with several output d o ports/116378xorg 7.3 on -stable breaks math/scilab f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/116586net/isc-dhcp3-server does not work when compiled with f ports/116777The math/scilab port fails in demos->signal->bode. f ports/116778security/nmap ping-scan misses some hosts o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/118808Fix to build ports/lang/drscheme on FreeBSD-7.0 o ports/118877audio/streamripper does not detect song title from str f ports/119546net/nss_ldap makes /usr/bin/ssh dump core in getpwuid( o ports/120372java/linux-sun-jdk16: linux-sun-jre1.6.0 plugin doesn' f ports/121346building net/ekiga fails o ports/121473graphics/gsnapshot crashes upon startup on FreeBSD-6.3 f ports/121830net-mgmt/nagios-plugins: check_disk plugin works incor o ports/122030mail/listmanager needs to install listmanager with mai f ports/122083www/mod_clamav refuses to build with apache22 installe o ports/122128Class not found error during print/pdftk port installa f ports/122150devel/libusb port fails to build f ports/122187[patch] security/ipsec-tools failed build on FreeBSD 7 o ports/122251New port: graphics/sK1 An opensource vector graphics e f ports/122276Compiled audio/musicpd segfaults on FreeBSD 7.0 o ports/122306misc/compat5x port fails to extract if you're root o ports/122381net-mgmt/collectd in FreeBSD 7.0 i386 and sparc64 segf f ports/122416deskutils/kmatrix3d and deskutils/ksmoothdock don't in f ports/122540net/throttled compilation failure 32 problems total. Non-critical problems S Tracker Resp. Description o ports/85513 Intel C++ compiler not 100% binary compatible with sys o ports/95294 netpipe doesn't work on amd64 o ports/102544ltmdm driver (comms/ltmdm) crashes system whene line r o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut o ports/108795ports/icc: Proposed update to icc port for intel compi o ports/110144New port: math/Matlab7 o ports/110697New port: ports-mgmt/pkg_deps o ports/114825pam module security/pam_abl not working s ports/115216ADA devel/florist exit_process program doesn't compile s ports/115217Ada devel/florist socket program doesn't compile due t f ports/1
Building 'gvfs'
FreeBSD-6.3 I have attempted to update to 'gvfs-0.2.3_2'. I have not modified the configuration file in any way. In fact, I even ran 'make rmconfig' to insure that it was not affecting the build. However, the update continually fails. 'gvfs' claims it wants 'cdio_paranoia.0' installed. I have 'libcdio-0.78.2_1' installed with the basic configuration file. I was forced to modify the configuration file, check 'PARANOIA', and rebuild the port in order to get 'gvfs' to build. This does not seem correct. I suppose that I could have also modified the 'gvfs' configuration file; however, neither should be required to do a basic port installation. I believe the 'gvfs' port should be modified. Am I overlooking something here? -- Gerard [EMAIL PROTECTED] "Women need a reason to have sex. Men just need a place." Billy Crystal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26
Hi John, In message <[EMAIL PROTECTED] .jp>, John/SML <[EMAIL PROTECTED]> writes I tried to install the vsftpd-2.0.6 port on FreeBSD 4.11-p26, but failed with the following error message :- The ports tree has not supported FreeBSD 4 for over a year now - see the entry in /usr/ports/UPDATING of 20070205. The last version of the ports tree that supports 4.x has the RELEASE_4_EOL CVS tag; vsftpd-2.0.5 is available with that tag. Whilst you may be able to persuade individual ports to work if you apply their changes to a RELEASE_4_EOL ports tree, the ports tree infrastructure no longer works with FreeBSD 4, ports are no longer tested with FreeBSD 4, packages are not being built for FreeBSD 4 any more and anything FreeBSD 4 specific is steadily being removed from individual ports. Thinking about the ports I maintain (net/freeradius, net/freeradius-mysql and net/freeradius2), I don't believe any of them will now build on FreeBSD 4, even with a FreeBSD 4 compatible ports tree infrastructure. Certainly some FreeBSD 4 specific Makefile lines and patches have been removed. There are still reasons to be fond of FreeBSD 4 - but it is now obsolete. There were people that wanted support to continue for version 4, but there weren't the spare resources available within a volunteer project and nobody was prepared to put up the necessary money to pay for further FreeBSD 4 support. Most volunteer developers are inevitably more interested in working at or near the bleeding edge than in maintaining support for increasingly obsolete legacy versions. This means that there's no longer any security updates or security team support for FreeBSD 4 - which I would regard as a more pressing reason to upgrade from FreeBSD 4 to a supported version than there no longer being any ports tree upgrades. Of course, with an unsupported version of FreeBSD, you can't benefit from any security related upgrades to ports either. In a similar vein, FreeBSD 5 will become end of life at the end of May, and the ports tree will then be dropping FreeBSD 5 support. I suspect that there will be at most one more release of FreeBSD 6, and it's possible that 6.3-RELEASE might be the last release of FreeBSD 6. FreeBSD 6 will go end of life sooner rather than later. Unfortunately, FreeBSD 7 was a long time coming for various reasons, which means that there's a fairly big leap in code terms from 6 to 7 - but that means there's also a lot of new features and enhancements in 7. It's too difficult to keep supporting multiple different versions of FreeBSD across all the different architectures, especially when the versions are as widely different as FreeBSD 6 and 7 are in some areas. From June 1 onwards, the ports tree will still have three major versions of FreeBSD to support - 6, 7 and 8 (-CURRENT). I do confess to some relief as a mere ports maintainer in no longer having to support FreeBSD 4; it was so far removed from the FreeBSD 6 machine that I was doing the bulk of my work on. Either upgrade to a newer version of FreeBSD or, I'm afraid, you're on your own. If you're upgrading now, FreeBSD 7 is recommended; as I explained earlier, because FreeBSD 7 was a long time in coming, FreeBSD 6 is already well on in its lifecycle. If you choose to upgrade, with all the changes between FreeBSD 4 and FreeBSD 7, I suspect backing up your data and starting again with a new installation is likely to be the best way ahead. Meanwhile, there seem to be two lessons to be learnt from this list still getting questions about FreeBSD 4. Firstly, it's a reminder to everyone to read /usr/ports/UPDATING (or wherever that file resides on your machine) after updating your ports tree. Secondly, if there isn't an explicit "This version of the ports tree does not support your obsolete and unsupported version of FreeBSD. Consider upgrading to a newer version of FreeBSD." warning when support for a version of FreeBSD is removed, is it worth adding the necessary code in the future? I can see other OSVERSION related conditionals in bsd.port.mk, but not this one - though I could have missed it and it's elsewhere in the ports tree infrastructure. Best wishes, David -- David Wood [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
multimedia/mpeg4ip-libmp4v build fails
Hello. # uname -a FreeBSD incubus.bsd 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i38 # sudo make install clean ===> Vulnerability check disabled, database not found ===> Extracting for mpeg4ip-libmp4v2-1.6.1 => MD5 Checksum OK for mpeg4ip-1.6.1.tar.gz. => SHA256 Checksum OK for mpeg4ip-1.6.1.tar.gz. ===> Patching for mpeg4ip-libmp4v2-1.6.1 ===> Applying FreeBSD patches for mpeg4ip-libmp4v2-1.6.1 /usr/bin/touch -f /usr/ports/multimedia/mpeg4ip-libmp4v2/work/mpeg4ip-1.6.1/bootstrapped ===> mpeg4ip-libmp4v2-1.6.1 depends on executable: gmake - found ===> mpeg4ip-libmp4v2-1.6.1 depends on file: /usr/local/bin/libtool - found ===> Configuring for mpeg4ip-libmp4v2-1.6.1 checking for ./bootstrapped... yes checking build system type... i386-portbld-freebsd7.0 checking host system type... i386-portbld-freebsd7.0 checking target system type... i386-portbld-freebsd7.0 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... gawk checking whether gmake sets $(MAKE)... yes checking for style of include used by gmake... GNU checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... gcc3 checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all checking how to run the C preprocessor... cc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking dependency style of c++... gcc3 checking how to run the C++ preprocessor... c++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... (cached) 262144 checking command to parse /usr/bin/nm -B output from cc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... freebsd7.0 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by c++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes checking for c++ option to produce PIC... -fPIC checking if c++ PIC flag -fPIC works... yes checking if c++ static
Re: error building java/jdk15
On понеділок 14 квітень 2008, [EMAIL PROTECTED] wrote: > I'm trying to install openoffice.org-2, and it needs jdk15 which gives > this error for me: > /usr/local/linux-sun-jdk1.4.2/bin/jar tf > ../../tools/crypto/jgss/jgss_kerberos.jar sun/security/jgss/spi [...] > /usr/ports/java/jdk15/work/control/build/bsd-i586/lib -target 1.5 [...] > javac: invalid target release: 1.5 [...] It is trying to build JDK-1.5 using 1.4.2 and failing. I would've recommended installing linux-sun-jdk15, but that will not work any more either: http://www.freebsd.org/cgi/query-pr.cgi?pr=122513 You have to use diablo-jdk15 to build native JDK ports... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Mon, 14 Apr 2008 03:50:09 -0500, Alexey Shuvaev <[EMAIL PROTECTED]> wrote: IMHO gio-fam-backend should not be implicit dependency. Otherwise why not to install all existing non-conflicting libraries just to ease maintainer's life :-> FWIW x11-toolkits/gtkdatabox2 (PR 116120) do not need gio-fam-backend. Well, all ports should depend on gio-fam-backend. The gio is included and part of glib20. marcus had to split gio out of glib20 package to avoid circle dependency of glib20 -> gamin (FAM replacement) -> glib20. If marcus doesn't split and you guys will have that gio library anyway. Cheers, Mezz Just my 0.02$, Alexey. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
On Mon, 14 Apr 2008 10:09:06 -0500, Jeremy Messenger <[EMAIL PROTECTED]> wrote: On Mon, 14 Apr 2008 03:50:09 -0500, Alexey Shuvaev <[EMAIL PROTECTED]> wrote: IMHO gio-fam-backend should not be implicit dependency. Otherwise why not to install all existing non-conflicting libraries just to ease maintainer's life :-> FWIW x11-toolkits/gtkdatabox2 (PR 116120) do not need gio-fam-backend. Well, all ports should depend on gio-fam-backend. The gio is included and part of glib20. marcus had to split gio out of glib20 package to avoid circle dependency of glib20 -> gamin (FAM replacement) -> glib20. If marcus doesn't split and you guys will have that gio library anyway. Uh, I should have check in glib20 and gio-fam-backend before I made that comment. I thought that gio (libgio-2.0.so) is in gio-fam-backend, but not it's in glib20. The gio-fam-backend only installs libgiofam.so and FAM support is option in glib configure. I don't think it will be easy to make optional (maybe I am wrong) with that split. Remove gio-fam-backend dependency is going to hurt some users if they want some missing fuction(s) of it. Cheers, Mezz Just my 0.02$, Alexey. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd port: dokuwiki-devel-20070723
Hello, do you have any plans to update to the newest RC thats been released? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fprint (finger print sensor framework) port ready for testing
Hi, I did a port [2] of the fprint finger print sensor framework [1] and would like to receive some feedback before I commit it. It comes with a PAM module for finger print based authentication, a graphical (fprint_demo) and a console (pam_fprint_enroll) application for finger print enrollment. I did my tests with the UPEK sensor found in Lenovo's T61. Simon (M'fup2 ports@) [1] http://www.reactivated.net/fprint/wiki/Main_Page [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgp99PhevKfsT.pgp Description: PGP signature
Re: what is gio-fam?
Mikhail Teterin wrote: So, once again, I have to update half of my ports in order to add a new port to the system, that's happily functioning with the older version(s). Or you install sysutils/bsdadminscripts and run pkg_libchk to see which ports actually require rebuilding. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: what is gio-fam?
понеділок 14 квітень 2008 03:52 по, Dominic Fandrey Ви написали: > > So, once again, I have to update half of my ports in order to add a new > > port to the system, that's happily functioning with the older version(s). > > Or you install sysutils/bsdadminscripts and run pkg_libchk to see which > ports actually require rebuilding. NONE of them /require/ rebuilding, if I'm happy with the existing version. Yet, I'm being forced to rebuild them so that I can add another piece of software (which is also happy with the versions I already have) -- and I don't like that at all... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
Hi, On Mon, Apr 14, 2008 at 08:07:40PM +0200, Simon Barner wrote: > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. I have reviewed your ports - they look good to me :) > I did my tests with the UPEK sensor found in Lenovo's T61. I have tested the software using the UPEK TouchStrip found in my ThinkPad X60s, works like a charm. Now I just need to switch to an X display manager with PAM support ;) Thanks for working on this! Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> pgpziRPG0b5Zq.pgp Description: PGP signature
Re: what is gio-fam?
> From: Mikhail Teterin <[EMAIL PROTECTED]> > Date: Mon, 14 Apr 2008 16:18:56 -0400 > Sender: [EMAIL PROTECTED] > > понедÑлок 14 квÑÑÐµÐ½Ñ 2008 03:52 по, Dominic Fandrey Ðи > напиÑали: > > > So, once again, I have to update half of my ports in order to add a new > > > port to the system, that's happily functioning with the older version(s). > > > > Or you install sysutils/bsdadminscripts and run pkg_libchk to see which > > ports actually require rebuilding. > > NONE of them /require/ rebuilding, if I'm happy with the existing version. > Yet, I'm being forced to rebuild them so that I can add another piece of > software (which is also happy with the versions I already have) -- and I > don't like that at all... If the port existed in a version prior to the release of 2.22 (see /usr/ports/UPDATING for the date), grab the port from just before that date. if your use csup or cvsup, you can do this by editing your supfile to include a date and run csup/cvsup with the -i option. It's really is not that hard, although it is a bit of work. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpfY3zE52Mda.pgp Description: PGP signature
Re: what is gio-fam?
понеділок 14 квітень 2008 05:47 по, Kevin Oberman Ви написали: > If the port existed in a version prior to the release of 2.22 > [...] grab the port from just before that No, thanks. I want the most recent version /of the port/. And the port itself does not care, which version of GNOME it is built against -- it is happy, with /what I already have/ (earlier GNOME). Yet, I'm forced to upgrade, what I already have -- gratuicously... -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26
Hi David, Thanks for your prompt reply. Then, I think the appropriate way to keep up with port updates is to upgrade from FreeBSD 4.11 to FreeBSD 7. However, it is possible to use the "build world" method to upgrade from 4.11 to 7, or I have to use the binary upgrade method by using the FreeBSD 7 CD media. Thanks a lot. John Mok David Wood <[EMAIL PROTECTED]> 04/14/2008 09:00 PM To: John/SML <[EMAIL PROTECTED]> cc: freebsd-ports@freebsd.org Subject:Re: vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26 Hi John, In message <[EMAIL PROTECTED] .jp>, John/SML <[EMAIL PROTECTED]> writes >I tried to install the vsftpd-2.0.6 port on FreeBSD 4.11-p26, but failed >with the following error message :- The ports tree has not supported FreeBSD 4 for over a year now - see the entry in /usr/ports/UPDATING of 20070205. The last version of the ports tree that supports 4.x has the RELEASE_4_EOL CVS tag; vsftpd-2.0.5 is available with that tag. Whilst you may be able to persuade individual ports to work if you apply their changes to a RELEASE_4_EOL ports tree, the ports tree infrastructure no longer works with FreeBSD 4, ports are no longer tested with FreeBSD 4, packages are not being built for FreeBSD 4 any more and anything FreeBSD 4 specific is steadily being removed from individual ports. Thinking about the ports I maintain (net/freeradius, net/freeradius-mysql and net/freeradius2), I don't believe any of them will now build on FreeBSD 4, even with a FreeBSD 4 compatible ports tree infrastructure. Certainly some FreeBSD 4 specific Makefile lines and patches have been removed. There are still reasons to be fond of FreeBSD 4 - but it is now obsolete. There were people that wanted support to continue for version 4, but there weren't the spare resources available within a volunteer project and nobody was prepared to put up the necessary money to pay for further FreeBSD 4 support. Most volunteer developers are inevitably more interested in working at or near the bleeding edge than in maintaining support for increasingly obsolete legacy versions. This means that there's no longer any security updates or security team support for FreeBSD 4 - which I would regard as a more pressing reason to upgrade from FreeBSD 4 to a supported version than there no longer being any ports tree upgrades. Of course, with an unsupported version of FreeBSD, you can't benefit from any security related upgrades to ports either. In a similar vein, FreeBSD 5 will become end of life at the end of May, and the ports tree will then be dropping FreeBSD 5 support. I suspect that there will be at most one more release of FreeBSD 6, and it's possible that 6.3-RELEASE might be the last release of FreeBSD 6. FreeBSD 6 will go end of life sooner rather than later. Unfortunately, FreeBSD 7 was a long time coming for various reasons, which means that there's a fairly big leap in code terms from 6 to 7 - but that means there's also a lot of new features and enhancements in 7. It's too difficult to keep supporting multiple different versions of FreeBSD across all the different architectures, especially when the versions are as widely different as FreeBSD 6 and 7 are in some areas. From June 1 onwards, the ports tree will still have three major versions of FreeBSD to support - 6, 7 and 8 (-CURRENT). I do confess to some relief as a mere ports maintainer in no longer having to support FreeBSD 4; it was so far removed from the FreeBSD 6 machine that I was doing the bulk of my work on. Either upgrade to a newer version of FreeBSD or, I'm afraid, you're on your own. If you're upgrading now, FreeBSD 7 is recommended; as I explained earlier, because FreeBSD 7 was a long time in coming, FreeBSD 6 is already well on in its lifecycle. If you choose to upgrade, with all the changes between FreeBSD 4 and FreeBSD 7, I suspect backing up your data and starting again with a new installation is likely to be the best way ahead. Meanwhile, there seem to be two lessons to be learnt from this list still getting questions about FreeBSD 4. Firstly, it's a reminder to everyone to read /usr/ports/UPDATING (or wherever that file resides on your machine) after updating your ports tree. Secondly, if there isn't an explicit "This version of the ports tree does not support your obsolete and unsupported version of FreeBSD. Consider upgrading to a newer version of FreeBSD." warning when support for a version of FreeBSD is removed, is it worth adding the necessary code in the future? I can see other OSVERSION related conditionals in bsd.port.mk, but not this one - though I could have missed it and it's elsewhere in the ports tree infrastructure. Best wishes, David -- David Wood [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any m
Re: lsof 4.79K build fails
Larry Rosenman wrote: On Mon, 14 Apr 2008, Ganbold wrote: Jonathan Chen wrote: On Mon, Apr 14, 2008 at 09:51:17AM +0800, Rong-en Fan wrote: On Mon, Apr 14, 2008 at 9:47 AM, Jonathan Chen <[EMAIL PROTECTED]> wrote: On Mon, Apr 14, 2008 at 09:36:36AM +0800, Rong-en Fan wrote: > On Mon, Apr 14, 2008 at 7:58 AM, Jonathan Chen <[EMAIL PROTECTED]> wrote: > > The latest update for sysutils/lsof to 4.79K ends in the following > > when building on 7_STABLE: > > > > cc -fno-strict-aliasing -pipe -DHASEFFNLINK=i_effnlink -DHASF_VNODE > > -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 > > -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DHAS_ZFS > > -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 > > -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-STABLE\" -I/usr/src/sys -O2 -c > > dnode.c > > dnode.c: In function 'get_lock_state': > > dnode.c:113: error: 'struct lockf' has no member named 'lf_flags' > > dnode.c:115: error: 'struct lockf' has no member named 'lf_id' > > dnode.c:121: error: 'struct lockf' has no member named 'lf_id' > > dnode.c:129: error: 'struct lockf' has no member named 'lf_start' > > dnode.c:130: error: 'struct lockf' has no member named 'lf_end' > > dnode.c:134: error: 'struct lockf' has no member named 'lf_type' > > dnode.c:136: error: 'struct lockf' has no member named 'lf_type' > > dnode.c:138: error: 'struct lockf' has no member named 'lf_type' > > dnode.c:141: error: 'struct lockf' has no member named 'lf_next' > > *** Error code 1 > > > > Stop in /usr/ports/sysutils/lsof/work/lsof_4.79K.freebsd. > > When is your RELENG_7 updated? It builds fine on my 7-STABLE (around Mar > 29) amd64. # uname -v FreeBSD 7.0-STABLE #0: Thu Feb 28 15:34:42 NZDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JONC what arch? i386 I tried yesterday and day before yesterday to upgrade my ports and latest lsof port doesn't build on FreeBSD-7.0-STABLE (built April 12, 2008) with similar errors if I'm not mistaken. Did you get the 4.79K version? If not, and you have a very recent RELENG_7, it should build. I've asked Vic Abell to look into these reports. (I've updated both of my amd64/RELENG_7's to this weekends sources and lsof builds fine). There might be issues with earlier, but I'm not sure. As I said, I've asked Vic Abell to look into it. Thanks for the reports. lsof-4.79K compiles fine here. Ganbold LER Ganbold -- You think Oedipus had a problem -- Adam was Eve's mother. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lsof 4.79K build fails
Ganbold writes: > lsof-4.79K compiles fine here. Still getting: cc -pipe -g -march=pentium4 -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-CURRENT\" -I/usr/src/sys -O -c dmnt.c cc -pipe -g -march=pentium4 -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-CURRENT\" -I/usr/src/sys -O -c dnode.c dnode.c: In function 'get_lock_state': dnode.c:113: error: 'struct lockf' has no member named 'lf_flags' dnode.c:115: error: 'struct lockf' has no member named 'lf_id' dnode.c:121: error: 'struct lockf' has no member named 'lf_id' dnode.c:129: error: 'struct lockf' has no member named 'lf_start' dnode.c:130: error: 'struct lockf' has no member named 'lf_end' dnode.c:134: error: 'struct lockf' has no member named 'lf_type' dnode.c:136: error: 'struct lockf' has no member named 'lf_type' dnode.c:138: error: 'struct lockf' has no member named 'lf_type' dnode.c:141: error: 'struct lockf' has no member named 'lf_next' *** Error code 1 Stop in /usr/ports/sysutils/lsof/work/lsof_4.79K.freebsd. *** Error code 1 on: FreeBSD 7.0-CURRENT #0: Tue Mar 18 20:52:53 EDT 2008 i386 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: lsof 4.79K build fails
There's a PR pending with the update to 4.79L which bullet-proof's it some. Upgrading your system to a more recent RELENG_7 will fix it as well. Thanks. Larry Rosenman Sysutils/lsof maintainer. -Original Message- From: Robert Huff [mailto:[EMAIL PROTECTED] Sent: Monday, April 14, 2008 8:48 PM To: Ganbold Cc: Larry Rosenman; Rong-en Fan; Jonathan Chen; freebsd-ports@freebsd.org Subject: Re: lsof 4.79K build fails Ganbold writes: > lsof-4.79K compiles fine here. Still getting: cc -pipe -g -march=pentium4 -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-CURRENT\" -I/usr/src/sys -O -c dmnt.c cc -pipe -g -march=pentium4 -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHASCPUMASK_T -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_NO_SI_UDEV -DHAS_SI_PRIV -DHAS_SYS_SX_H -DFREEBSDV=7000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHAS_STRFTIME -DLSOF_VSTR=\"7.0-CURRENT\" -I/usr/src/sys -O -c dnode.c dnode.c: In function 'get_lock_state': dnode.c:113: error: 'struct lockf' has no member named 'lf_flags' dnode.c:115: error: 'struct lockf' has no member named 'lf_id' dnode.c:121: error: 'struct lockf' has no member named 'lf_id' dnode.c:129: error: 'struct lockf' has no member named 'lf_start' dnode.c:130: error: 'struct lockf' has no member named 'lf_end' dnode.c:134: error: 'struct lockf' has no member named 'lf_type' dnode.c:136: error: 'struct lockf' has no member named 'lf_type' dnode.c:138: error: 'struct lockf' has no member named 'lf_type' dnode.c:141: error: 'struct lockf' has no member named 'lf_next' *** Error code 1 Stop in /usr/ports/sysutils/lsof/work/lsof_4.79K.freebsd. *** Error code 1 on: FreeBSD 7.0-CURRENT #0: Tue Mar 18 20:52:53 EDT 2008 i386 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vsftpd-2.0.6 failed to compile on FreeBSD-4.11-p26
On Tue, Apr 15, 2008 at 09:24:43AM +0800, John/SML wrote: > Then, I think the appropriate way to keep up with port updates is to > upgrade from FreeBSD 4.11 to FreeBSD 7. However, it is possible to use the > "build world" method to upgrade from 4.11 to 7, or I have to use the > binary upgrade method by using the FreeBSD 7 CD media. If you're using the source upgrade, you're probably going to have to do something like: update to 5.2; update to 5.3; update to 6.0; update to 7.0. You're facing an upgrade that takes you through literally years of technology. Although there are postings I've seen on the mailing lists where people have managed it, this is going to be a difficult task. In particular, you will need to pay attention to the various src/UPDATING files over this span of time. If at all possible, please consider doing a reinstall. You will probably save yourself considerable time in the end. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
www/links port fails to build with DirectFB library
To whom it might concern,
I've started a rebuild of all ports, on my home system, and links
port failed, with the libdirectfb. I have fixed it -- the dependancy
line with the "libdirectfb" entry should be changed to "directfb".
Line 51 (as of my last portsnap fetch; portsnap update, a few minutes
ago) of /usr/ports/www/links/Makefile should read:
LIB_DEPENDS+= directfb:${PORTSDIR}/devel/directfb
Instead it reads:
LIB_DEPENDS+= libdirectfb:${PORTSDIR}/devel/directfb
Hopefully this hasn't affected too many people, and hopefully I'm not
pestering the wrong people.
Regards,
--
ADAM David Alan Martin
Filesystem and Storage Lab, SUNY Stony Brook
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fprint (finger print sensor framework) port ready for testing
Sam Leffler wrote: > Does it still use the i386 binary module? I need a 64-bit module. No, there no binary modules at all (fully build from source). I did not test it in 64-bit environment, so your experience report would be interesting. (Cc:'d ports@) -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgpuuNan8OKOf.pgp Description: PGP signature
