Re: Monitoring a switch
On Jan 8, 2013, at 10:30 AM, Andrea Venturoli wrote: I'm looking for some software which can monitor a SNMP-enabled switch. Well, it's likely that the switch vendor offers some tools. Sure I can use Cacti to monitor bandwidth of every single port... or Nagios to warn me if some port gets some defined amount of traffic for a defined amount of time... Yes, those are reasonable starting points. I was wondering though, if there was some more specific tool which might be faster to setup and would do some magic automatically, like computing the total traffic flowing through, identifying bottlenecks, etc... Sure. What's your budget? Something like HP's OpenView (which I just learned was rebranded to HP Network Management Center), or Cisco's LAN Management stuff (evidently also rebranded) do all sorts of nice network discovery and autoconfig, routing/traffic bottleneck analysis, etc. They also cost 5 to 6-digit sums, but if you've got multiple WAN links between data centers to manage, or some complicated VM/cloud architecture, they're probably worth the price. (Of course, if you've just got a meaning one switch to manage, that would be overkill.) Regards, -- -Chuck ___ 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: BUILD_DEPENDS= RUN_DEPENDS=
On May 14, 2012, at 4:13 PM, Bryan Drewery wrote: I was trying to append to these in my /etc/make.conf and found that a large (thousands) number of ports are using = instead of +=, thus destroying any user-supplied depends. Yes. I think this may even be intentional on the part of the various port maintainers, but the notion of user-supplied additional dependencies is interesting. :-) The use case for wanting to do this is to force devel/ccache to be a build dependency on all ports, for package building. Or to force in a particular library along with LDFLAGS into particular ports. This is achievable by modifying bsd.local.mk, but is not ideal. Why do you need ccache added to the build dependencies to use it? Can't you just change CC/C++? This goes along with updating all CLFAGS/LDFLAGS to use += instead of =. For most cases, sure, I would agree that CFLAGS/LDFLAGS should use +=. Regards, -- -Chuck ___ 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: Need a little help with a dynamic linking problem
On Apr 25, 2012, at 5:01 PM, Ronald F. Guilmette wrote: When I try to run the gthumb binary that I built and install, I am getting the following perplexing error message: /libexec/ld-elf.so.1: /usr/local/hacked/lib/gthumb/extensions/libfile_viewer.so: Undefined symbol gth_viewer_page_get_type Does running ldconfig /usr/local/hacked/lib help? What does ldd say about things? Regards, -- -Chuck ___ 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: FreeBSD Port: samba34-3.4.14
On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? Don't know-- I don't recall having a build of Samba fail for me any time recently, but if you can confirm that a specific option causes the build failure, that would help reproduce. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... Regards, -- -Chuck ___ 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: FreeBSD Port: samba34-3.4.14
Hi-- On Apr 9, 2012, at 4:01 PM, Da Rock wrote: To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Regards, -- -Chuck ___ 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: phpmyadmin port files errors
On 4/3/2012 3:14 PM, Fbsd8 wrote: Just downloaded phpmyadmin for 9.0 system. The port files seem to be named wrong. Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v You downloaded the CVS repository instead of doing a checkout. If you were using cvsup, switch to checkout mode instead of CVS mode: http://www.gsp.com/cgi-bin/man.cgi?section=1topic=cvsup#5 Regards, -- -Chuck ___ 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: dl library and fdatasync(2)
On Feb 24, 2012, at 10:40 AM, Norman Khine wrote: i am trying to build nodejs on freebsd9, and get a warning: Checking for library dl : not found Checking for fdatasync(2) with c++ : no could someone point me where these libraries are? FreeBSD's libc provides dlopen(), dlclose(), etc-- there's no need for a separate libdl to do dynamic loading. fdatasync(2) is a cheaper version of fsync(2) which does not try to update filesystem metadata; using soft updates with FreeBSD's UFS2 filesystem already provides most of the benefits. So you don't need that either, just call fsync() instead. Regards, -- -Chuck ___ 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: Minor changes to bsd.port.mk and bsd.pkgng.mk
On Feb 24, 2012, at 2:35 PM, Cejka Rudolf wrote:
I'm sorry - all three lines with ${TR} have to be changed to
+defaultval=$$(${ECHO_CMD} $$3 | ${TR} [A-Z] [a-z]); \
so that one letter files in ports directories
do not break functionality.
For your next update, please use [:upper:] and [:lower:] character classes.
This works with languages with diacritical marks and so forth...
Regards,
--
-Chuck
___
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: pkgng support for tinderbox
On Feb 15, 2012, at 3:04 PM, Doug Barton wrote: On 02/15/2012 14:27, George Liaskos wrote: Thank you for the great work, pkg-updating.1 should be added in the MAN1 because pkg is currently falling under tinderbox. Shouldn't stuff like updating packages be in sbin man section 8? Comparing intro.1 to intro.8: Section one of the manual contains most of the commands which comprise the BSD user environment. Some of the commands included in section one are text editors, command shell interpreters, searching and sorting tools, file manipulation commands, system status commands, remote file copy commands, mail commands, compilers and compiler tools, formatted output tools, and line printer commands. - This section contains information related to system operation and maintenance. It describes commands used to create new file systems (newfs(8)), verify the integrity of the file systems (fsck(8)), control disk usage (edquota(8)), maintain system backups (dump(8)), and recover files when disks die an untimely death (restore(8)). Network related services like inetd(8) and ftpd(8) are also described. Well, yes, I suppose you could make a case for section 8, but it's not a perfect fit, especially if you consider packages/ports to be external to the FreeBSD operating system itself. Regards, -- -Chuck ___ 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: isc dhcp does not make
Hi-- On Jan 25, 2012, at 5:07 PM, Randy Bush wrote: all the other ports made just fine, as did that test, of course. reported to isc configure:2703: cc -O2 -pipe -march=i686 -fPIC -fno-strict-aliasing -D_PATH_DHCLIENT_SCRIPT='/usr/local/sbin/dhclient-script' -D_PATH_DHCLIENT_CONF='/usr/local/etc/dhclient.conf' -D_PATH_DHCPD_CONF='/usr/local/etc/dhcpd.conf' conftest.c 5 conftest.c:1: error: CPU you selected does not support x86-64 instruction set configure:2706: $? = 1 You've specified a 32-bit CPU architecture, but are running on a 64-bit (aka AMD64/EM64T) platform. Get rid of the -march flag from /etc/make.conf or where-ever it is coming from. Regards, -- -Chuck ___ 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: isc dhcp does not make
On Jan 25, 2012, at 4:38 PM, Randy Bush wrote:
checking for gcc... cc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
=== Script configure failed unexpectedly.
Please report the problem to z...@freebsd.org [maintainer] and attach the
/usr/ports/net/isc-dhcp42-server/work/dhcp-4.2.3-P2/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. an `ls
/var/db/pkg`).
*** Error code 1
clang?
The instructions given suggest looking at:
/usr/ports/net/isc-dhcp42-server/work/dhcp-4.2.3-P2/config.log
It's likely to be informative. Failing that, a basic sanity check:
echo 'int main() { return 0; }' test.c
cc -o test test.c
./test echo 'OK' || echo 'bad'
Regards,
--
-Chuck
___
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: xcb-util
On Jan 16, 2012, at 2:51 PM, ajtiM wrote: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Why do you need to reinstall? Regards, -- -Chuck ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On Jan 9, 2012, at 2:28 PM, Paul Schmehl wrote: My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? rpm -Va (or rpm --verify --all) ought to consult an MD5 checksum to identify changes for all installed packages... Regards, -- -Chuck ___ 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 vs packages
On Jan 9, 2012, at 2:00 PM, alexus wrote: One of the things I'm seeing is that unfortunately packages are somewhat limited vs ports... Packages come precompiled with default options. For people who want non-default options, you would need to build your own package from ports rather than using the precompiled one. For example: I'm trying to get Apache httpd + PHP to work, after pkg_add -r php5, php5 doesn't have libphp5.so that links Apache and PHP together... so unless I'm doing something entirely wrong I basically must use ports and nothing else to get the functionality i need... You can use ports and packages together just fine. In particular, you ought to be able to use the Apache-2.x package with a php5 port that you build to enable mod_php. Regards, -- -Chuck ___ 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: clang and configure checking for equivalent simple type
Hi--
On Sep 28, 2011, at 9:58 PM, Klaus T. Aehlig wrote:
However, I assume that these kind of tests are quite widespread in configure
scripts, so I wonder what to do about this. Possible options include
- adding 'CFLAGS+= -Wno-unused' just for this port
- do nothing, but recommend users to have -Wno-unused in CFLAGS when using
clang
(maybe somewhere in the handbook)
- check with portmgr@ if adding -Wno-unused to the default CFLAGS (for clang?)
is an option
- something completely different??
(like: add an appropriate entry to my /etc/make.conf and don't care)
Any suggestions?
Are you sure that you don't have -Werror being set somehow? I don't have a
FreeBSD-9 system handy at the moment, but that code ought to compile under
clang (with warnings, sure, but the result runs):
% clang -o t t.c
t.c:6:20: warning: comparison of distinct pointer types ('off_t *' (aka 'long
long *') and 'long *')
off_t u; long v; u==v;
~~^ ~~
t.c:6:20: warning: expression result unused [-Wunused-value]
off_t u; long v; u==v;
~~^ ~~
2 warnings generated.
% ./t ; echo $?
0
% clang --version
Apple clang version 2.0 (tags/Apple/clang-137) (based on LLVM 2.9svn)
Regards,
--
-Chuck
___
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: HEADS UP: ports/ and 10.0-CURRENT
Hi-- On Sep 27, 2011, at 11:50 AM, Gleb Kurtsou wrote: It's more exciting than that. FreeBSD = 10 is already seized by Apple :) http://www.google.com/codesearch#search/q=__FreeBSD__%5CW%2B10type=cs MacOS X doesn't define __FreeBSD__ either in CPP macros or the system headers: % touch foo.h; cpp -dM foo.h | grep __FreeBSD__ % cpp --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Regards, -- -Chuck ___ 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: Postfix - Dovecot SASL problem
Hi-- On Aug 18, 2011, at 2:38 PM, Petr Holub wrote: smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. You need to setup CRAM-MD5 or maybe GSSAPI, or else permit plaintext auth mechanisms if the connection is coming via TLS/SSL: http://wiki2.dovecot.org/HowTo/CRAM-MD5 Also see: http://www.postfix.org/postconf.5.html Warning: it appears that clients try authentication methods in the order as advertised by the server (e.g., PLAIN ANONYMOUS CRAM-MD5) which means that if you disable plaintext passwords, clients will log in anonymously, even when they should be able to use CRAM-MD5. So, if you disable plaintext logins, disable anonymous logins too. Postfix treats anonymous login as no authentication. Regards, -- -Chuck ___ 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: Postfix - Dovecot SASL problem
On Aug 18, 2011, at 4:25 PM, Sahil Tandon wrote: From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. His dovecot configuration also appears to be offering the PLAIN plaintext auth mechanism; not just LOGIN. Yes, that's right-- but they're both plaintext, which Postfix was configured not to allow... Regards, -- -Chuck ___ 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: Time to mark portupgrade deprecated?
On Jul 30, 2011, at 4:03 AM, Michel Talon wrote: [ ... ] The real problems are in the ports system itself. You've said this before. Come to think of it, you've said this so often that I've lost count of the number of times you've repeated the point. However, flogging the same dead horse over and over does not constitute forward progress. Speaking of which, if you'd spent some of this time filing bug reports instead, then it's very likely that at least some of the issues you claim to keep running into would be fixed by now. However, as far as I can tell from a quick search, you've never filed even one FreeBSD PR? Methinks 'tis time to change your approach: The clock upbraids me with the waste of time. Regards, -- -Chuck ___ 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: Which to bump for distfile location change?
On Jul 26, 2011, at 12:47 PM, Bob Eager wrote: Following a recent post to this list, I need to update a port, just to change a distfile location. It seems excessive to bump PORTREVISION, so what is the best thing to change (if any). Probably nothing-- if someone already has a copy of the distfile, and there are no other changes, then there is no need to force them to rebuild the port by bumping PORTREVISION. Regards, -- -Chuck ___ 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: [ANNOUNCE]: clang compiling ports, take 2
Hi--
On Jul 25, 2011, at 4:31 PM, Raphael Kubo da Costa wrote:
http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/
qt4-webkit seems to trigger a clang bug, but the description for clang
bug only says See (TBA) for further information. Is there anything we
(as in kde@) should do?
From:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/qt4-webkit-4.7.3.log
Clang is failing with an internal assertion failure, seems like it's not
parsing something correctly in RenderSlider.cpp, and hitting EOF:
Assertion failed: (FieldNo FieldCount Invalid Field No), function
getFieldOffset, file
/a/portbuild/amd64/9-exp/builds/20110616185105/src/lib/clang/libclangast/../../../contrib/llvm/tools/clang/include/clang/AST/RecordLayout.h,
line 121.
Stack dump:
0. Program arguments: /usr/bin/clang++ -cc1 -triple
x86_64-unknown-freebsd9.0 -emit-obj -disable-free -main-file-name
RenderSlider.cpp -pic-level 2 -mdisable-fp-elim -relaxed-aliasing -masm-verbose
-mconstructor-aliases -munwind-tables -target-cpu x86-64
-momit-leaf-frame-pointer -coverage-file .obj/release-shared/RenderSlider.o
-resource-dir /usr/bin/../lib/clang/3.0 -D QT_SHARED -D BUILDING_QT__=1 -D
WTF_USE_ACCELERATED_COMPOSITING -D NDEBUG -D QT_NO_CAST_TO_ASCII -D
QT_ASCII_CAST_WARNINGS -D QT3_SUPPORT -D QT_MOC_COMPAT -D
QT_USE_FAST_OPERATOR_PLUS -D QT_USE_FAST_CONCATENATION -D HAVE_PTHREAD_NP_H -D
BUILD_WEBKIT -D BUILDING_QT__ -D BUILDING_JavaScriptCore -D BUILDING_WTF -D
ENABLE_VIDEO=1 -D ENABLE_JAVASCRIPT_DEBUGGER=1 -D ENABLE_DATABASE=1 -D
ENABLE_EVENTSOURCE=1 -D ENABLE_OFFLINE_WEB_APPLICATIONS=1 -D
ENABLE_DOM_STORAGE=1 -D ENABLE_ICONDATABASE=1 -D ENABLE_CHANNEL_MESSAGING=1 -D
ENABLE_ORIENTATION_EVENTS=0 -D ENABLE_SQLITE=1 -D ENABLE_DASHBOARD_SUPPORT=0 -D
ENABLE_FILTERS=1 -D ENABLE_XPATH=1 -D ENABLE_WCSS=0 -D ENABLE_WML=0 -D
ENABLE_SHARED_WORKERS=1 -D ENABLE_WORKERS=1 -D ENABLE_XHTMLMP=0 -D
ENABLE_DATAGRID=0 -D ENABLE_RUBY=1 -D ENABLE_SANDBOX=1 -D ENABLE_PROGRESS_TAG=1
-D ENABLE_BLOB_SLICE=0 -D ENABLE_3D_RENDERING=1 -D ENABLE_SVG=1 -D
ENABLE_SVG_FONTS=1 -D ENABLE_SVG_FOREIGN_OBJECT=1 -D ENABLE_SVG_ANIMATION=1 -D
ENABLE_SVG_AS_IMAGE=1 -D ENABLE_SVG_USE=1 -D ENABLE_DATALIST=1 -D
ENABLE_TILED_BACKING_STORE=1 -D ENABLE_NETSCAPE_PLUGIN_API=1 -D
ENABLE_WEB_SOCKETS=1 -D ENABLE_XSLT=0 -D ENABLE_QT_BEARER=1 -D
ENABLE_TOUCH_EVENTS=1 -D XP_UNIX -D SQLITE_CORE -D SQLITE_OMIT_LOAD_EXTENSION
-D SQLITE_OMIT_COMPLETE -D QT_NO_DEBUG -D QT_GUI_LIB -D QT_NETWORK_LIB -D
QT_CORE_LIB -D QT_HAVE_AVX -D _LARGEFILE64_SOURCE -D _LARGEFILE_SOURCE -I
../../../../include/Qt -I ../../../../include -I /usr/local/include/freetype2
-I /usr/local/share/qt4/mkspecs/freebsd-clang -I . -I
../../../../include/QtCore -I ../../../../include/QtNetwork -I
../../../../include/QtGui -I ../../../../include -I bridge/qt -I page/qt -I
platform/graphics/qt -I platform/network/qt -I platform/qt -I ../WebKit/qt/Api
-I ../WebKit/qt/WebCoreSupport -I . -I accessibility -I bindings/js -I bridge
-I bridge/c -I bridge/jsc -I css -I dom -I dom/default -I editing -I history -I
html -I html/canvas -I inspector -I loader -I loader/appcache -I loader/archive
-I loader/icon -I notifications -I page -I page/animation -I platform -I
platform/animation -I platform/graphics -I platform/graphics/filters -I
platform/graphics/transforms -I platform/image-decoders -I platform/mock -I
platform/network -I platform/sql -I platform/text -I plugins -I rendering -I
rendering/style -I storage -I svg -I svg/animation -I svg/graphics -I
svg/graphics/filters -I websockets -I wml -I workers -I xml -I generated -I
../JavaScriptCore -I ../../webkit -I ../JavaScriptCore/assembler -I
../JavaScriptCore/bytecode -I ../JavaScriptCore/bytecompiler -I
../JavaScriptCore/debugger -I ../JavaScriptCore/interpreter -I
../JavaScriptCore/jit -I ../JavaScriptCore/parser -I ../JavaScriptCore/pcre -I
../JavaScriptCore/profiler -I ../JavaScriptCore/runtime -I
../JavaScriptCore/wtf -I ../JavaScriptCore/wtf/symbian -I
../JavaScriptCore/wtf/unicode -I ../JavaScriptCore/yarr -I
../JavaScriptCore/API -I ../JavaScriptCore/ForwardingHeaders -I
../JavaScriptCore/generated -I ../include/QtWebKit -I
../../../../include/QtWebKit -I .rcc/release-shared -I ../../sqlite -I
../../../../include/phonon -I /usr/local/include -I .moc/release-shared -I
/usr/local/include -O2 -Wall -W -fdeprecated-macro -ferror-limit 19
-fmessage-length 0 -fvisibility hidden -fvisibility-inlines-hidden
-fcxx-exceptions -fexceptions -fdiagnostics-show-option -o
.obj/release-shared/RenderSlider.o -x c++ rendering/RenderSlider.cpp
1. eof parser at end of file
2. rendering/RenderSlider.cpp:43:11: LLVM IR generation of declaration
'WebCore'
3. rendering/RenderSlider.cpp:81:26: Generating code for declaration
'WebCore::SliderThumbElement::defaultEventHandler'
4. rendering/RenderSlider.cpp:82:1: LLVM IR generation of compound
statement ('{}')
In file
Re: [ANNOUNCE]: clang compiling ports
On Jun 20, 2011, at 9:35 AM, Stephen Montgomery-Smith wrote: What I would like is a primer on how to suppress all the warnings and errors created by KR code. OK: http://clang.llvm.org/docs/UsersManual.html#cl_diagnostics Of course, you can only suppress warnings; you cannot suppress actual errors. clang doesn't currently support -traditional aka pure KR C. It's possible that compiling with -ansi aka -std=c89 might help-- at least you should get -Wno-implicit-function-declaration and maybe -Wno-implicit-int. Also, why is this an error: error: non-void function 'top_button_cross' should return a value [-Wreturn-type] when most everything else is a warning. (See http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/xppaut-5.99.log.) top_button_cross() probably should be declared as returning void. What's presumably happening is that it gets a default return type of int since it doesn't otherwise specify a return type, and then fails to have an explicit return, which is an error. Regards, -- -Chuck ___ 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: [ANNOUNCE]: clang compiling ports
On Jun 20, 2011, at 12:09 PM, Stephen Montgomery-Smith wrote: top_button_cross() probably should be declared as returning void. What's presumably happening is that it gets a default return type of int since it doesn't otherwise specify a return type, and then fails to have an explicit return, which is an error. Is a return with no value, from a function of type int, meant to be an error in KR code? I don't believe so, but pure KR didn't require compilers to perform any sanity checking of function return types. This led to all sorts of bugs, which is why lint was invented and why ANSI-C compilers do expect function prototypes and perform function return-type checking. If so, I will change the code so that return becomes return 0. Otherwise, I think the clang compiler should be changed so that this is a warning, not an error. Or at least an error that can be switched off with -Wno-return-type. I will say that I have no desire to put ansii patches into working KR code. It sounds like you want Clang to support -traditional. It explicitly does not do so, although there is a bug filed as: http://llvm.org/bugs/show_bug.cgi?id=4557 The best course is to convert KR C code to C89/ANSI; failing that, perhaps use gcc for things which require -traditional instead of Clang (although GCC seems to be depreciating -traditional also). Regards, -- -Chuck ___ 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: Mailman + postfix -- which group have people selected?
On Jun 14, 2011, at 11:43 AM, Chris Rees wrote: Before I revert the MAIL_GID=nobody change (I have had private mail explaining that it is in fact incorrect), does anyone have any more information on which value is more correct, and why one is preferable? Basically, Postfix will deliver to the owner of Mailman's alias file. So long as that is owned by mailman user, and so long as the mailman user has the mailman group as it's primary GID, then running with --with-mail-gid=mailman is correct. You'll probably find Mailman's documentation helpful: http://wiki.list.org/display/DOC/Understanding+group+mismatch+errors+-+how+mailman+implements+security http://www.seaglass.com/postfix/mailman-gid.html Regards, -- -Chuck ___ 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: ${CD}
On May 24, 2011, at 12:39 PM, Helmut Schneider wrote:
I need 'cd' in my Makefile. It seems that the variable ${CD} is not
defined and people are using 'cd' instead.
Is there a certain reason for that?
make isn't the same as a shell; while you can do shell one-liners starting with
a 'cd' if you have to, they won't have any effect on subsequent Makefile
statements. Consider using VPATH to find sources instead.
Regards,
--
-Chuck
___
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 make -j be used for ports?
On Mar 15, 2011, at 3:35 PM, Eitan Adler wrote:
[ ... ]
Yes. Ports which support parallel builds will have MAKE_JOBS_SAFE=yes set
in the port Makefile. It defaults to running -j with
MAKE_JOBS_NUMBER=`${SYSCTL} -n kern.smp.cpus`, but you can change that to
some other # if you like.
No, this is incorrect. The MAKE_JOBS_NUMBER and MAKE_JOBS_SAFE is used
internally when building a single port.
What is incorrect?
When the OP is asking if he can manually specify -j on the command line which
would end up
building multiple ports in parallel. This can not be done (primarily
because there is no locking done on ports)
It certainly wasn't clear to me that this is what the OP meant. If you:
cd /usr/ports/www/apache22
make -j 3
...what do you expect to happen, and how many ports would you expect to be
built at once?
(Building one port in parallel is supported, where the port itself is safe to
do so; building many at the same time is not. Supporting the former provides
more speed gain for many situations as compared to the latter; which doesn't
help at all if you are just installing or updating one port.)
Regards,
--
-Chuck
___
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 make -j be used for ports?
On Mar 15, 2011, at 3:51 PM, Eitan Adler wrote: It certainly wasn't clear to me that this is what the OP meant. If you: cd /usr/ports/www/apache22 make -j 3 ...what do you expect to happen, and how many ports would you expect to be built at once? What *would* happen is that make would try to build multiple ports at once. Did you actually try and see what happens? I'm thinking no...since, unless something is very different, you ought to find it terminating as follows: # cd /usr/ports/www/apache22 ; make -j 3 === apache-2.2.17_1 depends on file: /usr/local/lib/libcrypto.so.7 - found === apache-2.2.17_1 depends on file: /usr/local/bin/perl5.12.3 - found === apache-2.2.17_1 depends on file: /usr/local/bin/autoconf-2.68 - found === apache-2.2.17_1 depends on package: libtool=2.4 - found === apache-2.2.17_1 depends on shared library: expat.6 - found === apache-2.2.17_1 depends on shared library: apr-1 - found === apache-2.2.17_1 depends on shared library: pcre.0 - found === apache-2.2.17_1 depends on shared library: iconv.3 - found === apache-2.2.17_1 depends on shared library: mysqlclient.15 - found === apache-2.2.17_1 depends on shared library: db-4.4.0 - found === apache-2.2.17_1 depends on shared library: sqlite3.8 - found === Configuring for apache-2.2.17_1 ...whereas just typing make proceeds with: checking for chosen layout... FreeBSD checking for working mkdir -p... yes checking build system type... i386-portbld-freebsd7.4 checking host system type... i386-portbld-freebsd7.4 checking target system type... i386-portbld-freebsd7.4 [ ...followed by an actual build... ] Regards, -- -Chuck ___ 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 make -j be used for ports?
On Mar 15, 2011, at 7:38 PM, John wrote: 1. If I can speed things up, with *ports* as I have a dual cpu, I want to maybe run j2 or j3. I seek clarification which is logically best, because some literature says jn, others jn+1 where n is number of cores. kern.smp.cpus: 2 on my machine. Is there benefit setting this to 3,4,5? If you have plenty of RAM, then setting it somewhat higher than #CPUs is likely to improve performance. Frankly, it's best if you measure things on your own machine against the software you care about building, and decide for yourself whether the difference matters. :-) I want to know if there is perhaps a conf file or sysctl where I can specify this *for ports only.* - if not I'm happy to specify on the command line. It's just that the manual is a tad unclear about this. Setting MAKE_JOBS_NUMBER in /etc/make.conf will only apply to things using the bsd.ports.mk Makefile, unless they've chosen to honor the same variable independently. In other words, you're unlikely to hurt things much by setting it to some reasonable value. Obtain some data and let us know if you run into surprises... Regards, -- -Chuck ___ 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: New member for portmgr@
On Mar 10, 2011, at 1:17 PM, Thomas Abthorpe wrote: Just wanted to say that I have been made a voting member of portmgr@ http://blogs.freebsdish.org/portmgr/2011/03/10/new-member-for-portmgr/ Congratulations. (What is the reward for doing some work, but even *more* work...? :-) Regards, -- -Chuck ___ 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: FreeBSD Port: mysql-server-5.5.9
On Mar 10, 2011, at 11:37 AM, joeb wrote: FATAL ERROR: Could not find ./bin/my_print_defaults Does running rehash in your shell help it find the binary? Or does using --basedir /usr/local/bin help? Regards, -- -Chuck ___ 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: Gajim does not starts
On Feb 22, 2011, at 1:27 PM, David Demelier wrote: markand@Melon ~ $ gajim ** Message: pygobject_register_sinkfunc is deprecated (GstObject) nslookup: not found I know this is a very useful message, but I can't help more. Are you expecting the same behavior ? nslookup has been deprecated, also, but you can get a binary if you install /usr/ports/dns/bind96 or later version of BIND. Regards, -- -Chuck ___ 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: how to bootstrap libtool?
On Feb 9, 2011, at 10:06 AM, Michael Scheidell wrote: I can (and do) have libnet11 as a dependency, but by then, its too late. do I need to run makefile TWICE? what does this do to nightly package builds? how do I bootstrap it to install libnet11 EARLY if its not there? You should list libnet11 as both BUILD_DEPENDS and RUN_DEPENDS, likely... Regards, -- -Chuck ___ 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: how to bootstrap libtool?
On Feb 9, 2011, at 10:35 AM, Michael Scheidell wrote: On 2/9/11 1:32 PM, Chuck Swiger wrote: You should list libnet11 as both BUILD_DEPENDS and RUN_DEPENDS, likely... I do. didn't help (specifically referring to the new 2.9.0.3 security/snort port) I THINK this cludge helped: but I am not happy with it. not sure I understand portlint complaints about !=, or if there is/was a better way. Running portlint shows both the issue and an URL for the recommended approach: # cd /usr/ports/security/snort ; portlint /usr/local/bin/libnet11-config: not found Makefile, line 63: warning: /usr/local/bin/libnet11-config --cflags returned non-zero status /usr/local/bin/libnet11-config: not found Makefile, line 64: warning: /usr/local/bin/libnet11-config --libs returned non-zero status /usr/local/bin/libnet11-config: not found Makefile, line 63: warning: /usr/local/bin/libnet11-config --cflags returned non-zero status /usr/local/bin/libnet11-config: not found Makefile, line 64: warning: /usr/local/bin/libnet11-config --libs returned non-zero status WARN: Makefile: [63]: use of != in assignments is almost never a good thing to do. Try to avoid using them. See http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049777.html for some helpful hints on what to do instead. WARN: Makefile: possible use of absolute pathname /var/log/snort. 0 fatal errors and 2 warnings found. The problem with != is that is is evaluated in a subshell regardless of whether the results are needed, and it happens while the Makefile is first being read, before it tries to figure out which targets need to be processed. This is why setting libnet in BUILD_DEPENDS isn't being processed until after these commands are run (or fail to run, as above). GNU Make refers to the distinction as immediate vs. deferred, and you want to use the latter where possible. Regards, -- -Chuck ___ 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: how to bootstrap libtool?
On Feb 9, 2011, at 11:14 AM, Michael Scheidell wrote: The problem with != is that is is evaluated in a subshell regardless of whether the results are needed, and it happens while the Makefile is first being read, before it tries to figure out which targets need to be processed. This is why setting libnet in BUILD_DEPENDS isn't being processed until after these commands are run (or fail to run, as above). which is useless information to me. don't know why, been doing freebsd for 10 years, been a port maintainer for.. ? 4? 5? don't remember. still that is useless information, and doesn't make any sense. doesn't tell me what,why, how, or when to replace what lines with what alternatives. yes, I can hard code it, but I don't really understand what those (inherited lines) actually do. OK. If you don't understand make, and you aren't willing to look at the documentation, then it's hardly surprising that you're having problems figuring things out. Engineers solve problems. Managers create problems. Senior management exists to decide *which* problems management ought to create. (In this particular case, it seems like you ought to delegate the problem to an engineer who has the knowledge to solve it. If I get some free time, I'll see what I can do, otherwise someone else might volunteer) Regards, -- -Chuck ___ 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: Attention ports committers
On Jan 14, 2011, at 10:18 AM, joeb wrote: I would like to draw the attention of a ports committer to port http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148777 If it needs further work please provide feedback. Have you addressed the problems mentioned by Chris Rees utis...@gmail.com yet? A port submission which doesn't follow the requirements in the Porter's Handbook most likely isn't going to be added Regards, -- -Chuck ___ 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: Attention ports committers
On Jan 14, 2011, at 2:09 PM, Eygene Ryabinkin wrote: Almost all of them were addressed, as I can judge. But I had spotted some more nits ;)). Thanks for the additional review. :-) Regards, -- -Chuck ___ 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: ldconfig -r does not show devel/sfml libraries
On Jan 7, 2011, at 10:40 AM, David Demelier wrote: [ ... ] the weird thing is that ldconfig -m is ran after the devel/sfml install. What can I do to fix? If you cat /var/run/ld-elf.so.hints, does /usr/local/lib appear in the list of paths? (Yeah, this is a mildly binary file, but...) Does running ldconfig -R do anything helpful? Regards, -- -Chuck ___ 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/rkhunter 1.3.8 - false warning?
On Jan 4, 2011, at 9:38 AM, Torfinn Ingolfsen wrote: rkhunter 1.3.8 from ports complains about the /etc/passwd file. Why does it do that? It's buggy? RKHunter is better known for generating vast numbers of obscure false positives than it is for actually providing a security benefit. Something like tripwire or a functioning backup system which can provide a comparison of changes against current filesystem state is much more likely to be useful. Regards, -- -Chuck ___ 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: Upgrading mysql50-{server,client,scripts} to 5.0.91
On Jan 4, 2011, at 10:38 AM, Tom Judge wrote: Do you know if there would be any issues with MySQL 5.0.91 running on FreeBSD? There shouldn't be. I think ports is still at mysql-server-5.0.90_2, which works fine, but I would expect that 5.0.91 would also be fine Regards, -- -Chuck ___ 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: bsd 6 index file
On Dec 21, 2010, at 10:53 AM, Paul Macdonald wrote: I have a couple of older boxes on freebsd 6 that are reporting ports succeeding index, even after a fresh index has been downloaded. e.g portupgrade-2.4.8_1,2succeeds index (index has 2.4.8,2) spamass-milter-0.3.1_11succeeds index (index has 0.3.1_10) FreeBSD-6 is past it's end of life, and the ports tree no longer maintains a current index file for 6.x. You can do a make index yourself, but there are no guarantees that this will continue to work as time passes. Time to upgrade to FreeBSD 7 or 8... Regards, -- -Chuck ___ 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: ftp/proftpd 1.3.3c with a version which contained a backdoor.
On Dec 2, 2010, at 1:22 PM, Ivan Klymenko wrote: What do you think is it worth to pay attention to these events: http://sourceforge.net/mailarchive/message.php?msg_name=alpine.DEB.2.00.1012011542220.12930%40familiar.castaglia.org and that in this case needs to be done with the port ftp/proftpd itself? Presumably/hopefully, the proftpd tarball which contained the backdoor would fail to match the distinfo for the port: SHA256 (proftpd-1.3.3c.tar.bz2) = ea7f02e21f81e6ce79ebde8bbbd334bd269a039ac9137196a35309f791b24db1 SIZE (proftpd-1.3.3c.tar.bz2) = 4166609 Checking, the tarball you now fetch is the one which matches their md5 and GnuPG signing from the link above... Regards, -- -Chuck ___ 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: ftp/proftpd 1.3.3c with a version which contained a backdoor.
On Dec 2, 2010, at 2:55 PM, Rob Farmer wrote: Checking, the tarball you now fetch is the one which matches their md5 and GnuPG signing from the link above... For several hours on Wednesday the distinfo was updated to the compromised version (it has been reverted), so anyone who updated this port recently should check their system. I see-- that's useful information to be aware of. Hopefully port maintainers practice a bit more wariness about distfiles changing unexpectedly; while it's common enough that people re-roll tarballs for whatever reason, it seems like there have been more incidents of reference sites getting owned... Regards, -- -Chuck ___ 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 - installation upgrade history
On Nov 30, 2010, at 10:41 AM, David Southwell wrote: I was thinking of something which is far more comprehensive and systematic. Whilst installed options are obtained by examining /var/db/ports the files do not do not provide the detailed historical information which I envisage. Correct. Unless you've taken good backups, nothing else currently preserves all of the historical information you envision, but you can at least get some of the requested info just out of the current filesystem. The freshports/freebsd sites will tell us when the distributed ports tree was changed but does not provide a historical record of changes to the local ports tree. Also correct. Again, short of having periodic backups made at sufficiently rapid intervals, there is no way to track that information over time. Regards, -- -Chuck ___ 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 - installation upgrade history
On Nov 30, 2010, at 10:58 AM, David Southwell wrote: Seems to me that a comprehensive record would be extremely useful on a local system. I am wondering how difficult it might be to collect data from applications such as: cvsup of ports tree portupgrade/portmaster changes to /var/db/ports changes to /usr/ports/distfiles It's not difficult. The normal way people track changes to filesystems over time is by making backups (or snapshots, or other equivalents). The normal way people track process execution is accton / sa. The results could be held in a mysql database. I suppose...MySQL isn't particularly efficient at dealing with large numbers of BLOBs, which is what importing filesystem-tree changes would probably become. You'd likely end up with a MySQL database which grows to be many orders of magnitude bigger than the size of /var/db/ports + whatever under /usr/ports. Things like CVS or Subversion better understand how to represent the list of deltas representing the changes than MySQL does. Good backup software which understands dedup'ing, things like mbox format, etc can also track changes more efficiently than a naive method of keeping around a copy of every file every time it changes. -- -Chuck ___ 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 - installation upgrade history
On Nov 30, 2010, at 10:24 AM, David Southwell wrote: Something fairly comprehensive that would enable one to see when a port was first installed, its original version number, when it was upgraded/deinstalled/reinstalled and subsequent changes to the installed version. Maybe also time/date when a port tree was updated and which ports were affected by those updates. You can gather some information by: ls -ltr /var/db/ports For full information about all of the changes to the ports tree, you'd need to take a look at the CVS history, perhaps via: http://www.freshports.org/ http://www.freebsd.org/cgi/cvsweb.cgi/ports/ Regards, -- -Chuck ___ 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: unable to build net-im/ejabberd 2.1.5
On Oct 22, 2010, at 12:19 PM, Ruslan Mahmatkhanov wrote: It works. Thanks! Very good; you're most welcome Regards, -- -Chuck ___ 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: unable to build net-im/ejabberd 2.1.5
On Oct 22, 2010, at 11:44 AM, Ruslan Mahmatkhanov wrote: In file included from sha_drv.c:23: /usr/include/openssl/md2.h:64:2: error: #error MD2 is disabled. gmake[1]: *** [../sha_drv.so] Ошибка 1 gmake[1]: Leaving directory `/usr/ports/net-im/ejabberd/work/ejabberd-2.1.5/src/tls' gmake: *** [all-recursive] Ошибка 1 *** Error code 1 I've tried both base system openssl and port openssl (using WITH_OPENSSL_PORT knob in make.conf). # pkg_info | grep erlang erlang-r14b,1 A functional programming language from Ericsson # uname -srp FreeBSD 8.1-STABLE i386 How to fix this error? cd /usr/ports/security/openssl make config [ ...ensure that the MD2 option is checked... ] rebuild and reinstall the openssl port rebuild and reinstall ejabberd port Regards, -- -Chuck ___ 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: ptlib build failure - breaks pwlib - hence also asterisk - opal - openh323
Hi, Steve-- On Sep 20, 2010, at 4:14 PM, Steve Ames wrote: PS Would you mind not top posting Seriously? Top posting is somehow worse than scrolling to the bottom of pages of compile output to see a tiny response? Welcome to the 21st century. Welcome to the FreeBSD mailing lists. Please see: http://www.freebsd.org/doc/en/articles/mailing-list-faq/etiquette.html#ETIQUETTE-REPLYING Please do not top post. By this, we mean that if you are replying to a message, please put your replies after the text that you copy in your reply. • A: Because it reverses the logical flow of conversation. • Q: Why is top posting frowned upon? Regards, -- -Chuck ___ 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: [legal] port with restrictive license
Hi-- On Sep 16, 2010, at 11:44 AM, Dmitry Marakasov wrote: The only thing left that worries me is that US export laws stuff - I absolutely don't understand what that means and how we can/cannot violate these by mirroring distfiles/packages. For now I've removed all mirroring permissions from LICENSE_PERMS for EULA, so this should be safe. However, I'd really like that stuff explained by someone so mirroring could maybe be reenabled. Is I understand, to comply with license, we need to prohibit distribution of software into (or to a national or resident of) any country to which the United States has embargoed goods, which we likely won't do thus we should not mirror the files. It generally isn't useful to include specific legal geographical restrictions into the terms of a license which is used world-wide. US citizens/residents already are obligated to obey US law, just as people elsewhere are obligated to follow their own local laws; a software license doesn't need to mention them any more than it needs to include the Magnuson-Moss Warranty Act or the US FTC's policies and statutes on unfair or deceptive acts or practices. Both the OSI and the FSF/GNU folks recommend against including references to US ITAR export restrictions or similar in licenses. However, if you want more info, then the US export regulations described as ITAR are documented here: http://www.pmddtc.state.gov/regulations_laws/itar_consolidated.html ...but they explicitly do not apply to material which legitimately is in the public domain: The controls of this part apply to the export of technical data and the export of classified defense articles. Information which is in the public domain (see §120.11 of this subchapter and §125.4(b)(13)) is not subject to the controls of this subchapter. FTP or webservers located in the US which are hosting open-source software generally do not check whether source IPs come from an embargoed country. On the other hand, Dan Bernstein and Phil Zimmerman/PGP folks ended up fighting protracted legal battles over the issue of publishing cryptographic software Regards, -- -Chuck Disclaimer: I'm not a lawyer, nor will I play one on FreeBSD mailing lists. :-) ___ 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: devel/autotools267 and UPDATING
Hi, all-- On Sep 15, 2010, at 4:43 PM, Barbara wrote: About my previous mail, shouldn't the upgrade be handled by the entry in MOVED? Is it a portupgrade problem? Is the rebuild of ports like xmms or libX11 really necessary after a new version of autoconf? It looks like maybe a repocopy is going on (or has gone wrong), since it is pointing to autoconf-2.62: # pwd /usr/ports/devel/autoconf267 # cat distinfo MD5 (autoconf-2.62.tar.bz2) = e1fb8fe0b22e651240afdfa2be537a3c SHA256 (autoconf-2.62.tar.bz2) = 42be7628e32fd3bebe07d684b11fb6e7e7920ef698fc4ccb3da6d77f91cefb96 SIZE (autoconf-2.62.tar.bz2) = 1165951 # head Makefile # New ports collection makefile for:autoconf262 # Date created: 7th December 2006 # Whom: a...@freebsd.org # # $FreeBSD: ports/devel/autoconf267/Makefile,v 1.75 2009/12/16 11:21:25 linimon Exp $ # PORTNAME= autoconf PORTVERSION=2.62 CATEGORIES= devel Regards, -- -Chuck ___ 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: devel/autotools267 and UPDATING
Hi, Ade-- On Sep 15, 2010, at 5:13 PM, Ade Lovett wrote: On Sep 15, 2010, at 18:48 , Chuck Swiger wrote: It looks like maybe a repocopy is going on (or has gone wrong), since it is pointing to autoconf-2.62: You need to update your ports tree. Makefile is revision 1.77, not 1.75 as you have shown. Oh, I did-- but it seems like cvsup8.FreeBSD.org is running behind. I switched to a different cvsup server and /usr/ports/devel/autoconf267 looks sensible now. Thanks for the feedback, -- -Chuck ___ 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: Converting from jiffies to ticks
Hi-- On Aug 19, 2010, at 12:15 PM, Jesse Smith wrote: This raises two questions for me: 1. Where can I find the equivalent information on FreeBSD? I assume there's a function call. Maybe in the kvm_* family? I need to be able to get the number of ticks a given PID is using. Does process accounting described by acct(2) / acct(5) address your requirements? 2. Any idea on what the conversion rate between ticks and jiffies is? Are they the same thing, but with different names? Or is it a kilometres and miles issue? It depends on what the system interrupt quanta are set to: http://en.wikipedia.org/wiki/Jiffy_%28time%29 In the case of FreeBSD, the standard interrupt rate and the rate which statistical sampling is done are not the same, and the latter is done at fuzzy times to prevent bad processes that as trying to cheat and avoid their time being counted Regards, -- -Chuck ___ 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: net-im/telepathy-haze Build fail
On Jul 28, 2010, at 10:00 AM, David Southwell wrote: This is a python error. Is anyone sufficiently familiar with python to take a look at tools/glib-signals-marshall-gen.py. Is all the code in that script strict enough for python 3. No, that script contains syntax that doesn't work with Python 3: File ../tools/glib-signals-marshal-gen.py, line 49 print 'VOID:' + ','.join(rhs) ^ SyntaxError: invalid syntax See: http://docs.python.org/release/3.0.1/whatsnew/3.0.html#print-is-a-function This one change alone is so fundamental that you should assume that almost no python-2 code will run under python-3 without changes Regards, -- -Chuck ___ 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: net-im/telepathy-haze Build fail
On Jul 28, 2010, at 11:13 AM, David Southwell wrote: In that case should the port not call for 26? Here is an extract from my pkgdb from which you can see python26 is installed on the system. If the port needs 26 surely should it not call for it as a dependency rather than failing because python31-3.1.2_1 is present?? You'd have to discuss that with gn...@freebsd.org. However, you would certainly save time if you kept /usr/local/bin/python as a link to python2.6 instead of to python-3.x. Regards, -- -Chuck ___ 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: net-im/telepathy-haze Build fail
On Jul 28, 2010, at 11:28 AM, David Southwell wrote: I believe the porters handbook recomends that ports should set the appropriate python environment at build time to prevent this problem occuring. Sure, modulo that setting USE_PYTHON isn't going to change the default Python which gets run when scripts do: #!/usr/bin/env python Again, at the present time, most things are going to want python-2.x; anything which is python-3.x should explicitly invoke python3. Regards, -- -Chuck ___ 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: apr ports devrandom option
On Jun 16, 2010, at 4:01 PM, RW wrote: The devel/apr* ports have an option to use /dev/random, which is on by default. I was wondering under what circumstances anyone would turn that off. As far as I can see switching it off doesn't replace /dev/random with anything else. On some platforms, /dev/random and /dev/urandom used to provide different quality of random numbers-- FreeBSD simply uses Yarrow or a hardware RNG source if available. Even if you disable it, it's likely to just fall back to OpenSSL's source of random numbers, which probably is /dev/random anyway Regards, -- -Chuck ___ 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: apr ports devrandom option
On Jun 16, 2010, at 5:00 PM, RW wrote:
Right, but I'm asking about the make config port option, not the configure
options to apr itself.
When you enable the option via make config, apr's ./configure gets fed the
appropriate flag:
OPTIONS= ...
DEVRANDOM Use /dev/random or compatible in apr on \
...
.if defined(WITHOUT_DEVRANDOM)
CONFIGURE_ARGS+=--without-devrandom
.else
CONFIGURE_ARGS+=--with-devrandom
.if defined(PKGNAMESUFFIX)
PKGNAMESUFFIX:= ${PKGNAMESUFFIX}-devrandom
.else
PKGNAMESUFFIX= -devrandom
.endif
.endif
Regards,
--
-Chuck
___
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: LICENSE questions
Hi-- On Jun 14, 2010, at 4:10 PM, Doug Barton wrote: On 06/14/10 09:59, Chuck Swiger wrote: On Jun 14, 2010, at 1:07 AM, Doug Barton wrote: I'm working on adding LICENSE information to my ports, and have a few questions. A lot of my ports are ISC products, and they have the following: http://people.freebsd.org/~dougb/COPYRIGHT.txt Yes, that's the ISC license, http://www.opensource.org/licenses/isc-license.txt. Right-O, so can we/I add that to ports/Mk/bsd.license*? +1 to that. (ISC isn't extremely common, but it's not rare, and a bunch of commonly used ports do use it.) I also have dns/fpdns which has this: http://people.freebsd.org/~dougb/LICENSE.txt which looks like it could be BSD, but I'm not sure. I also have several others in this category. That's a 3-clause BSD license variant. Yeah, I guess I didn't ask my question properly. :) Can I use just BSD for the license in these cases, or is there a need for us to differentiate between this BSD license and the now-standard 2-clause version? The main distinction which matters for BSD licenses is whether the acknowledgement clause (aka clause 3 of the 4-clause license from FreeBSD's /COPYRIGHT) is present, since that makes it not miscible with GPLv2. In your particular case, you don't have the acknowledgement clause. net-mgmt/p5-Net-IP has http://people.freebsd.org/~dougb/COPYING.txt which could fall into the perl category, except there isn't one. :) Many Perl things are licensed under the same terms as Perl itself; ie, dual-licensed under the GPL Artistic license. (The latter license is not well-written, and should be deprecated-- the GPL does a better job.) My vote would be that we add a PERL category, but maybe there is a reason not to do this? Considering that there are ~4000 p5 ports, it seems reasonable to indicate that they are licensed under the same terms as Perl itself. Similar arguments might be made for Python or Ruby, but I'm not sure they're as common. [ ...quoted-printable mangling deleted... ] That's a MIT/X11 license minus the all-caps DISCLAIMER. Oy, ok, so how do I classify it? Or am I correct in assuming we do not yet have a category for it? I see MIT listed, although I would describe it more precisely as the MIT/X11 variant rather than a pure MIT license. Regards, -- -Chuck ___ 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: License Framework: Develop Best Practices
On Jun 14, 2010, at 8:30 PM, Warren Block wrote: On Tue, 15 Jun 2010, Marco Br?der wrote: But it is not very useful in its current state, because several popular licenses are missing and some license foo is not right / specific enough to be considered legally correct (for example there is no 'one BSD License', there are at least three of them, all legally different). The legal consequences of even very small differences can be very huge. We actually have to make this legally right or the whole thing is useless. This points nicely to something I've been wondering about. Could it be a problem for non-lawyers to categorize (give an opinion) on a license that isn't an exact word-for-word duplicate of a known license? Where I live, someone without a legal degree cannot offer legal advice-- giving rise to acronyms like IANAL (I Am Not A Lawyer) and TINLA (This Is Not Legal Advice). You should not rely on automated tools including the ports framework to provide arbitrarily complex guidance appropriate for various combinations of licenses, local peculiarities, and so forth-- if you don't feel comfortable you understand and comply with the licenses of the software you use, hire a local lawyer-- don't ask for legal advice from a world-wide mailing list. :-) However, there are plenty of sites like SourceForge, Apache.org, GNU/FSF, and so forth which provide support/hosting for various projects and provide a classification of licenses. Like almost any human activity, such a categorization process is imperfect-- but good enough for now works just fine, until someone notices/complains about some issue, in which case it will probably be quickly fixed. There are probably some things which the FreeBSD implementation of licensing could be improved. For example, if port maintainers or committers make an effort to confirm with the original author(s)/copyright holder(s) that the license of the software is being correctly categorized and recorded that with the CVS/SVN commit adopting the license categorization in the port Makefile. It might also not be a bad idea to not display anything about licensing until a human enables some Makefile switch which acknowledges the limitations of the system (ie, license description coverage is incomplete, etc, etc). Regards, -- -Chuck ___ 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: Users and groups kept after a port deinstallation
Hi-- On May 22, 2010, at 10:59 PM, Matthew Seaman wrote: OpenBSD has a convention that all system user accounts start with a '_' character. There are a few accounts in UIDs that have adopted that, but no great stampede to adopt the idea despite most people agreeing with it. That convention is being adopted by MacOS 10.6, also. It does make it easier for one to separate out processes invoked by a human from automated tasks in ps or top... Regards, -- -Chuck ___ 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
portupgrade of gtk-2.18.7_1 failing against cairo-xlib?
Hi, all-- Upgrading x11-toolkits/gtk20 is failing for me with: --- Upgrading 'gtk-2.18.7' to 'gtk-2.18.7_1' (x11-toolkits/gtk20) OK? [yes] --- Build of x11-toolkits/gtk20 started at: Fri, 23 Apr 2010 13:55:32 -0400 --- Building '/usr/ports/x11-toolkits/gtk20' === Cleaning for gtk-2.18.7_1 === Extracting for gtk-2.18.7_1 = MD5 Checksum OK for gnome2/gtk+-2.18.7.tar.bz2. = SHA256 Checksum OK for gnome2/gtk+-2.18.7.tar.bz2. === gtk-2.18.7_1 depends on file: /usr/local/bin/perl5.8.9 - found === Patching for gtk-2.18.7_1 === gtk-2.18.7_1 depends on file: /usr/local/bin/perl5.8.9 - found === gtk-2.18.7_1 depends on package: libtool=2.2 - found === Applying FreeBSD patches for gtk-2.18.7_1 [ ... ] checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether gmake sets $(MAKE)... (cached) yes checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for BASE_DEPENDENCIES... yes checking for CAIRO_BACKEND... configure: error: Package requirements (cairo-xlib = 1.6) were not met: gnome-config: not found No package 'cairo-xlib' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables CAIRO_BACKEND_CFLAGS and CAIRO_BACKEND_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === Script configure failed unexpectedly. I do have: # pkg_info | grep cairo cairo-1.8.8_1,1 Vector graphics library with cross-device output support # locate cairo-xlib ...returns no hits, and gnomelogalyzer.sh does not provide useful suggestions, so additional data suggested is available here: http://freebsd-gnome.pastebin.com/XhYpCeHf (/usr/ports/x11-toolkits/gtk20/work/gtk+-2.18.7/config.log) http://freebsd-gnome.pastebin.com/FHLud0D8 (ls -1 /var/db/pkg) Regards, -- -Chuck ___ 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: Exchange ActiveSync account
Hi-- On Mar 25, 2010, at 6:16 AM, Jack Raats wrote: I have an Exchange ActiveSync account and I would like to get this mail on my freebsd 7.3-stable server. I donn't haven an imap or pop account, only the information of the activesync account. Can anyone give me a clue how to achieve this? Yes, abandon this proprietary account in favor of something using published Internet RFC standards. As far as I can tell from 30 seconds with the wikipedia entry, there are no freely available implementations which would run on FreeBSD. You can pay for the Outlook connector to Zimbra, which runs on Linux and MacOSX Regards, -- -Chuck ___ 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: python and HUGE_STACK_SIZE
Hi-- On Mar 24, 2010, at 4:11 PM, Xin LI wrote: If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a reason to provide the option to not compile python with it, or at the very least, should it default to being on? Ah, yes this is the thing I turn on on all systems I have myself... I'd vote for enabling it by default. I've run and written quite a bit of Python (including Trac, Mailman, the Python IDE, our own custom stuff [like some log munging and web processing stuff], and even a few graphical Python games) without ever turning HUGE_STACK_SIZE on. I don't have any objection to turning it on, but it's not needed by default for most things. YMMV. Regards, -- -Chuck ___ 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: lang/guile fails to build on amd64 / 9-CURRENT
On Mar 18, 2010, at 12:48 AM, Doug Barton wrote: touch /etc/make.conf echo CFLAGS += -Wno-error /etc/make.conf No reason for the touch first, FWIW. Some shells aren't willing to append to files which don't already exist: # echo CFLAGS += -Wno-error /etc/make.conf zsh: no such file or directory: /etc/make.conf Regards, -- -Chuck ___ 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: lang/guile fails to build on amd64 / 9-CURRENT
Hi-- On Mar 17, 2010, at 6:35 PM, Jason Garrett wrote: I can't believe that no one running 9-CURRENT also didn't build gnome2 and found this problem? Shall I submit a PR? You appear to be compiling with -Werror set. Consider changing that, otherwise submitting a PR with the fix would certainly be helpful. Regards, -- -Chuck ___ 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: lang/guile fails to build on amd64 / 9-CURRENT
On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: This must be set by default as I have set no other flags in /etc/make.conf or otherwise. How would I go about un-setting this? -Wno-error? Yes, that should do it: touch /etc/make.conf echo CFLAGS += -Wno-error /etc/make.conf Please note that I'm inferring from the compiler treating a #warning as an error; if you show more of the actual compilation line, the list might be better able to understand what the compiler flags were and where they might have been set. Regards, -- -Chuck ___ 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: spamassassin problem with upgrade
On Feb 12, 2010, at 2:09 PM, Marco Beishuizen wrote: Feb 12 23:06:42.196 [4545] dbg: dns: query failed: mirrors.updates.spamassassin.org = NOERROR channel: no 'mirrors.updates.spamassassin.org' record found, channel failed Feb 12 23:06:42.196 [4545] dbg: diag: updates complete, exiting with code 4 Looks like your local DNS might be broken: # dig -t any mirrors.updates.spamassassin.org ; DiG 9.5.2-P2 -t any mirrors.updates.spamassassin.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 40052 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0 ;; QUESTION SECTION: ;mirrors.updates.spamassassin.org. IN ANY ;; ANSWER SECTION: mirrors.updates.spamassassin.org. 3600 IN TXT http://spamassassin.apache.org/updates/MIRRORED.BY; ;; AUTHORITY SECTION: spamassassin.org. 70841 IN NS ns.hyperreal.org. spamassassin.org. 70841 IN NS a.auth-ns.sonic.net. spamassassin.org. 70841 IN NS b.auth-ns.sonic.net. spamassassin.org. 70841 IN NS c.auth-ns.sonic.net. ;; Query time: 56 msec ;; SERVER: 206.126.224.1#53(206.126.224.1) ;; WHEN: Fri Feb 12 17:19:14 2010 ;; MSG SIZE rcvd: 205 Regards, -- -Chuck ___ 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: Puzzled about gettext dependencies
Hi-- On Feb 9, 2010, at 3:53 PM, Andrea Venturoli wrote: # pkg_which /usr/local/bin/msgcat gettext-0.17_1 # ldd /usr/local/bin/msgcat /usr/local/bin/msgcat: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x33c7f000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x33cb4000) libcroco-0.6.so.3 = /usr/local/lib/libcroco-0.6.so.3 (0x33d91000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x33dc6000) libz.so.4 = /lib/libz.so.4 (0x33ef2000) libm.so.5 = /lib/libm.so.5 (0x33f04000) libglib-2.0.so.0 = /usr/local/lib/libglib-2.0.so.0 (0x33f19000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x33fc8000) libpcre.so.0 = /usr/local/lib/libpcre.so.0 (0x33fd1000) libncurses.so.7 = /lib/libncurses.so.7 (0x34004000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x34043000) libc.so.7 = /lib/libc.so.7 (0x3413a000) libz.so.3 = /lib/libz.so.3 (0x3423c000) libm.so.4 = /lib/libm.so.4 (0x3424d000) Is it me or the output of the latter command contraddicts the dependency database? It seems to me libcroco, libglib, libpcre, and libxml2 are additional dependencies... Have I done something wrong? It doesn't do that here: # pkg_which /usr/local/bin/msgcat gettext-0.17_1 # ldd /usr/local/bin/msgcat /usr/local/bin/msgcat: libgettextsrc-0.17.so = /usr/local/lib/libgettextsrc-0.17.so (0x2807e000) libgettextlib-0.17.so = /usr/local/lib/libgettextlib-0.17.so (0x280b2000) libncurses.so.6 = /lib/libncurses.so.6 (0x281b2000) libintl.so.8 = /usr/local/lib/libintl.so.8 (0x281f1000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x281fa000) libc.so.6 = /lib/libc.so.6 (0x282d9000) I wonder why it's dragged in all of those...? Regards, -- -Chuck ___ 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: Need help from someone with boost fu + RELENG_6
Hi, Doug--
On Jan 18, 2010, at 1:17 PM, Doug Barton wrote:
However I apparently inherited some build problems on 6-stable that I
don't understand, and since I don't have a 6-stable system available I
cannot test fixes for. The problems appear to be boost-related, both
more or less look like this:
In file included from /usr/local/include/boost/thread/future.hpp:12,
from /usr/local/include/boost/thread.hpp:24,
from ../include/libtorrent/storage.hpp:45,
from ../include/libtorrent/peer_connection.hpp:63,
from peer_connection.cpp:41:
/usr/local/include/boost/exception_ptr.hpp:43: error: looser throw
specifier for `virtual boost::exception_ptr::~exception_ptr()'
/usr/local/include/boost/exception/detail/exception_ptr_base.hpp:27:
error: overriding `virtual
boost::exception_detail::exception_ptr_base::~exception_ptr_base() throw ()'
[ ... ]
Whether this constitutes a legitimate problem or something that the compiler
should figure out seems to be arguable-- evidently this sort of error is highly
dependent upon the compiler version. The following changes seems to allow
net-p2p/rblibtorrent to build successfully under 6-STABLE:
--- /usr/local/include/boost/exception/detail/exception_ptr_base.hpp~
2010-01-18 18:20:52.0 -0500
+++ /usr/local/include/boost/exception/detail/exception_ptr_base.hpp
2010-01-18 19:03:46.0 -0500
@@ -23,7 +23,7 @@
protected:
virtual
-~exception_ptr_base() throw()
+~exception_ptr_base()
{
}
};
--- libtorrent-0.13/src/storage.cpp~2010-01-18 17:11:00.0 -0500
+++ libtorrent-0.13/src/storage.cpp 2010-01-18 19:19:05.0 -0500
@@ -378,7 +378,7 @@
size_type read_impl(char* buf, int slot, int offset, int size,
bool fill_zero);
- ~storage()
+ ~storage() throw ()
{ m_files.release(this); }
boost::intrusive_ptrtorrent_info const m_info;
Eww. It's entirely possible that adding a USE_GCC=4.2+ line to Boost or these
ports might provide a cleaner solution. Or consult someone who knows C++
better than I...
Regards,
--
-Chuck
___
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: Update claws-mail
Hi-- On Nov 20, 2009, at 1:07 PM, Sylvio Cesar wrote: There is PR to update of claws-mail. See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/139467 It will be committed soon. It's quite useful for people to try the patches for updates that they are interested in, and report back whether the update works well for them. Especially if the ports tree is in a freeze or slush period (ie, say for 8.0 release), portmgr folks like to see independent confirmation that changes work as expected... Regards, -- -Chuck ___ 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: Stealth dependency in textproc/redland
Hi, Mel-- On Sep 16, 2009, at 5:46 AM, Mel Flynn wrote: the naughty rasqal/configure will try to find libgmp and link with it if found [ ... ] I traced this to the now absent libgmp.so.8. I'm a little short on time, but if needed can patch and PR it. Would you like this through OPTIONS asking for libgmp or disable it all together? Thanks for the report. It's probably best to have an OPTION which controls whether to pull in libgmp and list as a dependency, or disable it from being used. If you write a patch, I'll be happy to review, otherwise I'll try to add something along those lines when I get a chance... Regards, -- -Chuck ___ 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: amavisd-new crashing
Hi-- On Sep 10, 2009, at 4:23 PM, Eric Sheesley wrote: Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024 /var/amavis/tmp/amavis-20090910T190007-77712: froma...@fromaddr.com - mya...@shadowlair.com SIZE=7072 BODY=7BIT Received: from rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for eshee...@shadowlair.com; Thu, 10 Sep 2009 19:00:07 -0400 (EDT) Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U [65.55.88.13] froma...@fromaddr.com - mya...@shadowlair.com Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type: text/plain, size: 3607 B, name: Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection with proxy 127.0.0.1:10024 Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5 (100%)100, rundown: 0 (0%)100 It sounds like amavisd can't open a BerkeleyDB database (probably the nanny/cache/snmp stuff). Make sure that /var/amavis/db exists and is writable by the amavisd or vscan user, whatever you are running amavisd as: # ls -l /var/amavis/db total 556 -rw-r- 1 vscan vscan 24576 Sep 9 19:01 __db.001 -rw-r- 1 vscan vscan 131072 Sep 9 18:44 __db.002 -rw-r- 1 vscan vscan 270336 Sep 10 11:43 __db.003 -rw-r- 1 vscan vscan 360448 Sep 9 18:44 __db.004 -rw-r- 1 vscan vscan4096 Sep 9 14:20 cache-expiry.db -rw-r- 1 vscan vscan 90112 Sep 10 14:01 cache.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 nanny.db -rw-r- 1 vscan vscan 12288 Sep 9 14:20 snmp.db Regards, -- -Chuck ___ 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: PHP question
On Jan 14, 2009, at 12:26 PM, Albert Thiel wrote: I am trying to figure out how to get a working Apache 2.x server with PHP in a safe configuration (or as safe as possible based upon all the vulns). I do not need a database. What version and options is my best bet. I have tried on my own but losing it. Nothing I have tried works. Make sure your ports tree is up-to-date, and then: cd /usr/ports/www/apache20 # or apache22 if you prefer make install /usr/ports/lang/php5 make config # enable build apache module and Suhosin protection at the very least make install cd /usr/ports/lang/php5-extensions make config # select any additional PHP modules and extensions you want make install Look at less /usr/ports/lang/php5/pkg-message.mod and other documentation from http://www.php.net. Regards, -- -Chuck ___ 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: looking for a tool which handles pdf files
On Jan 6, 2009, at 8:11 AM, Oliver Lehmann wrote: I have a bunch of postcript files (generated by gschem) in various pagesizes (A0-A2). I want to have the generated PS files belonging to the same device in a multipaged PDF. Until now I'm cat-ing the ps files together doing some awk magic to get a multipage ps. I then convert the multipage PS file via ps2pdf to a multipage PDF. My problem now is, that ps2pdf can only set a general pagesize - so A0 for all pages for example - as far as I know. I'm now looking for a tool which creates a multipage PDF with different pagesizes each page (if wanted). Someone told me pdftk could do this but I run an amd64 so no gcj/pdftk for me... Someone knows another tool which would fit here? You might look into the enscript or nenscript ports (/usr/ports/print/ enscript-a4, /usr/ports/print/nenscript); while enscript itself is intended for converting ASCII to PS, I recall that they also came with some utilities like psnup and so forth that would do a better job of gluing together and N-uping your documents. However, I don't recall anything which would support a document consisting of different page sizes; for most people, that sort of thing would be separate documents. -- -Chuck ___ 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: Problem with net/x11vnc update.
On Dec 15, 2008, at 4:15 PM, Beech Rintoul wrote: I'm trying to update the x11vnc port to the latest and I'm getting the following configure error: checking jpeglib.h usability... yes checking jpeglib.h presence... yes checking for jpeglib.h... yes checking for jpeg_CreateCompress in -ljpeg... no Note I see that symbol here: % nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress T jpeg_CreateCompress % pkg_info | grep jpeg jpeg-6b_7 IJG's jpeg compression utilities Are you sure you have the latest version of the port, and that you have these files: /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.la /usr/local/lib/libjpeg.so /usr/local/lib/libjpeg.so.9 ...? :-) Regards, -- -Chuck ___ 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: What if a port doesn't have a version
On Oct 27, 2008, at 11:35 AM, matt donovan wrote: I am writing a port for cinelerra and to grab the source you must get it from the git repo that they have. so the software doesn't have a version so to speak. Should I use the version from the installed version after I install cinelerra for the portversion and just tar it up? Create your own tarball and give it a version which is a date- timestamp like 20081027... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What if a port doesn't have a version
On Oct 27, 2008, at 11:55 AM, Pietro Cerutti wrote: | Should I use the version from the installed version after I install | cinelerra for the portversion and just tar it up? | | Create your own tarball and give it a version which is a date- timestamp | like 20081027... Or use the revision control's revision number. That works well with things like Subversion which ensure that the revision number is monotonically increasing. My understanding of git is that it favors decentralized workareas or repositories without a project-wide unique version number, and it's revisions look like commit c82a22c39cbc32576f64f5c6b3f24b99ea8149c7 in the logs, which do not compare sensibly when considered as numbers. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ADS STudio
Hi-- On Oct 27, 2008, at 12:04 PM, Melissa A. VandenBrink wrote: I only have a license for adstudio 6.5 - 7.0 - is there a port for that version? I can't seem to find it. The port should be located at /usr/ports/databases/adstudio, and claims to be v7.0.4. Presumably your 7.0 license will work with 7.0.4, otherwise you might find portdowngrade helpful. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: start new thread in Makefile
On Oct 20, 2008, at 1:50 PM, Eitan Adler wrote: How would you start a new thread in a Makefile? make isn't threaded but you can run multiple processes in parallel via the -j flag. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: redland build failure
Hi, all-- On Aug 10, 2008, at 2:36 AM, Max Brazhnikov wrote: On Sun, 10 Aug 2008 05:09:54 +0200, Jan Henrik Sylvester wrote: I am on 7.0 with all ports up to date. I have no nonstandard OPTIONS for any dependencies. It seems to have picked up mysql-client although I did not have WITH_MYSQL on. Do I miss anything? I've submitted ports/126410 with fix, waiting for maintainer approval. If this patch fixes the issue, by all means. I've submitted a followup response to that effect to ports/126410. :-) Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsd-grep-20080725_1 -v flag busted...
On Aug 5, 2008, at 5:10 PM, Stuart Barkley wrote: [ ... ] Yes, I was seeing problems building several ports with the latest bsdgrep port. Specifically the neon28 and avifile ports where hanging in the ./configure phase as shown at in the original message in this thread. Thanks for the confirmation, Stuart, as well as your analysis of what the configure script was trying to do with grep that was resulting in the endless loop. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
bsd-grep-20080725_1 -v flag busted...
Hi-- I'd just updated the BSD grep port to bsd-grep-20080725_1, but regrettably have noticed that many things using grep stopped working. For example, running GNU-style ./configure hangs here: configure: creating ./config.status load: 1.15 cmd: sh 72964 [runnable] 7.60u 95.78s 14% 2260k A trivial test case: % echo 'fee\nfi\nfoe\nfum' | ./grep -v fi % echo 'fee\nfi\nfoe\nfum' | /usr/bin/grep -v fi fee foe fum % ./grep --version grep (BSD grep) 2.5.1-FreeBSD Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsd-grep-20080725_1 -v flag busted...
On Aug 4, 2008, at 1:18 PM, Andrey Chernov wrote: echo 'fee\nfi\nfoe\nfum' | ./grep -v fi echo 'fee\nfi\nfoe\nfum' | /usr/bin/grep -v fi Example is broken, echo (for sh) supposed to be echo 'fee fi foe fum' | ... Well, if your shell's built-in echo doesn't grok newlines, then /usr/ bin/printf works, as Daniel suggested. But using /bin/sh and a multiline statement as you suggest shows the exact same problem: % echo 'fee fi foe fum' | ./grep -v fi % echo 'fee fi foe fum' | /usr/bin/grep -v fi fee foe fum (I'm much more interested in confirming whether the bug I see in BSD grep is reproducible by others than debating how to get real newlines from various shells.) -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsd-grep-20080725_1 -v flag busted...
On Aug 4, 2008, at 1:26 PM, Paul Schmehl wrote: Are you sure it's grep that's broken? No, not entirely. :-) [EMAIL PROTECTED] echo 'fee\nfi\nfoe\nfum' fee\nfi\nfoe\nfum Your shell's built-in echo doesn't understand the C-style \n; try using printf command instead of echo. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Deleting python compiled files
On Aug 4, 2008, at 3:35 PM, ros wrote: Working in a port using python i'm facing this problem. If I run the application after the install the py source files are compiled in pyc (or pyo) files. This is good cause precompiled files provide better performances. Mildly. :-) The compiled or optimized .pyc/.pyo files mainly improve upon the time required to load them by the interpreter. The problem is deleting the port. The pyc files aren't registered in the pkg-plist so the deletion isn't complete and I can't delete the main directory containing the application files. If I add the pyc files, when I remove the port I receive an error saying the checksum dosn't exist, and that's right. So what's the best way handle this problem ? Anyway, to address your issue, most Python software uses a setup.py file which uses distutils, and that is supported by the BSD ports infrastructure via the USE_PYDISTUTILS option, which will call the setup.py with the right arguments to build the .pyc/.pyo files. You can then list all of them in the pkg-plist and the right thing should happen from there. If you'd like to see an example, check out one of the python ports which use this, such as /usr/ports/security/denyhosts; you'll see it listing: %%PYTHON_SITELIBDIR%%/DenyHosts/loginattempt.py %%PYTHON_SITELIBDIR%%/DenyHosts/loginattempt.pyc %%PYTHON_SITELIBDIR%%/DenyHosts/loginattempt.pyo [ ... ] Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIG Update for www/webalizer
On Jul 21, 2008, at 8:55 AM, Eric Zimmerman wrote: thanks for the info. The main webalizer page states: July 12, 2008 Version 2.20-01 has been released. This is a drop in replacement for sites running v2.01 with no additional changes required, and all users are encouraged to upgrade when possible. Many new and exciting features have been added in this release. See the CHANGES file for a list of what's been changed/added/fixed. Go to the download page to obtain a copy in your preferred format. any idea what command line options changed based on your experience? For what it's worth, I updated the webalyzer port and it had no problems running against my old config file and the reports being generated seem to be valid. I don't feed it options via the command line, however Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
DejaVuSansMono-Roman.ttf missing after update to mailgraph-1.14_2 + rrdtool-1.3.0
Hi, all-- My beautiful mailgraph charts were missing the fonts after updating to mailgraph-1.14_2 + rrdtool-1.3.0, and logging: [Thu Jun 26 19:48:34 2008] [error] [client w.x.y.z] Premature end of script headers: mailgraph.cgi, referer: http://www.example.com/cgi-bin/mailgraph.cgi [Thu Jun 26 19:48:34 2008] [error] [client w.x.y.z] ERROR: failed to load /usr/local/share/rrdtool/fonts/DejaVuSansMono-Roman.ttf, referer: http://www.example.com/cgi-bin/mailgraph.cgi I restored a backup copy, which works fine, but the file is no longer associated with any port: # pkg_which /usr/local/share/rrdtool/fonts/DejaVuSansMono-Roman.ttf ? I'm not sure whether this should belong to rrdtool port, or to mailgraph, but at least one of these should ensure that the fonts needed get installed. If it matters, I generally compile with WITHOUT_X11=true set in /etc/make.conf... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
archivers/lzo2 selftest is a little much...?
Hi, all--
I'm all for having software do a sanity check before being used, but
the recent update to archivers/lzo2 (lzo2-2.03) generates some
~28,000+ lines of output. Please consider a change like:
--- ports/archivers/lzo2/Makefile~ Fri May 30 18:33:46 2008
+++ ports/archivers/lzo2/Makefile Fri May 30 19:05:55 2008
@@ -25,3 +25,3 @@
-post-build:
+test:
cd ${WRKSRC} ${MAKE} test
Regards,
--
-Chuck
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup4 seems to be badly constipated
On Apr 18, 2008, at 2:46 PM, Kevin Oberman wrote: Don't know if this is the appropriate place for this report, but cvsup4 seems to be permanently saying that too many users are logged in and to try again later. Been that wat for about a day. Seems to be working fine, here: -- Running /usr/local/bin/cvsup -- Connected to cvsup4.FreeBSD.org Updating collection src-all/cvs Edit src/contrib/gcc/config/i386/freebsd64.h [ ... ] -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling utilizing multiple CPUs
On Jan 15, 2008, at 11:34 AM, Chuck Robey wrote: The quality of the Makefiles or similar used by individual ports varies, and many of them are not safe to compile in a multithreaded fashion. You can set MAKEFLAGS=-j3 or similar in your environment, but it's really not recommended. I think it's necessary to tell why its not recommend it: because many makefiles are insufficiently sedt up to correctly allow multiple cpu's to work side by side. Well, didn't I just say that above? I assure you that not safe to compile in a multithreaded fashion means pretty much the same thing as not set up to correctly allow multiple CPU's to work side by side. :-) Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limited Freeware License question
On Jan 15, 2008, at 4:13 PM, Dmitry Marakasov wrote:
I want to port a game which requires data released under Limited
Freeware License
(http://liberatedgames.org/licenses/Limited_Freeware_License.txt)
---
The owner of this software reserves all rights granted by copyright.
However, the owner grants the following rights to users:
1) The right to make personal copies of the software.
2) The right to distribute the software for free (at no cost) to other
users.
No further rights are granted or should be assumed. This includes, but
is not limited to, the right to create derivative works.
---
OK, this is a fairly classic restrictive freeware license.
The question is: does FreeBSD port fall under `derivative work'?
So long as you do not need to make any patches to the software, no.
I.e. may the data files be installed by it (or should I ask users
to download files themselves instead) and may the package of such
a port be created? Port does not modify any datafiles, it just needs
to download zip and install them to ${DATADIR}.
The following section of the Porter's Handbook describes the variables
you should set to comply with this license:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-restrictions.html
You should definitely set NO_CDROM and probably NO_PACKAGE, as
creating a package would be making a derivative work. However, you
might consider asking the authors of this software for additional
permission
Regards,
--
-Chuck
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limited Freeware License question
On Jan 15, 2008, at 4:13 PM, Dmitry Marakasov [EMAIL PROTECTED] wrote: [ ... ] Your email bounces, BTW, so you probably wish to fix it: [EMAIL PROTECTED]: host cluster.relay.agava.net[89.108.67.8] said: 550 5.1.1 [EMAIL PROTECTED]: Recipient address rejected: User unknown in relay recipient table (in reply to RCPT TO command) Reporting-MTA: dns; mail-out3.apple.com X-Postfix-Queue-ID: 554A21E270BB X-Postfix-Sender: rfc822; [EMAIL PROTECTED] Arrival-Date: Tue, 15 Jan 2008 16:23:42 -0800 (PST) Final-Recipient: rfc822; [EMAIL PROTECTED] Original-Recipient: rfc822;[EMAIL PROTECTED] Action: failed Status: 5.1.1 Remote-MTA: dns; cluster.relay.agava.net Diagnostic-Code: smtp; 550 5.1.1 [EMAIL PROTECTED]: Recipient address rejected: User unknown in relay recipient table -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Handing references to GPL within ports
On Sep 13, 2007, at 12:21 AM, Peter Jeremy wrote: I'm working on a port for H-Inventory (a computer inventory/resource management tool). By default, it installs a copy of the GPL. According to the Porter's Handbook, a port should avoid installing copies of the GPL. Whilst it's fairly easy to adapt the port so it doesn't install the license file, the installed web pages include at least one hyperlink to the file (I haven't done a complete check). What is the preferred mechanism for handling this? - Ignore the Porter's Handbook and install the file anyway - Create a symlink to an existing copy of the GPL. (In which case, where do I find a GPL that will always exist) - Change the hyperlink to point to a copy of the GPL on the Internet - something else. It wouldn't hurt to install the file anyway, but if you'd like to try to following the Porter's Handbook recommendations more closely, making a symlink to /usr/src/gnu/COPYING is going to provide you with the GPLv2 license text, presuming /usr/src is available on the machine in question. I don't think the third option is a good idea-- if the license for the software requires one to make the license text available, then it should be available from the same machine which the software is on. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: emacs-22.0.99_1
On Aug 21, 2007, at 2:21 AM, Giorgos Keramidas wrote:
Anyway, did you have a specific concern about GPLv3?
I was mostly concerned about local patches which we have 'backported'
from CVS trunk of GNU Emacs to the editors/emacs port, to unbreak GTK+
builds.
Should we sign papers with the FSF to 'distribute' builds of this
port?
Do we need to change anything from the way we handled GPLv2
versions of
GNU Emacs in the Ports tree? .. and so on.
The FSF probably would like people who *submit* substantial patches
to GNU projects to sign a contributor agreement, but of course one
doesn't have to do so in order to use, modify, or even redistribute
GPLv{2,3}'ed code.
It might be the case that pinging [EMAIL PROTECTED] would provide
you authoritative feedback from them rather than just my random
opinion :-)
--
-Chuck
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: emacs-22.0.99_1
On Aug 20, 2007, at 3:02 AM, Giorgos Keramidas wrote: [ ... ] I apologize for leaving the port stale for so long, but it's a fairly big moving target right now, with the release of GNU Emacs 22.2 in the works. Thanks for your work on the Emacs port, Giorgos. The integration of the patches may require a bit of care though, since a lot of GNU software has switched to GPLv3 and I am a bit unsure about the proper way to integrate GPLv3 code with our Ports tree. Emacs and GNU tar have switched; gcc will move with 4.3 (.0, or perhaps 4.3.3 [depending on how silly someone is about bumping version #'s]); but most of the other utilities seem to be waiting until their next normal feature release before changing the license terms over. Anyway, did you have a specific concern about GPLv3? -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
On Jul 26, 2007, at 4:14 PM, Kurt Abahar wrote: I'm trying to find a way to keep the ports tree synchronized with that from which the latest packages in packages-6-stable were built. Is there a way to accomplish this? Sure, you probably want something like portupgrade -P or portupgrade -PP options. Note that if you have reason to select non-default options, you're better off building the ports locally to suit your preferences... -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Openoffice.org-2-RC and bison conflicts
On Jun 18, 2007, at 3:59 PM, Clint Olsen wrote: I'm trying to install openoffice, and some sub-portion of the port is installing bison2, and later it tries to install bison and then it complains about conflicting ports. How is one supposed to deal with sub-port conflicts like these? Why do we /ever/ allow ports to have conflicts with other ports? Two ports which install files to the same place conflict-- you can't have two different versions of a file at the same path location. With some work, it is possible to install multiple versions of some ports (like Perl, Berkeley DB, GNU autoconf, etc) using a version # suffix, and symlink the version you prefer to the unqualified name: % ls -l /usr/local/bin/perl5 lrwxr-xr-x 1 root wheel 24 Mar 23 2006 /usr/local/bin/perl5@ - / usr/local/bin/perl5.8.8 ...but it doesn't magically happen. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Openoffice.org-2-RC and bison conflicts
On Jun 18, 2007, at 4:33 PM, Clint Olsen wrote: [ ... ] % ls -l /usr/local/bin/perl5 lrwxr-xr-x 1 root wheel 24 Mar 23 2006 /usr/local/bin/perl5@ - / usr/local/bin/perl5.8.8 ...but it doesn't magically happen. Ok, so I'm required to resolve this myself if I want to install this port? It's likely that the maintainer of OpenOffice can provide help/ suggestions. They'll probably want to know the release of FreeBSD you are running and maybe the list of installed ports on your machine... -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't cd to...
Joffrey Audin wrote: Hi, Hi-- I have a problems with lots of ports. Ex in gnome-games : #make install clean make all-recursive make all in po cd: can't cd to po *** Error code 1 Stop in /usr/ports/games/gnome-games/work/gnome-games-2.18.1 I have this problem with lots of ports and to my 'autotools' too. the 'cd' doesn't work. But not all, today, xorg-lib. update correctly Where is the bug please ?? What does which make tell you, and is it a GNU make or the BSD make? The ports tree expects to run with BSD make, and will invoke GNU make for various ports if the maintainer decided that the individual port needs or prefers to do so. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: email addresses and spam
On May 24, 2007, at 12:02 PM, Walter Ian Kaye wrote: All right, who released my email address to spammers? Nobody. Spammers routinely search for email addresses by scraping Google, websites, mailing list archives, and even word-list dictionaries or random number generators. I send mail to [EMAIL PROTECTED], and 2 weeks later I get spam. That is not cool, people. You MUST make sure that never happens. Now I have to blacklist this address. Sheesh. Welcome to the Internet, as (presumably!) you are new here. The FreeBSD postmaster already spends a lot of resources to try to keep these mailing lists (mostly) spam-free, but there's nothing that we can do to prevent a spammer from sending email to you after you've chosen to make your email address available by sending mail to a public list, and this is going to be true of other mailing lists elsewhere, web forums, Usenet, and so forth. Most people deal with spam by setting up some combination of MTA checking, greylisting, and spam-filtering via Amavis/SpamAssassin/ dspam/ClamAV/etc rather than creating new email addresses, but you can do as you see fit. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
