Re: Proposition: make x11/nvidia-driver independent of misc/compat5x
On Sat, Oct 27, 2007 at 10:53:30PM -0200, Carlos A. M. dos Santos wrote: On 10/27/07, Carlos A. M. dos Santos [EMAIL PROTECTED] wrote: On 10/27/07, Alex Kozlov [EMAIL PROTECTED] wrote: On Sat, Oct 27, 2007 at 11:33:46AM -0200, Carlos A. M. dos Santos wrote: Hello, Using the patch below it is possible to make x11/nvidia-driver independent of misc/compat5x, by means of some library mapping. I did this successfuly on 6.x but still did not test on 7.x. I would like to hear some comments before submitting a PR with a change request. What is the problem using compat5x in the first place? I think this is more correct variant: $cat /etc/libmap.conf #nvidia-driver [/usr/local/lib/libGL.so.1] libm.so.3 libm.so.4 [/usr/local/lib/libXvMCNVIDIA.so.1] libc.so.5 libc.so.6 [/usr/local/lib/libXvMCNVIDIA_dynamic.so.1] libc.so.5 libc.so.6 [/usr/local/lib/libnvidia-cfg.so.1] libm.so.3 libm.so.4 Ah, I forgot that one. Good catch. [/usr/local/lib/xorg/modules/libwfb.so] libm.so.3 libm.so.4 librpcsvc.so.2 librpcsvc.so.3 That's potentially unsafe to put next .so version of library when the code expects previous one. It *may* work, but be prepared for all sorts of incompatibilities and ABI breakage. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems S Tracker Resp. Description f ports/117270[UPDATE] net/asterisk-addons to 1.4.4 1 problem total. Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode f ports/108077www/linux-flashplugin9 crashes linux-firefox f ports/108413net/vnc does not works. f ports/112385sysutils/lookupd on Kernel 64 f ports/112921x11-wm/Beryl not loading focus and keybinding settings f ports/113144print/ghostscript-gnu dumps core with several output d f ports/115818Executable clash between databases/grass and ruby gems f ports/115967enable chrooted net/isc-dhcp3-server on the FreeBSD 7. f ports/116378xorg 7.3 on -stable breaks math/scilab f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/116586net/isc-dhcp3-server does not work when compiled with f ports/116753multimedia/MPlayer crashes after playing *.flv on 7.0- f ports/116777The math/scilab port fails in demos-signal-bode. f ports/116778security/nmap ping-scan misses some hosts f ports/116949security/vpnc: Some Cisco Concentrators refuse Connect o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117119new port: emulators/dboxfe, a front-end to DosBox conf f ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/117144sysutils/nut : ACL with IPv6 address rejected o ports/117145[PATCH] math/dislin - update to 9.2 f ports/117196Port net/asterisk-addons 1.4.2 fails to compile o ports/117263audio/libtunepimp-old is broken f ports/117541textproc/Wordnet checksum error 24 problems total. Non-critical problems S Tracker Resp. Description f ports/101166bittorrent-curses only works under English locales. o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM a ports/107447[patch] devel/sdl12 - Add devel/directfb support f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut f ports/111399print/ghostscript-gpl: ghostscript-gpl WITH_FT_BRIDGE f ports/111456[UPDATE] finance/pfpro updated distinfo f ports/112887net/nxserver 1.4.0_1 fails to compile after upgrading f ports/113423Update for ports net/freenx to version 0.6.0 f ports/114127net/vnc - vnc.so installed to bad location f ports/114825pam module security/pam_abl not working s ports/115216ADA devel/florist exit_process program doesn't compile s ports/115217Ada devel/florist socket program doesn't compile due t f ports/115304multimedia/gpac-mp4box cannot import files larger than f ports/115336port multimedia/avifile on FreeBSD 7.0 not BROKEN with f ports/115401Update port: graphics/ipe Version 6.0pre28 of Ipe that f ports/115627www/Lynx (-ssl) does not correctly test for OpenSSL o ports/115654[UPDATE] devel/sdl12 to 1.2.12 o ports/115656[UPDATE] graphics/sdl_ttf to 2.0.9 o ports/115657[UPDATE] net/sdl_net to 1.2.7 o ports/115658[UPDATE] audio/sdl_mixer to 1.2.8 o
RE: FreeBSD Port: postgresql-server-8.2.5_2
I have 8.2.5 running on a 7/amd64 box without issue... $ psql Welcome to psql 8.2.5, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit ler=# select version(); version -- PostgreSQL 8.2.5 on amd64-portbld-freebsd7.0, compiled by GCC cc (GCC) 4.2.1 20 070719 [FreeBSD] (1 row) ler=# select version(); version -- PostgreSQL 8.2.5 on amd64-portbld-freebsd7.0, compiled by GCC cc (GCC) 4.2.1 20070719 [FreeBSD] (1 row) ler=# -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ivan Voras Sent: Saturday, October 27, 2007 3:02 PM To: freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: postgresql-server-8.2.5_2 Michael wrote: Hello. PostgreSQL 8.2.5 compiled from ports core dumps on freebsd 7 (RELENG_7), i've asked pgsql-bugs about this issue, and they answered, that probably FreeBSD 7 have problems with spinlocks: http://archives.postgresql.org/pgsql-bugs/2007-10/msg00197.php Postmaster isn't threaded so it looks like a problem with their own implementation of spinlock, not the OS's. One thing that may or may not help you is: can you rebuild your (exact!) version of PostgreSQL on a 6.2 machine, save the output (e.g. with tee), then rebuild it (the *same* version) on 7.0 and also save the output, then compare them? Can you help me resolve this problem? Did you look at the postmaster's stderror output? For what is worth, PostgreSQL 8.1 works on 7 flawlessly. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: nessus-2.2.9_1
Hi, I'm curious if there will be a nession version 3 in the ports someday. I hope that you can give me the answer. With regards, Ruud Boon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: print/fontforge: link failure on amd64
I'm really not sure about it, but maybe Python needs rebuilding for that? Either that or I could look into seeing if there's an option to enable/disable Python support. I think by default it just auto-detects if Python is there and tries to use it if it is. Naram Qashat Andriy Gapon wrote: I have the following problem while building print/fontforge version 20071002 on FreeBSD 6.2-RELEASE-p6 amd64: *** Warning: Linking the shared library ../libfontforge.la against the *** static library /usr/local/lib/python2.5/config/libpython2.5.a is not portable! cc -shared .libs/autohint.o .libs/autosave.o ... /usr/local/lib/python2.5/config/libpython2.5.a -lutil -lpthread -lm /usr/local/lib/libintl.so -march=athlon64 -Wl,-soname -Wl,libfontforge.so.1 -o ../.libs/libfontforge.so.1 /usr/bin/ld: /usr/local/lib/python2.5/config/libpython2.5.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.5/config/libpython2.5.a: could not read symbols: Bad value gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/work/fontforge-20071002/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 Stop in /usr/ports/print/fontforge. I think that there either should be a PIC version of libpython2.5.a and that's what fontforge should link to or it should link to .so version of the library. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
rrdtool performance tuning
Dear colleagues, any hints to tune rrdtool with ~30k rrd files (approx 2k target devices)? machine is mostly IO-bound, showing 100% disk load with 8 or sometimes even 3 mB/s, 300-400 tps (it's 2 SATA300 disks in gmirror) Thanks in advance. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: [EMAIL PROTECTED] ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: print/fontforge: link failure on amd64
on 29/10/2007 15:08 Naram Qashat said the following: I'm really not sure about it, but maybe Python needs rebuilding for that? Either that or I could look into seeing if there's an option to enable/disable Python support. I think by default it just auto-detects if Python is there and tries to use it if it is. Just in case: there is already /usr/local/lib/python2.5/config/libpython2.5.so installed, I hacked Makefile to link against it and everything seems to be OK. Andriy Gapon wrote: I have the following problem while building print/fontforge version 20071002 on FreeBSD 6.2-RELEASE-p6 amd64: *** Warning: Linking the shared library ../libfontforge.la against the *** static library /usr/local/lib/python2.5/config/libpython2.5.a is not portable! cc -shared .libs/autohint.o .libs/autosave.o ... /usr/local/lib/python2.5/config/libpython2.5.a -lutil -lpthread -lm /usr/local/lib/libintl.so -march=athlon64 -Wl,-soname -Wl,libfontforge.so.1 -o ../.libs/libfontforge.so.1 /usr/bin/ld: /usr/local/lib/python2.5/config/libpython2.5.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.5/config/libpython2.5.a: could not read symbols: Bad value gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/work/fontforge-20071002/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 Stop in /usr/ports/print/fontforge. I think that there either should be a PIC version of libpython2.5.a and that's what fontforge should link to or it should link to .so version of the library. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openoffice - drawing block arrows broken?
Oliver Lehmann ha scritto: Can someone please try drawing a blockarrow with ooo 2.3.0 (editors/openoffice.org) and tell me if it works for him? It works for me. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: krb5 1.6.3 build ldl error on 7.0-BETA1/i386
In message [EMAIL PROTECTED], John Marshall writes:
John Marshall wrote:
I don't understand what this is doing, so I can't provide any diagnosis.
Sorry.
After hitting this error this morning, I updated the other out-of-date
ports on this system, and then attempted krb5 again. Same error.
The previous revision of this port (krb5-1.6.2_1) built without any
error on this system after the 7.0-BETA1 upgrade and has been running
fine for over a week.
rwsrv05# uname -vm
FreeBSD 7.0-BETA1 #0: Sat Oct 20 10:13:47 AEST 2007
[EMAIL PROTECTED]:/spare/obj/usr/src/sys/RWSRV05 i386
rwsrv05# pkg_version -Iv | grep -v '='
krb5-1.6.2_1 needs updating (index has 1.6.3_1)
rwsrv05# portmaster -D krb5-1.6.2_1
...
...
rm -f pkinit.so
building dynamic pkinit object
set -x; objlist=`set -x perl -p -e 'BEGIN { $SIG{__WARN__} = sub {die
@_} };
$e=$ARGV; $e =~ s/OBJS\...$//; s/^/ /; s/ $//; s/ / $e/g;' OBJS.SH`
libtool -
-mode=link cc -shared -o pkinit.so $objlist -R/usr/local/lib
-L../../../lib -lkrb5 -lcom_err -lk5crypto -ldl -lkrb5support -lcrypto
-lcrypto
+ set -x
+ perl -p -e BEGIN { $SIG{__WARN__} = sub {die @_} }; $e=$ARGV; $e =~
s/OBJS\...
$//; s/^/ /; s/ $//; s/ / $e/g; OBJS.SH
+ objlist= pkinit_accessor.so pkinit_srv.so pkinit_lib.so pkinit_clnt.so
pkinit_profile.so pkinit_identity.so pkinit_matching.so
pkinit_crypto_openssl.so
+ libtool --mode=link cc -shared -o pkinit.so pkinit_accessor.so
pkinit_srv.so pkinit_lib.so pkinit_clnt.so pkinit_profile.so
pkinit_identity.so pkinit_matching.so pkinit_crypto_openssl.so
-R/usr/local/lib -L../../../lib -lkrb5 -lcom_err -lk5crypto -ldl
-lkrb5support -lcrypto -lcrypto
mkdir .libs
cc -shared -o pkinit.so pkinit_accessor.so pkinit_srv.so pkinit_lib.so
pkinit_clnt.so pkinit_profile.so pkinit_identity.so pkinit_matching.so
pkinit_crypto_openssl.so
-L/usr/ports/security/krb5/work/krb5-1.6.3/src/lib -lkrb5 -lcom_err
-lk5crypto -ldl -lkrb5support -lcrypto -Wl,--rpath -Wl,/usr/local/lib
/usr/bin/ld: cannot find -ldl
gmake[1]: *** [pkinit.so] Error 1
gmake[1]: Leaving directory
`/usr/ports/security/krb5/work/krb5-1.6.3/src/plugin
s/preauth/pkinit'
gmake: *** [all-recurse] Error 1
*** Error code 2
Stop in /usr/ports/security/krb5.
=== make failed for security/krb5
=== Aborting update
Thank you for maintaining this port. I use it for Samba in a Windows
2003 Active Directory environment.
I just updated krb5 to 1.6.3 on two 6.2-RELEASE/i386 systems without any
error.
I don't have a second 7.0-BETA1 system to use for comparison.
This is not ports-mgmt tools related because I see the error even with a
manual make in the security/krb5 directory.
I'll check it out on my testbed system, which is currently booted to
6.2-STABLE on another problem.
--
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org
e**(i*pi)+1=0
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: parallel ports build
No responses yet so... *ping* :)
On Thu, October 18, 2007 18:50, Jonathan Noack wrote:
With most modern systems having 2+ cores, I was wondering if the ports
system could make use of more than one of them. I briefly searched the
web and list archives and found several short discussions and the
following page (cced author markus@):
http://www.brueffer.de/parallel_ports_build.html
The bsd.port.mk patch on that page is dated March 2004 (!) but looks
pretty simple. A port must set SUPPORTS_PARALLEL_BUILD=yes to allow a
parallel build. If it does, the BUILD_JOBS knob is used (either read from
/etc/make.conf, env, or defaults to 0) and -j${BUILD_JOBS} is passed to
make. As a bonus, the patch includes CC/CXX wrapper support for
ccache/distcc/etc.
Given that not all ports successfully build in parallel, the opt-in
approach seems reasonable. It allows port maintainers to test their ports
and update them if everything works well. Even a simple pass through the
ports tree focusing on the heavy-hitters (X, KDE, Gnome, Apache, PHP,
MySQL, Postgres, OpenOffice, etc.) and their dependencies could make a
significant dent in build time. This would be most evident for new
installs and upgrades where you are basically starting from scratch.
I am far from an expert in this area so I wanted to see what others
thought. Is this a good approach or is there a better one?
-Jon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
print/fontforge: link failure on amd64
I have the following problem while building print/fontforge version 20071002 on FreeBSD 6.2-RELEASE-p6 amd64: *** Warning: Linking the shared library ../libfontforge.la against the *** static library /usr/local/lib/python2.5/config/libpython2.5.a is not portable! cc -shared .libs/autohint.o .libs/autosave.o ... /usr/local/lib/python2.5/config/libpython2.5.a -lutil -lpthread -lm /usr/local/lib/libintl.so -march=athlon64 -Wl,-soname -Wl,libfontforge.so.1 -o ../.libs/libfontforge.so.1 /usr/bin/ld: /usr/local/lib/python2.5/config/libpython2.5.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.5/config/libpython2.5.a: could not read symbols: Bad value gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/work/fontforge-20071002/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 Stop in /usr/ports/print/fontforge. I think that there either should be a PIC version of libpython2.5.a and that's what fontforge should link to or it should link to .so version of the library. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
net/tightvnc, bsd.port.options,mk issues
Hi! net/tightvnc seem to be the first port to actually use bsd.port.options.mk, but AFAIK tha latter is broken for now: # cd /usr/ports/net/tightvnc make Makefile, line 41: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue options.mk should only work on forthcoming 6.3 and 7.0, as there's no /usr/share/mk/bsd.port.options.mk wrapper on existing versions. Please see this thread: http://www.mail-archive.com/freebsd-ports@freebsd.org/msg09949.html On my 6.1-RELEASE-p20 not only net/tightvnc does not build, but also pkg_version spits an error message: % pkg_version -v -l ' ... scummvm-0.10.0aneeds updating (port has 0.10.0a_1) setxkbmap-1.0.3needs updating (port has 1.0.4) Makefile, line 41: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue pkg_version: Failed to get PKGNAME from /usr/ports/net/tightvnc/Makefile! tightvnc-1.3.9 needs updating (index has 1.3.9_1) wine-0.9.44,1 needs updating (port has 0.9.48,1) ... -- Dmitry A. Marakasov| jabber: [EMAIL PROTECTED] [EMAIL PROTECTED] | http://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: net/tightvnc, bsd.port.options,mk issues
On Mon, 29 Oct 2007 21:48:53 +0300 Dmitry Marakasov [EMAIL PROTECTED] wrote: Hi! net/tightvnc seem to be the first port to actually use bsd.port.options.mk, but AFAIK tha latter is broken for now: # cd /usr/ports/net/tightvnc make Makefile, line 41: Could not find bsd.port.options.mk make: fatal errors encountered -- cannot continue options.mk should only work on forthcoming 6.3 and 7.0, as there's no /usr/share/mk/bsd.port.options.mk wrapper on existing versions. Yes,I know of the problem. I will have to back-out the usage of this nice file. Please see this thread: http://www.mail-archive.com/freebsd-ports@freebsd.org/msg09949.html On my 6.1-RELEASE-p20 not only net/tightvnc does not build, but also pkg_version spits an error message: [ .. ] Strictly speaking I don't think I'm required to have my ports running on anything else that -STABLE. But ... -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Re: print/fontforge: link failure on amd64
I'm using FreeBSD 6.2 on i386 and it links Python just fine with /usr/local/lib/python2.5/config/libpython2.5.a, so I suspect it has something to do with how Python gets built on an amd64. I don't have one to test it on, but have you tried rebuilding Python and then Fontforge? I just want to see if it's Python's fault, Fontforge's fault, or something weird with the way Fontforge's libtool is handling Python. I'm not even sure if Python is actually used by Fontforge either. I haven't looked into that. Naram Qashat Andriy Gapon wrote: on 29/10/2007 15:08 Naram Qashat said the following: I'm really not sure about it, but maybe Python needs rebuilding for that? Either that or I could look into seeing if there's an option to enable/disable Python support. I think by default it just auto-detects if Python is there and tries to use it if it is. Just in case: there is already /usr/local/lib/python2.5/config/libpython2.5.so installed, I hacked Makefile to link against it and everything seems to be OK. Andriy Gapon wrote: I have the following problem while building print/fontforge version 20071002 on FreeBSD 6.2-RELEASE-p6 amd64: *** Warning: Linking the shared library ../libfontforge.la against the *** static library /usr/local/lib/python2.5/config/libpython2.5.a is not portable! cc -shared .libs/autohint.o .libs/autosave.o ... /usr/local/lib/python2.5/config/libpython2.5.a -lutil -lpthread -lm /usr/local/lib/libintl.so -march=athlon64 -Wl,-soname -Wl,libfontforge.so.1 -o ../.libs/libfontforge.so.1 /usr/bin/ld: /usr/local/lib/python2.5/config/libpython2.5.a(abstract.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.5/config/libpython2.5.a: could not read symbols: Bad value gmake[1]: *** [../libfontforge.la] Error 1 gmake[1]: Leaving directory `/usr/ports/print/fontforge/work/fontforge-20071002/fontforge' gmake: *** [fontforge] Error 2 *** Error code 2 Stop in /usr/ports/print/fontforge. I think that there either should be a PIC version of libpython2.5.a and that's what fontforge should link to or it should link to .so version of the library. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysutils/screen -- INFO issue
In message [EMAIL PROTECTED], Pietro Cerutti writes:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig25037A9EB2B21A45B2ACF21A
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Dear Cy, dear list
here I am to talk about the INFO issue of sysutils/screen [screen].
To summarize:
screen has an option to [en|dis]able installation of an INFO page.
If the option is set, WITH_INFO gets set accordingly, otherwise the
port's Makefile sets the make argument NO_INFO.
In turn, ${WRKSRC}/doc/Makefile checks for NO_INFO, and if it's not set,
it prepares the INFO page for installation by running
makeinfo --no-split ./screen.texinfo -o screen.info
The problem is that make.conf(5) documents the variable NO_INFO under
the section BUILDING THE WORLD - The following list provides a name and
short description for variables that are used during the world build.
I think here we have a namespace collision problem for the variable NO_IN=
FO.
If NO_INFO is set in make.conf and the WITH_INFO option is enabled while
building screen, ${WRKSRC}/doc/Makefile won't prepare the info page but
the port's Makefile will try to install it anyway. This leads to a file
not found build error:
install-info --quiet /usr/local/info/screen.info /usr/local/info/dir
install-info: No such file or directory for /usr/local/info/screen.info
*** Error code 1
I suggest that we change ${WRKSRC}/doc/Makefile to check for WITH_INFO
(used within ports) instead of !NO_INFO (used while building the world).
In addition, we should change the port's Makefile to set the make
argument WITH_INFO if the option was chosen instead of setting NO_INFO
it it wasn't.
The same whole issue exists for the MAN page, for which I suggest the
same modifications in the port's Makefile and in ${WRKSRC}/doc/Makefile.
The following patches to the port's Makefile and for
files/patch-doc_Makefile.in implement the changes discussed above.
--- Makefile.orig 2007-10-29 19:18:41.0 +0100
+++ Makefile 2007-10-29 20:15:20.0 +0100
@@ -31,16 +31,14 @@
GNU_CONFIGURE=3D yes
.if defined(WITH_MAN)
MAN1=3D screen.1
-.else
-MAKE_ARGS+=3D-DNO_MAN
+MAKE_ARGS+=3D -DWITH_MAN
.endif
.if defined(WITH_INFO)
.if !exists(/usr/bin/install-info)
RUN_DEPENDS+=3D install-info:${PORTSDIR}/print/texinfo
.endif
INFO=3D screen
-.else
-MAKE_ARGS+=3D-DNO_INFO
+MAKE_ARGS+=3D -DWITH_INFO
.endif
.if ${ARCH} =3D=3D alpha
--- files/patch-doc_Makefile.in.orig 2007-10-29 19:40:13.0 +0100
+++ files/patch-doc_Makefile.in 2007-10-29 20:11:43.0 +0100
@@ -4,10 +4,10 @@
$(MAKEINFO) $(srcdir)/screen.texinfo -o screen.info
install: installdirs
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
$(INSTALL_DATA) $(srcdir)/screen.1 $(DESTDIR)$(mandir)/man1/screen.1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
-$(MAKE) screen.info
-if test -f screen.info; then d=3D.; else d=3D$(srcdir); fi; \
if test -f $$d/screen.info; then \
@@ -23,10 +23,10 @@
installdirs:
-$(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
$(DESTDIR)$(infodir)
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
+$(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
+$(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(infodir)
+.endif
I would greatly appreciate input / clarification / feedback / ideas on
the whole story before filling a PR.
What you're discussing is renaming NO_INFO and NO_MAN to WITHOUT_INFO and
WITHOUT_MAN (or comparing for non-definition of WITH_MAN and WITH_INFO).
Agreed something needs to be done about the namespace collision. There has
been some discussion of make.conf files for src/ports/doc/etc, which I
believe didn't result in any decision being made.
--
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org
e**(i*pi)+1=0
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysutils/screen -- INFO issue
In message [EMAIL PROTECTED], Pietro Cerutti writes:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigB8265C98D519CDAA1FC5B00B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cy Schubert wrote:
In message [EMAIL PROTECTED], Pietro Cerutti writes:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig25037A9EB2B21A45B2ACF21A
Content-Type: text/plain; charset=3DUTF-8
Content-Transfer-Encoding: quoted-printable
Dear Cy, dear list
here I am to talk about the INFO issue of sysutils/screen [screen].
To summarize:
screen has an option to [en|dis]able installation of an INFO page.
If the option is set, WITH_INFO gets set accordingly, otherwise the
port's Makefile sets the make argument NO_INFO.
In turn, ${WRKSRC}/doc/Makefile checks for NO_INFO, and if it's not se=
t,
it prepares the INFO page for installation by running
makeinfo --no-split ./screen.texinfo -o screen.info
The problem is that make.conf(5) documents the variable NO_INFO under
the section BUILDING THE WORLD - The following list provides a name a=
nd
short description for variables that are used during the world build.=
I think here we have a namespace collision problem for the variable NO=
_IN=3D
FO.
If NO_INFO is set in make.conf and the WITH_INFO option is enabled whi=
le
building screen, ${WRKSRC}/doc/Makefile won't prepare the info page bu=
t
the port's Makefile will try to install it anyway. This leads to a fi=
le
not found build error:
install-info --quiet /usr/local/info/screen.info /usr/local/info/dir
install-info: No such file or directory for /usr/local/info/screen.inf=
o
*** Error code 1
I suggest that we change ${WRKSRC}/doc/Makefile to check for WITH_INFO=
(used within ports) instead of !NO_INFO (used while building the world=
).
In addition, we should change the port's Makefile to set the make
argument WITH_INFO if the option was chosen instead of setting NO_INFO=
it it wasn't.
The same whole issue exists for the MAN page, for which I suggest the
same modifications in the port's Makefile and in ${WRKSRC}/doc/Makefil=
e.
The following patches to the port's Makefile and for
files/patch-doc_Makefile.in implement the changes discussed above.
--- Makefile.orig 2007-10-29 19:18:41.0 +0100
+++ Makefile 2007-10-29 20:15:20.0 +0100
@@ -31,16 +31,14 @@
GNU_CONFIGURE=3D3Dyes
.if defined(WITH_MAN)
MAN1=3D3D screen.1
-.else
-MAKE_ARGS+=3D3D -DNO_MAN
+MAKE_ARGS+=3D3D -DWITH_MAN
.endif
.if defined(WITH_INFO)
.if !exists(/usr/bin/install-info)
RUN_DEPENDS+=3D3D install-info:${PORTSDIR}/print/texinfo
.endif
INFO=3D3D screen
-.else
-MAKE_ARGS+=3D3D -DNO_INFO
+MAKE_ARGS+=3D3D -DWITH_INFO
.endif
.if ${ARCH} =3D3D=3D3D alpha
--- files/patch-doc_Makefile.in.orig 2007-10-29 19:40:13.0 +
01=
00
+++ files/patch-doc_Makefile.in2007-10-29 20:11:43.0 +0100
@@ -4,10 +4,10 @@
$(MAKEINFO) $(srcdir)/screen.texinfo -o screen.info
install: installdirs
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
$(INSTALL_DATA) $(srcdir)/screen.1 $(DESTDIR)$(mandir)/man1/screen.=
1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
-$(MAKE) screen.info
-if test -f screen.info; then d=3D3D.; else d=3D3D$(srcdir); fi; \
if test -f $$d/screen.info; then \
@@ -23,10 +23,10 @@
installdirs:
- $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
$(DESTDIR)$(infodir)
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(infodir)
+.endif
I would greatly appreciate input / clarification / feedback / ideas on=
the whole story before filling a PR.
=20
What you're discussing is renaming NO_INFO and NO_MAN to WITHOUT_INFO a=
nd=20
WITHOUT_MAN (or comparing for non-definition of WITH_MAN and WITH_INFO)=
=2E=20
Agreed something needs to be done about the namespace collision. There =
has=20
been some discussion of make.conf files for src/ports/doc/etc, which I =
believe didn't result in any decision being made.
This would also solve the problem. Do you have any argument supporting
the use of WITHOUT_* when an option is not set and against the use
WITH_* when the option is set?
My option would save a few lines of in the Makefile (you don't need an
=2Eelse branch).
Probably. I'll update the port. A documentation change to the porters handbook
should discuss this.
--
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org
e**(i*pi)+1=0
___
freebsd-ports@freebsd.org mailing list
Re: sysutils/screen -- INFO issue
Cy Schubert wrote:
In message [EMAIL PROTECTED], Pietro Cerutti writes:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig25037A9EB2B21A45B2ACF21A
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Dear Cy, dear list
here I am to talk about the INFO issue of sysutils/screen [screen].
To summarize:
screen has an option to [en|dis]able installation of an INFO page.
If the option is set, WITH_INFO gets set accordingly, otherwise the
port's Makefile sets the make argument NO_INFO.
In turn, ${WRKSRC}/doc/Makefile checks for NO_INFO, and if it's not set,
it prepares the INFO page for installation by running
makeinfo --no-split ./screen.texinfo -o screen.info
The problem is that make.conf(5) documents the variable NO_INFO under
the section BUILDING THE WORLD - The following list provides a name and
short description for variables that are used during the world build.
I think here we have a namespace collision problem for the variable NO_IN=
FO.
If NO_INFO is set in make.conf and the WITH_INFO option is enabled while
building screen, ${WRKSRC}/doc/Makefile won't prepare the info page but
the port's Makefile will try to install it anyway. This leads to a file
not found build error:
install-info --quiet /usr/local/info/screen.info /usr/local/info/dir
install-info: No such file or directory for /usr/local/info/screen.info
*** Error code 1
I suggest that we change ${WRKSRC}/doc/Makefile to check for WITH_INFO
(used within ports) instead of !NO_INFO (used while building the world).
In addition, we should change the port's Makefile to set the make
argument WITH_INFO if the option was chosen instead of setting NO_INFO
it it wasn't.
The same whole issue exists for the MAN page, for which I suggest the
same modifications in the port's Makefile and in ${WRKSRC}/doc/Makefile.
The following patches to the port's Makefile and for
files/patch-doc_Makefile.in implement the changes discussed above.
--- Makefile.orig2007-10-29 19:18:41.0 +0100
+++ Makefile 2007-10-29 20:15:20.0 +0100
@@ -31,16 +31,14 @@
GNU_CONFIGURE=3Dyes
.if defined(WITH_MAN)
MAN1=3D screen.1
-.else
-MAKE_ARGS+=3D -DNO_MAN
+MAKE_ARGS+=3D -DWITH_MAN
.endif
.if defined(WITH_INFO)
.if !exists(/usr/bin/install-info)
RUN_DEPENDS+=3D install-info:${PORTSDIR}/print/texinfo
.endif
INFO=3D screen
-.else
-MAKE_ARGS+=3D -DNO_INFO
+MAKE_ARGS+=3D -DWITH_INFO
.endif
.if ${ARCH} =3D=3D alpha
--- files/patch-doc_Makefile.in.orig 2007-10-29 19:40:13.0 +0100
+++ files/patch-doc_Makefile.in 2007-10-29 20:11:43.0 +0100
@@ -4,10 +4,10 @@
$(MAKEINFO) $(srcdir)/screen.texinfo -o screen.info
install: installdirs
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
$(INSTALL_DATA) $(srcdir)/screen.1 $(DESTDIR)$(mandir)/man1/screen.1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
-$(MAKE) screen.info
-if test -f screen.info; then d=3D.; else d=3D$(srcdir); fi; \
if test -f $$d/screen.info; then \
@@ -23,10 +23,10 @@
installdirs:
- $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
$(DESTDIR)$(infodir)
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(infodir)
+.endif
I would greatly appreciate input / clarification / feedback / ideas on
the whole story before filling a PR.
What you're discussing is renaming NO_INFO and NO_MAN to WITHOUT_INFO and
WITHOUT_MAN (or comparing for non-definition of WITH_MAN and WITH_INFO).
Agreed something needs to be done about the namespace collision. There has
been some discussion of make.conf files for src/ports/doc/etc, which I
believe didn't result in any decision being made.
This would also solve the problem. Do you have any argument supporting
the use of WITHOUT_* when an option is not set and against the use
WITH_* when the option is set?
My option would save a few lines of in the Makefile (you don't need an
.else branch).
--
Pietro Cerutti
PGP Public Key:
http://gahr.ch/pgp
signature.asc
Description: OpenPGP digital signature
sysutils/screen -- INFO issue
Dear Cy, dear list
here I am to talk about the INFO issue of sysutils/screen [screen].
To summarize:
screen has an option to [en|dis]able installation of an INFO page.
If the option is set, WITH_INFO gets set accordingly, otherwise the
port's Makefile sets the make argument NO_INFO.
In turn, ${WRKSRC}/doc/Makefile checks for NO_INFO, and if it's not set,
it prepares the INFO page for installation by running
makeinfo --no-split ./screen.texinfo -o screen.info
The problem is that make.conf(5) documents the variable NO_INFO under
the section BUILDING THE WORLD - The following list provides a name and
short description for variables that are used during the world build.
I think here we have a namespace collision problem for the variable NO_INFO.
If NO_INFO is set in make.conf and the WITH_INFO option is enabled while
building screen, ${WRKSRC}/doc/Makefile won't prepare the info page but
the port's Makefile will try to install it anyway. This leads to a file
not found build error:
install-info --quiet /usr/local/info/screen.info /usr/local/info/dir
install-info: No such file or directory for /usr/local/info/screen.info
*** Error code 1
I suggest that we change ${WRKSRC}/doc/Makefile to check for WITH_INFO
(used within ports) instead of !NO_INFO (used while building the world).
In addition, we should change the port's Makefile to set the make
argument WITH_INFO if the option was chosen instead of setting NO_INFO
it it wasn't.
The same whole issue exists for the MAN page, for which I suggest the
same modifications in the port's Makefile and in ${WRKSRC}/doc/Makefile.
The following patches to the port's Makefile and for
files/patch-doc_Makefile.in implement the changes discussed above.
--- Makefile.orig 2007-10-29 19:18:41.0 +0100
+++ Makefile2007-10-29 20:15:20.0 +0100
@@ -31,16 +31,14 @@
GNU_CONFIGURE= yes
.if defined(WITH_MAN)
MAN1= screen.1
-.else
-MAKE_ARGS+=-DNO_MAN
+MAKE_ARGS+= -DWITH_MAN
.endif
.if defined(WITH_INFO)
.if !exists(/usr/bin/install-info)
RUN_DEPENDS+= install-info:${PORTSDIR}/print/texinfo
.endif
INFO= screen
-.else
-MAKE_ARGS+=-DNO_INFO
+MAKE_ARGS+= -DWITH_INFO
.endif
.if ${ARCH} == alpha
--- files/patch-doc_Makefile.in.orig2007-10-29 19:40:13.0 +0100
+++ files/patch-doc_Makefile.in 2007-10-29 20:11:43.0 +0100
@@ -4,10 +4,10 @@
$(MAKEINFO) $(srcdir)/screen.texinfo -o screen.info
install: installdirs
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
$(INSTALL_DATA) $(srcdir)/screen.1 $(DESTDIR)$(mandir)/man1/screen.1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
-$(MAKE) screen.info
-if test -f screen.info; then d=.; else d=$(srcdir); fi; \
if test -f $$d/screen.info; then \
@@ -23,10 +23,10 @@
installdirs:
- $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
$(DESTDIR)$(infodir)
-+.if !defined(NO_MAN)
++.if defined(WITH_MAN)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(mandir)/man1
+.endif
-+.if !defined(NO_INFO)
++.if defined(WITH_INFO)
+ $(srcdir)/../etc/mkinstalldirs $(DESTDIR)$(infodir)
+.endif
I would greatly appreciate input / clarification / feedback / ideas on
the whole story before filling a PR.
Best Regards,
--
Pietro Cerutti
PGP Public Key:
http://gahr.ch/pgp
signature.asc
Description: OpenPGP digital signature
Re: krb5 1.6.3 build ldl error on 7.0-BETA1/i386
In message [EMAIL PROTECTED], Cy Schubert
writes:
In message [EMAIL PROTECTED], John Marshall writes:
John Marshall wrote:
I don't understand what this is doing, so I can't provide any diagnosis.
Sorry.
After hitting this error this morning, I updated the other out-of-date
ports on this system, and then attempted krb5 again. Same error.
The previous revision of this port (krb5-1.6.2_1) built without any
error on this system after the 7.0-BETA1 upgrade and has been running
fine for over a week.
rwsrv05# uname -vm
FreeBSD 7.0-BETA1 #0: Sat Oct 20 10:13:47 AEST 2007
[EMAIL PROTECTED]:/spare/obj/usr/src/sys/RWSRV05 i386
rwsrv05# pkg_version -Iv | grep -v '='
krb5-1.6.2_1 needs updating (index has 1.6.3_1)
rwsrv05# portmaster -D krb5-1.6.2_1
...
...
rm -f pkinit.so
building dynamic pkinit object
set -x; objlist=`set -x perl -p -e 'BEGIN { $SIG{__WARN__} = sub {die
@_} };
$e=$ARGV; $e =~ s/OBJS\...$//; s/^/ /; s/ $//; s/ / $e/g;' OBJS.SH`
libtool -
-mode=link cc -shared -o pkinit.so $objlist -R/usr/local/lib
-L../../../lib -lkrb5 -lcom_err -lk5crypto -ldl -lkrb5support -lcrypto
-lcrypto
+ set -x
+ perl -p -e BEGIN { $SIG{__WARN__} = sub {die @_} }; $e=$ARGV; $e =~
s/OBJS\...
$//; s/^/ /; s/ $//; s/ / $e/g; OBJS.SH
+ objlist= pkinit_accessor.so pkinit_srv.so pkinit_lib.so pkinit_clnt.so
pkinit_profile.so pkinit_identity.so pkinit_matching.so
pkinit_crypto_openssl.so
+ libtool --mode=link cc -shared -o pkinit.so pkinit_accessor.so
pkinit_srv.so pkinit_lib.so pkinit_clnt.so pkinit_profile.so
pkinit_identity.so pkinit_matching.so pkinit_crypto_openssl.so
-R/usr/local/lib -L../../../lib -lkrb5 -lcom_err -lk5crypto -ldl
-lkrb5support -lcrypto -lcrypto
mkdir .libs
cc -shared -o pkinit.so pkinit_accessor.so pkinit_srv.so pkinit_lib.so
pkinit_clnt.so pkinit_profile.so pkinit_identity.so pkinit_matching.so
pkinit_crypto_openssl.so
-L/usr/ports/security/krb5/work/krb5-1.6.3/src/lib -lkrb5 -lcom_err
-lk5crypto -ldl -lkrb5support -lcrypto -Wl,--rpath -Wl,/usr/local/lib
/usr/bin/ld: cannot find -ldl
gmake[1]: *** [pkinit.so] Error 1
gmake[1]: Leaving directory
`/usr/ports/security/krb5/work/krb5-1.6.3/src/plugin
s/preauth/pkinit'
gmake: *** [all-recurse] Error 1
*** Error code 2
Stop in /usr/ports/security/krb5.
=== make failed for security/krb5
=== Aborting update
Thank you for maintaining this port. I use it for Samba in a Windows
2003 Active Directory environment.
I just updated krb5 to 1.6.3 on two 6.2-RELEASE/i386 systems without any
error.
I don't have a second 7.0-BETA1 system to use for comparison.
This is not ports-mgmt tools related because I see the error even with a
manual make in the security/krb5 directory.
I'll check it out on my testbed system, which is currently booted to
6.2-STABLE on another problem.
Looks like under 6.2 a number of directories are skipped and are assumed to
be missing by the build process. This is why it fails under 7.0. I will
need to address the 6.2 issue first then address the libdl problem, which
will become a problem under 6.2 once I fix the missing directories
problem.
--
Cheers,
Cy Schubert [EMAIL PROTECTED]
FreeBSD UNIX: [EMAIL PROTECTED] Web: http://www.FreeBSD.org
e**(i*pi)+1=0
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
