Re: where to install kld ports
Juergen Lock ha scritto: > The upside would be that the kld wouldn't be deleted > by installkernel I don't think they are deleted, the modules directory is not replaced on installkernel. If the kld is needed at boot time by loader it cannot stay in /usr/local, but probably kqemu can be loaded later. -- 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: openoffice 2 (RC, devel) broken
From: Oliver Lehmann <[EMAIL PROTECTED]> Subject: openoffice 2 (RC, devel) broken Date: Wed, 14 Feb 2007 06:01:49 +0100 > Hi, > > openoffice.org-2 > openoffice.org-2-RC > openoffice.org-2-devel > > is broken on amd64 (running 6.2-PRERELEASE): > > > g++41 -O -shared -Wl,-soname -Wl,libicuio.so.36 -o > ../lib/libicuio.so.36.0 locbund.o ufile.o ufmt_cmn.o uprintf.o uprntf_p.o > uscanf.o uscanf_p.o ustdio.o sprintf.o sscanf.o ustream.o ucln_io.o -L../lib > -licuuc -L../lib -L../stubdata -licudata -L../lib -licui18n -lpthread -lm > /usr/bin/ld: > /usr/local/lib/gcc-4.1.2/gcc/x86_64-portbld-freebsd6.2/4.1.2/../../../libstdc++.a(ios_init.o): > relocation R_X86_64_32 can not be used when making a shared object; > recompile with -fPIC > /usr/local/lib/gcc-4.1.2/gcc/x86_64-portbld-freebsd6.2/4.1.2/../../../libstdc++.a: > could not read symbols: Bad value > collect2: ld returned 1 exit status Hmm, I don't know. Recently I'm verifying the build with 6.2-RELEASE/amd64. Does anybody have same error? -- NAKATA, Maho ([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: default postgresql 7.4 -> 8.1, OK?
14 feb 2007 kl. 05.29 skrev Ade Lovett: On Feb 13, 2007, at 09:17 , Koen Martens wrote: I'm all in favour of this. Any specific reason you're not moving to the 8.2.x branch? 8.2.x isn't really stable enough yet for Joe User to pick it up when they want postgresql support for random-port. I'm definitely in favor of making 8.1.x the default version, and would go a little further, and suggest putting in a suitable deprecation date (say 12 months for 74 and 6 months for 80). 8.0->8.1 is pretty straightforward, whereas there are definitely folks who need to stick with 7.x for a while, hence the difference in expiration dates. Hello Ade, Good thinking! Will do that as well. Cheers, Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
openoffice 2 (RC, devel) broken
Hi, openoffice.org-2 openoffice.org-2-RC openoffice.org-2-devel is broken on amd64 (running 6.2-PRERELEASE): g++41 -O -shared -Wl,-soname -Wl,libicuio.so.36 -o ../lib/libicuio.so.36.0 locbund.o ufile.o ufmt_cmn.o uprintf.o uprntf_p.o uscanf.o uscanf_p.o ustdio.o sprintf.o sscanf.o ustream.o ucln_io.o -L../lib -licuuc -L../lib -L../stubdata -licudata -L../lib -licui18n -lpthread -lm /usr/bin/ld: /usr/local/lib/gcc-4.1.2/gcc/x86_64-portbld-freebsd6.2/4.1.2/../../../libstdc++.a(ios_init.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc-4.1.2/gcc/x86_64-portbld-freebsd6.2/4.1.2/../../../libstdc++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[1]: *** [../lib/libicuio.so.36.0] Error 1 rm sscanf.ao uscanf.ao uscanf_p.ao ustream.ao locbund.ao ucln_io.ao sprintf.ao uprintf.ao uprntf_p.ao ustdio.ao ufile.ao ufmt_cmn.ao gmake[1]: Leaving directory `/mnt/movies/usr/ports/editors/openoffice.org-2-devel/work/SRC680_m203/icu/unxfbsdx.pro/misc/build/icu/source/io' gmake: *** [all-recursive] Error 2 dmake: Error code 2, while making 'unxfbsdx.pro/misc/build/so_built_so_icu' ---* tg_merge.mk *--- ERROR: Error 65280 occurred while making /mnt/movies/usr/ports/editors/openoffice.org-2-devel/work/SRC680_m203/icu dmake: Error code 1, while making 'build_instsetoo_native' ---* *--- *** Error code 255 Stop in /usr/ports/editors/openoffice.org-2-devel. Exit 1 -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
On Feb 13, 2007, at 09:17 , Koen Martens wrote: I'm all in favour of this. Any specific reason you're not moving to the 8.2.x branch? 8.2.x isn't really stable enough yet for Joe User to pick it up when they want postgresql support for random-port. I'm definitely in favor of making 8.1.x the default version, and would go a little further, and suggest putting in a suitable deprecation date (say 12 months for 74 and 6 months for 80). 8.0->8.1 is pretty straightforward, whereas there are definitely folks who need to stick with 7.x for a while, hence the difference in expiration dates. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How does portupgrade -ar work?
On Mon, 12 Feb 2007 21:13:50 +0100 Uwe Laverenz <[EMAIL PROTECTED]> wrote: > On Mon, Feb 12, 2007 at 08:30:58PM +0100, Lars Stokholm wrote: > > > First of all, is it safe to just use 'portupgrade -a' or should I > > use 'portupgrade -ar'. > > 'portupgrade -a' is sufficient and in fact is not different from '-ar' > or '-arR'. If you take a look at the source of portupgrade (just read > the script file) you will see that as soon as '-a' is specified, the > options '-r' and '-R' are ignored/switched off. > > > Secondly, I've seen people use 'portupgrade -arR', but isn't that > > completely unnessesary? > > Yes. > > > updated, and an upgrade was required: libiconv and libslang. Would > > portupgrade be intelligent enough to upgrade both before upgrading > > slrn > > Yes. > > > Are there (other?) problems with using 'portupgrade -ar'? > > No, but you can use just '-a', there really is no difference. > One exception to all this is that -FaR is a bit more thorough than -Fa at fetching distfiles. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
where to install kld ports
Hi! I received a request (with patch) to install kqemu-kmod in /usr/local/modules like fusefs-kmod does. Other klds, like nivdia-driver, still install into /boot/modules, so I wonder what is better... The upside would be that the kld wouldn't be deleted by installkernel, the downsides I can see are 1. additional steps to be done by the user (see /usr/ports/sysutils/fusefs-kmod/pkg-message) and 2. users may forget to rebuild the kld after upgrading the kernel, which may be needed depending on what changed in the new kernel. So, what do you ppl think? Thanx, Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: multimedia/kbtv: broken saa kmod?
On Tuesday 13 February 2007 04:09, Yuri Pankov wrote: > Hi, > > I've attached a patch allowing saa kmod to compile cleanly on amd64 with > WERROR defined. > > I don't use kbtv but am interested in saa713x driver, so improvements to > make it work in SECAM are welcome. Just setting SECAM video standard to get > colour picture seems pretty easy, given the code in > saa/saa/support/set_videoopt.c. Diff adding SECAM option to it is also > attached. Thanks. Should be in the driver really, so that GETVIDEOSTD provides it. > > Another question - is anyone successfully running this driver on -CURRENT? > I'm wondering cause of the following change by imp@ to iicbus.c, denying > attach of generic iic device: > > === > RCS file: /usr/local/www/cvsroot/FreeBSD/src/sys/dev/iicbus/iicbus.c,v > retrieving revision 1.21 > retrieving revision 1.22 > diff -u -p -r1.21 -r1.22 > > > > @@ -139,51 +139,52 @@ iicbus_attach(device_t dev) > printf("\n"); > #endif > > - /* attach any known device */ > device_add_child(dev, "ic", -1); > - device_add_child(dev, "iic", -1); > device_add_child(dev, "iicsmb", -1); Outch. I would think yes, this would be a problem (I don't run 7-current yet). BTW, I did notice that iic(4) behaves different than its manpage says. At least with the (mk3) tuner programming I found that write command doesn't automagically takes care of start/stop conditions. I really must START first (and write first cmd) then after that can use write. The Philips tuner documentation also specifically says first start then optionally write/read then stop. I see the same in Rohit's tuning code (plus some bus resets). In the kbtv saa module I only reset the bus at tuner/IF init, not while changing channels. Sometimes it loses its way and tunes to 0 MHz but fortunately it can then be correctly tuned again. I recall Rohit's ftvv app having a button "restart IF" or something alike the meaning of which I only understood much later :) Dan > - > +#if 0 > + /* attach any known device */ > + device_add_child(dev, "iic", -1); > +#endif > bus_generic_attach(dev); > - > return (0); > } > > > > > HTH, > Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
On Tue, Feb 13, 2007 at 09:33:11PM +0100, Palle Girgensohn wrote: > >Won't it break something? :) > > Of course it will... ;^) > > But I don't think that it will break anything more badly than what > can be fixed by a portupgrade -rf postgresql-server.. Also, the > default postgresql version setting only kicks in when there is no > postgresql installed. If you use prebuilt packages, you should really > always portupgrade -rf, I guess... I mean at the compile stage. We can toss this on a future pointyhat build if you like Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
On Feb 13, 2007, at 2:00 PM, Kris Kennaway wrote: On Tue, Feb 13, 2007 at 04:37:00PM +0100, Palle Girgensohn wrote: Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? Won't it break something? :) It might. But ports that *demand* 7.4 should prominently declare that, adn the simple fix is to install postgres before any other ports, so you can pick the version you want. 8.1 should be the default, if not 8.2... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
13 feb 2007 kl. 20.00 skrev Kris Kennaway: On Tue, Feb 13, 2007 at 04:37:00PM +0100, Palle Girgensohn wrote: Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? Won't it break something? :) Of course it will... ;^) But I don't think that it will break anything more badly than what can be fixed by a portupgrade -rf postgresql-server.. Also, the default postgresql version setting only kicks in when there is no postgresql installed. If you use prebuilt packages, you should really always portupgrade -rf, I guess... /Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
13 feb 2007 kl. 18.17 skrev Koen Martens: Palle Girgensohn wrote: Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? I'm all in favour of this. Any specific reason you're not moving to the 8.2.x branch? I'm really just beeing modestly conservative, but the 8.2 branch is really too young to be the default branch, IMO. /Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
math/ATLAS upgrade fails Benchmarking xzllttst
I am duplicating Karsten Rothemund's earlier post, as my error message is identical except for timing numbers: Unfortunately I only have the last few lines (because of the portupgrade): 10 cases: 10 passed, 0 skipped, 0 failed Benchmarking xcllttstF NREPS UPLO Nlda TIMEMFLOPS RESID = = = = 1 Lower100100 0.0 0.000 6.688674e-03 1 Lower200200 0.02719 396.642 4.398721e-03 1 Lower300300 0.07179 505.188 2.341770e-03 1 Lower400400 0.15059 569.836 2.147220e-03 1 Lower500500 0.28906 579.186 2.432632e-03 1 Lower600600 0.48022 601.979 1.839629e-03 1 Lower700700 0.76107 602.840 1.436337e-03 1 Lower800800 1.13554 602.873 1.535296e-03 1 Lower900900 1.59588 610.590 9.815540e-04 1 Lower 1000 1000 2.18219 612.381 1.306027e-03 10 cases: 10 passed, 0 skipped, 0 failed Benchmarking xzllttst NREPS UPLO Nlda TIMEMFLOPS RESID = = = = assertion ATL_zpotrf(CblasColMajor, Uplo, N, A, lda) == 0 failed, line 344 of file ../llttst.c *** Error code 255 Stop in /usr/ports/math/atlas. *** Error code 1 Stop in /usr/ports/math/atlas. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.72539.60 e nv UPGRADE_TOOL=portupgrade UPGRADE_PORT=atlas-3.6.0,1 UPGRADE_PORT_VER=3.6.0,1 make ** Fix the problem and try again. It was in the THREADED_PIC run of the compilation. Since this appears to be an error in the benchmark / test software rather than in ATLAS proper, I'm thinking of removing the test from the Makefile and trying again. However, doing this sort of thing is more an act of desperation than a well-thought-out strategy for success. Any suggestions would be greatly appreciated. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
On Tue, Feb 13, 2007 at 04:37:00PM +0100, Palle Girgensohn wrote: > Hi! > > As the maintainer of the PostgreSQL ports, I'm planning a move to set the > 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which > starts to get a bit rusty. > > Any objections? Won't it break something? :) Kris pgpd0Eg8GUWTB.pgp Description: PGP signature
x11-toolkits/wxgtk26: fatal error: had to relocate PCH
Hi ! Please Cc: me in your replies. I'm trying to install multimedia/vlc on my 3 month-old -CURRENT, and I got the following error while compiling one of its dependency (x11-toolkits/wxgtk26): % g++ -c -o xmldll_xml.o -I.pch/wxprec_xmldll -D__WXGTK__ -DwxUSE_GUI=0 -DWXUSINGDLL -DWXMAKINGDLL_XML -fPIC -DPIC -DWX_PRECOMP -DNO_GCC_PRAGMA -DGTK_NO_CHECK_CASTS -Ilib/wx/include/gtk2-ansi-release-2.6 -I./include -D_REENTRANT -DXTHREADS -DXUSE_MTSAFE_API -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -I/usr/X11R6/include -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -I/usr/local/include/gstreamer-0.8 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml2 -I/usr/local/include -O2 -fno-strict-aliasing -pipe -march=pentium-m -D_THREAD_SAFE -Wall -Wundef -Wno-ctor-dtor-privacy ./src/xml/xml.cpp % ./src/xml/xml.cpp:1: fatal error: had to relocate PCH I've tried to compile it with gcc-4.1, it breaks as well but earlier: it stumbles on src/common/archive.cpp. Any clue will be welcome. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: default postgresql 7.4 -> 8.1, OK?
Go for it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Palle Girgensohn Sent: Tuesday, February 13, 2007 9:37 AM To: [EMAIL PROTECTED] Subject: default postgresql 7.4 -> 8.1, OK? Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? /Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
Palle Girgensohn wrote: > Hi! > > As the maintainer of the PostgreSQL ports, I'm planning a move to set > the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, > which starts to get a bit rusty. > > Any objections? I'm all in favour of this. Any specific reason you're not moving to the 8.2.x branch? Gr, Koen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[solved] Re: Need help with porting tvtime - uses video4linux (was [Fwd: Re: Porting a Linux application to FreeBSD])
On Tue, 13 Feb 2007, Florent Thoumie wrote: [EMAIL PROTECTED] wrote: On Tue, 13 Feb 2007, Florent Thoumie wrote: Garrett Cooper wrote: Hello Florent, I was given your name after some corresponding on the ports@ list because I am trying to port a "video4linux enabled" application to FreeBSD. I was wondering if you maybe had any tips on the API or ideas, where I could possibly take the video4linux stuff and convert it to FreeBSD native lib calls, etc? There's no conversion to make. If you write a port, just make sure to depend on the multimedia/v4l_compat port. That should be everything you need to do. Cheers. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer Ok. (Sorry for the extra question but) how do I include that library then? Thanks for the help! -Garrett Check this post from Luigi: http://article.gmane.org/gmane.os.freebsd.devel.ports/65664 -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer Sounds good. Thanks :)! -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ruby segfaults on FreeBSD 6.2 + tidy-lib-070211
Cheers, I use the tidy/Ruby bridge on FreeBSD 6.2 to filter html mails. I have tidy-lib-070211 and Ruby 1.8.5 installed. Ruby dies with this output: Command died with signal 6: "/usr/local/bin/ruby". Command output: /usr/local/www/www.doktormail.org/current/script/../config/../vendor/plugins/tidy-1.1.2/lib/tidy/tidybuf.rb:39: [BUG] Segmentation fault ruby 1.8.5 (2006-12-25) [i386-freebsd6] This is a recent thing so I suspect that it has to do with my tidy-lib/Ruby version but I wanted to ask if this is something known. Regards, Jonathan -- Jonathan Weiss http://blog.innerewut.de ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default postgresql 7.4 -> 8.1, OK?
Palle Girgensohn wrote: > Hi! > > As the maintainer of the PostgreSQL ports, I'm planning a move to set > the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, > which starts to get a bit rusty. I vote for the change. Thanks! Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
default postgresql 7.4 -> 8.1, OK?
Hi! As the maintainer of the PostgreSQL ports, I'm planning a move to set the 8.1.x branch as the default version for FreeBSD. Now it is 7.4, which starts to get a bit rusty. Any objections? /Palle Index: Mk/bsd.database.mk === RCS file: /opt/ncvs/ports/Mk/bsd.database.mk,v retrieving revision 1.17 diff -u -r1.17 bsd.database.mk --- Mk/bsd.database.mk 6 Dec 2006 16:48:56 - 1.17 +++ Mk/bsd.database.mk 13 Feb 2007 15:35:55 - @@ -40,7 +40,7 @@ #necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. -#Default: 74. +#Default: 81. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by #using it. @@ -147,7 +147,7 @@ .endif # USE_MYSQL .if defined(USE_PGSQL) -DEFAULT_PGSQL_VER?=74 +DEFAULT_PGSQL_VER?=81 PGSQL73_LIBVER=3 PGSQL74_LIBVER=3 PGSQL80_LIBVER=4 ___ 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: rancid-2.3.1_1
If possible, the 2.3.2a7 release. Aaron -Original Message- From: Aaron Dudek (adudek) Sent: Tuesday, February 13, 2007 9:58 To: 'Mohacsi Janos' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: FreeBSD Port: rancid-2.3.1_1 Yes, that is correct, the alpha version. Aaron -Original Message- From: Mohacsi Janos [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 3:47 To: Aaron Dudek (adudek) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: rancid-2.3.1_1 Hi Aaron, What do you mean by getting rancid-dev version ? You would need the alpha release? Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning and Projects NIIF/HUNGARNET, HUNGARY Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882 On Mon, 12 Feb 2007, Aaron Dudek (adudek) wrote: > Janos, > > Is there a possibility of getting a racid-dev version? > > Thanks > Aaron > ___ 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: rancid-2.3.1_1
Yes, that is correct, the alpha version. Aaron -Original Message- From: Mohacsi Janos [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 3:47 To: Aaron Dudek (adudek) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: rancid-2.3.1_1 Hi Aaron, What do you mean by getting rancid-dev version ? You would need the alpha release? Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning and Projects NIIF/HUNGARNET, HUNGARY Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882 On Mon, 12 Feb 2007, Aaron Dudek (adudek) wrote: > Janos, > > Is there a possibility of getting a racid-dev version? > > Thanks > Aaron > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gtk-2.10.9 doesn't compile
Please find attached the complete tarred log of gtk failed compilation. Ciao Vittorio -- Messaggio inoltrato -- Subject: Re: gtk-2.10.9 doesn't compile Date: 18:06, lunedì 12 febbraio 2007 From: "Jeremy Messenger" <[EMAIL PROTECTED]> To: Vittorio <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] On Mon, 12 Feb 2007 06:52:05 -0600, Vittorio <[EMAIL PROTECTED]> wrote: > Dear All, > > Under a fresh installation of 6.2 I recently updated via > portsnap the ports tree and recompiled what was needed (including > portupgrade!), BUT after issuing as root: > > portupgrade gtk > I obtain the > following obscure, esoteric diagnostic: > You have cutted out the important part. In general, it is always best to send a FULL log. While I am here, please follow this: http://www.freebsd.org/gnome/docs/bugging.html Cheers, Mezz > gmake[2]: Leaving > directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.9/gdk' > gmake > [1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.9' > gmake: *** [all] Error > 2 > *** Error code 2 > > Stop in /usr/ports/x11-toolkits/gtk20. > ** Command > failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.55166.1 env > UPGRADE_TOOL=portupgrade UPGRADE_PORT=gtk-2.10.7 UPGRADE_PORT_VER=2. > 10.7 make > ** Fix the problem and try again. > > > What shall I do? > Ciao from Rome - Vittorio > > Ciao > Vittorio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gtk-2.10.9 doesn't compile
As requested, please find attached the complete, tarred log of gtk failed compilation. Ciao Vittorio -- Messaggio inoltrato -- Subject: Re: gtk-2.10.9 doesn't compile Date: 18:06, lunedì 12 febbraio 2007 From: "Jeremy Messenger" <[EMAIL PROTECTED]> To: Vittorio <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] On Mon, 12 Feb 2007 06:52:05 -0600, Vittorio <[EMAIL PROTECTED]> wrote: > Dear All, > > Under a fresh installation of 6.2 I recently updated via > portsnap the ports tree and recompiled what was needed (including > portupgrade!), BUT after issuing as root: > > portupgrade gtk > I obtain the > following obscure, esoteric diagnostic: > You have cutted out the important part. In general, it is always best to send a FULL log. While I am here, please follow this: http://www.freebsd. org/gnome/docs/bugging.html Cheers, Mezz > gmake[2]: Leaving > directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.9/gdk' > gmake > [1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.9' > gmake: *** [all] Error > 2 > *** Error code 2 > > Stop in /usr/ports/x11-toolkits/gtk20. > ** Command > failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.55166.1 env > UPGRADE_TOOL=portupgrade UPGRADE_PORT=gtk-2.10.7 UPGRADE_PORT_VER=2. > 10.7 make > ** Fix the problem and try again. > > > What shall I do? > Ciao from Rome - Vittorio > > Ciao > Vittorio -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot compile Firefox
On 13/02/07, Lars Eighner <[EMAIL PROTECTED]> wrote: uname -a output: FreeBSD goodwill.6dollardialup.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Makefile variables: PORTNAME= firefox DISTVERSION=2.0.0.1 PORTREVISION= 1 PORTEPOCH= 1 Crash message: [...] ype -lz -lpango-1.0 -lm -lXrender -lX11 -lXext -lgobject-2.0 -lgmodule-2.0 -lgli b-2.0 -liconv -L/usr/X11R6/lib -lXt -lX11 -Wl,-Bsymbolic -lc -lm -pthread -pt hread -L/usr/local/lib -liconv /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x1b6): In function `gtk_c ontainer_class_init': : undefined reference to `libintl_dgettext' /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x1c9): In function /`gtk_container_class_init': : undefined reference to `libintl_dgettext' /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x203): In function /`gtk_container_class_init': /usr/X11R6/lib/libgtk-x11-2.0.a(gtkmenubar.o)(.text+0x278): more undefined references to `libintl_dgettext' follow /usr/X11R6/lib/libgdk_pixbuf-2.0.a(gdk-pixdata.o)(.text+0xb26): In function `IA_ _gdk_pixbuf_from_pixdata': : undefined reference to `libintl_ngettext' gmake[2]: *** [libgtkxtbin.so] Error 1 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla/widget/src/gtkx tbin' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.61663.0 en v UPGRADE_TOOL=portupgrade UPGRADE_PORT=firefox-2.0_2,1 UPGRADE_PORT_VER=2.0_2,1 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! www/firefox (firefox-2.0_2,1) (linker error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed with a freshly cvsup'd ports tree I forced a reinstall of gettext and gt20 (although portupgrade thought they were current) but the attempt to upgrade firefox ended in exactly the same way. Any ideas? GTK was moved into LOCALBASE back when GNOME 2.16.1 entered the ports tree. Your error messages relate to a GTK lib in /usr/X11R6, which could explain why you still get the failures even though you've reinstalled gettext and gtk. I would try moving the two .a files mentioned in the compile error out of /usr/X11R6 and see if the compile gets any further. Al -- WWW: http://ajs.no-dns-yet.org.uk GPG/PGP: http://ajs.no-dns-yet.org.uk/pubkey.gpg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cannot compile Firefox
uname -a output: FreeBSD goodwill.6dollardialup.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Makefile variables: PORTNAME= firefox DISTVERSION=2.0.0.1 PORTREVISION= 1 PORTEPOCH= 1 Crash message: [...] ype -lz -lpango-1.0 -lm -lXrender -lX11 -lXext -lgobject-2.0 -lgmodule-2.0 -lgli b-2.0 -liconv -L/usr/X11R6/lib -lXt -lX11 -Wl,-Bsymbolic -lc -lm -pthread -pt hread -L/usr/local/lib -liconv /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x1b6): In function `gtk_c ontainer_class_init': : undefined reference to `libintl_dgettext' /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x1c9): In function /`gtk_container_class_init': : undefined reference to `libintl_dgettext' /usr/X11R6/lib/libgtk-x11-2.0.a(gtkcontainer.o)(.text+0x203): In function /`gtk_container_class_init': /usr/X11R6/lib/libgtk-x11-2.0.a(gtkmenubar.o)(.text+0x278): more undefined references to `libintl_dgettext' follow /usr/X11R6/lib/libgdk_pixbuf-2.0.a(gdk-pixdata.o)(.text+0xb26): In function `IA_ _gdk_pixbuf_from_pixdata': : undefined reference to `libintl_ngettext' gmake[2]: *** [libgtkxtbin.so] Error 1 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla/widget/src/gtkx tbin' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Stop in /usr/ports/www/firefox. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.61663.0 en v UPGRADE_TOOL=portupgrade UPGRADE_PORT=firefox-2.0_2,1 UPGRADE_PORT_VER=2.0_2,1 make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! www/firefox (firefox-2.0_2,1) (linker error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed with a freshly cvsup'd ports tree I forced a reinstall of gettext and gt20 (although portupgrade thought they were current) but the attempt to upgrade firefox ended in exactly the same way. Any ideas? -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: rancid-2.3.1_1
Hi Aaron, What do you mean by getting rancid-dev version ? You would need the alpha release? Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning and Projects NIIF/HUNGARNET, HUNGARY Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882 On Mon, 12 Feb 2007, Aaron Dudek (adudek) wrote: Janos, Is there a possibility of getting a racid-dev version? Thanks Aaron ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Port marked as IGNORE: java/diablo-jre15" though not trying to upgrade
Despite having already installed diablo-jre15 and despite it not needing an upgrade, if I delete the distfile, I get this when running 'portupgrade -a': ** Port marked as IGNORE: java/diablo-jre15: :\n Because of licensing restrictions, you must fetch the distribution\n manually. Please access\n \n http://www.FreeBSDFoundation.org/cgi-bin/download ?download=diablo-latte-freebsd6-i386-1.5.0_07-b01.tar.bz2\n \n with a web browse r and \"Accept\" the End User License Agreement for\n \"Latte Diablo 1.5.0\". P lease place the downloaded\n diablo-latte-freebsd6-i386-1.5.0_07-b01.tar.bz2 in /usr/ports/distfiles.\n I would have expected this message, if portversion showed that diablo-jre15 needed an upgrade, but as I said, it doesn't. One way around it is to keep the distfile, but it seems kind of stupid if that's the only reason. Is there a real solution for this? Perhaps there's something wrong with portupgrade? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Impending update to devel/gettext
I tried your gettext 0.16.1 patch, and ran into problems as I have sysutils/coreutils installed with NLS enabled. The issue is that coreutils installs a /usr/local/bin/gmkdir which uses the gettext library. An upgrade of gettext fails as the gettext configure process prefers gmkdir over mkdir, but the deinstall deletes the gettext library, so the subsequent install can't work as gmkdir doesn't work without the old library being installed! The correct fix is probably a patch to the gettext configure script to disable the check for gmkdir. Thanks, Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"