problems building the latest ghostscript-gpl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Using the default options I get the following when attempting to rebuild the latest version of print/ghostscript-gpl on 8-CURRENT (AMD64): cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -pipe -march=nocona -fno-strict-aliasing -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript-gpl/work/ghostscript-8.62/jasper/src/libjasper/include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE=unsigned long int -O2 -pipe -march=nocona -fno-strict-aliasing -I./obj/../soobj -I./src -o ./obj/../soobj/gsromfs0.o -c ./src/gsromfs0.c ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib -L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o ./bin/../sobin/libgs.so.8.62 ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/gsromfs0.o ./obj/../soobj/gs.o -s cat ./obj/../soobj/ld.tr ./obj/../soobj/ldt.tr ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm -liconv -lstdc++ -L/usr/local/lib -lfontconfig -Wl,-export-dynamic -lm if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ ~XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ ~FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ ~DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ ~DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ ~DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ ~DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ ~DEVICE_DEVS_EXTRA= \ ~/bin/sh ./obj/../soobj/ldt.tr /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC ./obj/../soobj/gs.o: could not read symbols: Bad value gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1 gmake[1]: Leaving directory `/usr/ports/print/ghostscript-gpl/work/ghostscript-8.62' gmake: *** [so] Error 2 *** Error code 2 Stop in /usr/ports/print/ghostscript-gpl. *** Error code 1 Stop in /usr/ports/print/ghostscript-gpl. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkghXn4ACgkQk8GFzCrQm4BQUQCfc2ttbTBVDzOxk52Yr0afAGEu pRAAn0S8p5tTzaCbkUSxmUwsTnaI4AtR =Lvx/ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
On May 7, 2008, at 12:47 AM, Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Using the default options I get the following when attempting to rebuild the latest version of print/ghostscript-gpl on 8-CURRENT (AMD64): cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -pipe - march=nocona -fno-strict-aliasing -DUPD_SIGNAL=0 -I. -I/usr/ports/ print/ghostscript-gpl/work/ghostscript-8.62/jasper/src/libjasper/ include -I/usr/local/include/libpng -I/usr/local/include -Wall - Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing- prototypes -Wwrite-strings -Wno-strict-aliasing -fno-builtin -fno- common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE=unsigned long int -O2 -pipe -march=nocona -fno-strict-aliasing -I./obj/../soobj -I./src - o ./obj/../soobj/gsromfs0.o -c ./src/gsromfs0.c ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/ lib -L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o ./bin/../ sobin/libgs.so.8.62 ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/ gsromfs0.o ./obj/../soobj/gs.o -s cat ./obj/../soobj/ld.tr ./obj/../soobj/ldt.tr ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm -liconv - lstdc++ -L/usr/local/lib -lfontconfig -Wl,-export-dynamic -lm if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ ~XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ ~FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ ~DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ ~DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ ~DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ ~DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ ~DEVICE_DEVS_EXTRA= \ ~/bin/sh ./obj/../soobj/ldt.tr /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC ./obj/../soobj/gs.o: could not read symbols: Bad value gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1 gmake[1]: Leaving directory `/usr/ports/print/ghostscript-gpl/work/ ghostscript-8.62' gmake: *** [so] Error 2 *** Error code 2 Stop in /usr/ports/print/ghostscript-gpl. *** Error code 1 Stop in /usr/ports/print/ghostscript-gpl. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkghXn4ACgkQk8GFzCrQm4BQUQCfc2ttbTBVDzOxk52Yr0afAGEu pRAAn0S8p5tTzaCbkUSxmUwsTnaI4AtR =Lvx/ -END PGP SIGNATURE- Aryeh, What are your CFLAGS? -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Cooper wrote: | On May 7, 2008, at 12:47 AM, Aryeh M. Friedman wrote: | | Using the default options I get the following when attempting to rebuild the latest version of print/ghostscript-gpl on 8-CURRENT (AMD64): | | cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -pipe -march=nocona -fno-strict-aliasing -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript-gpl/work/ghostscript-8.62/jasper/src/libjasper/include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE=unsigned long int -O2 -pipe -march=nocona -fno-strict-aliasing -I./obj/../soobj -I./src -o ./obj/../soobj/gsromfs0.o -c ./src/gsromfs0.c | ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib -L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o ./bin/../sobin/libgs.so.8.62 | ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/gsromfs0.o ./obj/../soobj/gs.o -s | cat ./obj/../soobj/ld.tr ./obj/../soobj/ldt.tr | ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm -liconv -lstdc++ -L/usr/local/lib -lfontconfig -Wl,-export-dynamic -lm | if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ | ~XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ | ~FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ | ~DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ | ~DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ | ~DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ | ~DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ | ~DEVICE_DEVS_EXTRA= \ | ~/bin/sh ./obj/../soobj/ldt.tr | /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC | ./obj/../soobj/gs.o: could not read symbols: Bad value | gmake[1]: *** [bin/../sobin/libgs.so.8.62] Error 1 | gmake[1]: Leaving directory `/usr/ports/print/ghostscript-gpl/work/ghostscript-8.62' | gmake: *** [so] Error 2 | *** Error code 2 | | Stop in /usr/ports/print/ghostscript-gpl. | *** Error code 1 | | Stop in /usr/ports/print/ghostscript-gpl. | | Aryeh, | What are your CFLAGS? If you mean the ones from /etc/make.conf: CPUTYPE?=nocona KERNCONF=MONSTER NO_LPR=true NO_PROFILE=true NO_CLEAN=true # added by use.perl 2008-04-25 20:07:30 PERL_VER=5.8.8 PERL_VERSION=5.8.8 | -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkghYroACgkQk8GFzCrQm4A5PgCeKY4fY1wBdq1S2FoZSHO5wF5D GBgAoNbNzADeG5e9QGhw3z6opyUGQYYI =y2HR -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Cooper wrote: [...] | Aryeh, | What are your CFLAGS? If you mean the ones from /etc/make.conf: CPUTYPE?=nocona KERNCONF=MONSTER NO_LPR=true NO_PROFILE=true NO_CLEAN=true # added by use.perl 2008-04-25 20:07:30 PERL_VER=5.8.8 PERL_VERSION=5.8.8 | -Garrett I'd submit this info in a bug report. It looks like CFLAGS = -fno- strict-aliasing only. -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Little valgrind issue
On May 6, 2008, at 8:05 AM, Gé Weijers wrote: Hello, I tried to build 'valgrind' in a jail environment. The Makefile tries to make sure that /proc is mounted before it build valgrind, which is fine, but the way it does it won't work in a jail because / sbin/mount does not show anything useful. A quick workaround: define the environment variable 'PACKAGE_BUILDING=yes' and then run 'make' and 'make install' It would be better if the Makefile would just look for, say, the existence of '/proc/curproc' in stead of relying on /sbin/mount. Gé -- Gé Weijers [EMAIL PROTECTED] You should probably submit this as a bug report and notify the maintainer at: http://www.freebsdsoftware.org/devel/valgrind.html. -Garrett___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
On May 7, 2008, at 2:15 AM, Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Cooper wrote: | On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote: | | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Garrett Cooper wrote: | | [...] | | | Aryeh, | | What are your CFLAGS? | | If you mean the ones from /etc/make.conf: | | CPUTYPE?=nocona | KERNCONF=MONSTER | NO_LPR=true | NO_PROFILE=true | NO_CLEAN=true | # added by use.perl 2008-04-25 20:07:30 | PERL_VER=5.8.8 | PERL_VERSION=5.8.8 | | | -Garrett | | I'd submit this info in a bug report. It looks like CFLAGS = -fno- strict-aliasing only. Quick question PR or rbug report to the gs people? Also the options screen is a little screwy take a look at http://www.dnull.com/~aryeh/gsnapshot.png for a screenshot of it | -Garrett | Upstream bug report, unless it's tied down to a strictly FreeBSD environment. -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Cooper wrote: | On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote: | | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Garrett Cooper wrote: | | [...] | | | Aryeh, | | What are your CFLAGS? | | If you mean the ones from /etc/make.conf: | | CPUTYPE?=nocona | KERNCONF=MONSTER | NO_LPR=true | NO_PROFILE=true | NO_CLEAN=true | # added by use.perl 2008-04-25 20:07:30 | PERL_VER=5.8.8 | PERL_VERSION=5.8.8 | | | -Garrett | | I'd submit this info in a bug report. It looks like CFLAGS = -fno-strict-aliasing only. Quick question PR or rbug report to the gs people? Also the options screen is a little screwy take a look at http://www.dnull.com/~aryeh/gsnapshot.png for a screenshot of it | -Garrett | -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkghcxUACgkQk8GFzCrQm4C9DACcDqqCopby2iTc0nvK4k9+1Kui aVUAnjmfVq7qJQXlOGZlelb3F8rqaW6T =WhU9 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Little valgrind issue
On Tue, May 6, 2008 at 6:05 PM, Gé Weijers [EMAIL PROTECTED] wrote: Hello, I tried to build 'valgrind' in a jail environment. The Makefile tries to make sure that /proc is mounted before it build valgrind, which is fine, but the way it does it won't work in a jail because /sbin/mount does not show anything useful. A quick workaround: define the environment variable 'PACKAGE_BUILDING=yes' and then run 'make' and 'make install' It would be better if the Makefile would just look for, say, the existence of '/proc/curproc' in stead of relying on /sbin/mount. I'm very surprised. Just because unable to build valgring at all since FreeBSD-7.0... :-( (New threading implementation related issue?) -- Andrew W. Nosenko [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_7/i386 net/asterisk brokes when CPUTYPE set
Dear colleagues, net/asterisk from today's ports tree does not build at least under RELENG_7/i386 when CPUTYPE is set to (at least) k8 or i686 in /etc/make.conf: [LD] abstract_jb.o acl.o aescrypt.o aeskey.o aestab.o alaw.o app.o ast_expr2.o ast_expr2f.o asterisk.o astmm.o astobj2.o audiohook.o autoservice.o callerid.o cdr.o channel.o chanvars.o cli.o config.o cryptostub.o db.o devicestate.o dial.o dns.o dnsmgr.o dsp.o enum.o file.o fixedjitterbuf.o frame.o fskmodem.o global_datastores.o http.o image.o indications.o io.o jitterbuf.o loader.o logger.o manager.o md5.o netsock.o pbx.o plc.o privacy.o rtp.o say.o sched.o sha1.o slinfactory.o srv.o stdtime/localtime.o strcompat.o tdd.o term.o threadstorage.o translate.o udptl.o ulaw.o utils.o editline/libedit.a - asterisk astobj2.o(.text+0x221): In function `ao2_ref': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' astobj2.o(.text+0x4a8): In function `__ao2_link': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' astobj2.o(.text+0x4d8):/usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' astobj2.o(.text+0x975): In function `ao2_callback': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' astobj2.o(.text+0x9a3):/usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' channel.o(.text+0x30b4):/usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: more undefined references to `__sync_fetch_and_add_4' follow manager.o(.text+0x32a): In function `free_session': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1147: undefined reference to `__sync_sub_and_fetch_4' manager.o(.text+0x1837): In function `process_events': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1147: undefined reference to `__sync_sub_and_fetch_4' manager.o(.text+0x1bfd): In function `accept_thread': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' manager.o(.text+0x4b50): In function `action_waitevent': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1147: undefined reference to `__sync_sub_and_fetch_4' manager.o(.text+0x6e5e): In function `generic_http_callback': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' manager.o(.text+0x6e6c):/usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' utils.o(.text+0xdd4): In function `ast_atomic_dec_and_test': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1147: undefined reference to `__sync_sub_and_fetch_4' utils.o(.text+0xded): In function `ast_atomic_fetchadd_int': /usr/ports/net/asterisk/work/asterisk-1.4.18.1/include/asterisk/lock.h:1101: undefined reference to `__sync_fetch_and_add_4' gmake[1]: *** [asterisk] Error 1 gmake: *** [main] Error 2 *** Error code 2 Stop in /usr/ports/net/asterisk. *** Error code 1 Stop in /usr/ports/net/asterisk. 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: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
On Tue, May 6, 2008 at 12:32 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Tue, May 06, 2008 at 12:20:17AM -0500, Matt wrote: The symptom is as described above - the gvfs-fuse-daemon processes do not exit cleanly and more processes continue to build-up whenever I complete an X-session. The processes do exit when I send them a manual kill signal. The only info I have at this point is a backtrace from a stuck process. Hopefully it will be useful in identifying the issue. What makes it stuck? What state is the process in? ps or top output would've been helpful, ditto with truss or ktrace output. Is it eating 100% CPU (e.g. read() is continually being called without handling error conditions), or does it just sit there idling? Sorry - should have been more specific than the generic stuck description. Top shows the process state as fu_msg and it is not consuming any processor resources, just seemingly sits there idling. Output from ps is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1000 4019 1 0 44 0 6324 2528 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto Attaching the process with truss when it enters this state (which happens after I end an X-session) yields no data. Are there any truss command line switches that I should try? I've tried -f, -a and -e. Attaching the process with ktrace yields very minimal data. The only time I can get the process to show something in the trace is when I attach it with gdb while the trace is running. When I do that, kdump shows this: [EMAIL PROTECTED] ~]$ kdump 4019 gvfs-fuse-daemon CALL read(0x3,0x1055c000,0x21000) 4019 gvfs-fuse-daemon RET read RESTART 4019 gvfs-fuse-daemon CALL read(0x3,0x1055c000,0x21000) 4019 gvfs-fuse-daemon RET read RESTART 4019 gvfs-fuse-daemon CALL read(0x3,0x1055c000,0x21000) 4019 gvfs-fuse-daemon RET read RESTART [EMAIL PROTECTED] ~]$ Each pair of CALL and RET lines represents one attaching of the process via gdb and executing the bt command within gdb. The system is a dual-core Opteron running 7.0-RELEASE i386 with the ULE scheduler. There does not appear to be any detrimental side effects to the system with the gvfs-fuse-daemon processes hanging around. They just keep stacking up (one for each X-session, so usually one per day) until I manually kill them off. (gdb) bt #0 0x1045d3d1 in read () from /lib/libc.so.7 #1 0x10379792 in read () from /lib/libthr.so.3 #2 0x1035a67b in fuse_kern_chan_receive (chp=0xbf9fef8c, buf=0x1055c000 , size=135168) at fuse_kern_chan.c:28 #3 0x1035fb13 in fuse_chan_recv (chp=0xbf9fef8c, buf=0x1055c000 , size=135168) at fuse_session.c:184 #4 0x1035aac6 in fuse_do_work (data=0x10517580) at fuse_loop_mt.c:70 #5 0x1037ab1f in pthread_getprio () from /lib/libthr.so.3 #6 0x in ?? () ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
On Wed, 7 May 2008, Aryeh M. Friedman wrote: /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC On amd64, you need to remove the FT_BRIDGE option to compile. I have not had time to look into what is actually happening or needs to be fixed. Sean -- [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: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: Sorry - should have been more specific than the generic stuck description. Top shows the process state as fu_msg and it is not consuming any processor resources, just seemingly sits there idling. Output from ps is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1000 4019 1 0 44 0 6324 2528 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto The T flag under State says that the process is stopped. It's as if the process was running in the foreground, and was ^Z'd -- same behaviour. The part which confuses me (I'm sure others can explain this part) is that the parent PID is 1, which is init. This would indicate that the process is actually a zombie whose parent has been killed off, and the child's parent has been assigned to init. You might try doing a kill -CONT on the process to see what happens. I don't think truss or ktrace are going to help here, because something is explicitly stopping the process (SIGSTOP or some other means). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
On Wed, May 7, 2008 at 9:48 AM, Robert Noland [EMAIL PROTECTED] wrote: On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: Sorry - should have been more specific than the generic stuck description. Top shows the process state as fu_msg and it is not consuming any processor resources, just seemingly sits there idling. Output from ps is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1000 4019 1 0 44 0 6324 2528 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto The T flag under State says that the process is stopped. It's as if the process was running in the foreground, and was ^Z'd -- same behaviour. I don't want to state the obvious, but attaching to the process with gdb will produce the stopped state. Was this ps snap taken before or after attaching with gdb? My fault - bad order of info gathering. Here's a ps snap after sending the process -CONT signal: [EMAIL PROTECTED] ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs robert. The part which confuses me (I'm sure others can explain this part) is that the parent PID is 1, which is init. This would indicate that the process is actually a zombie whose parent has been killed off, and the child's parent has been assigned to init. You might try doing a kill -CONT on the process to see what happens. I don't think truss or ktrace are going to help here, because something is explicitly stopping the process (SIGSTOP or some other means). ___ 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: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
On Wed, May 7, 2008 at 9:53 AM, Matt [EMAIL PROTECTED] wrote: On Wed, May 7, 2008 at 9:48 AM, Robert Noland [EMAIL PROTECTED] wrote: On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: Sorry - should have been more specific than the generic stuck description. Top shows the process state as fu_msg and it is not consuming any processor resources, just seemingly sits there idling. Output from ps is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1000 4019 1 0 44 0 6324 2528 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto The T flag under State says that the process is stopped. It's as if the process was running in the foreground, and was ^Z'd -- same behaviour. I don't want to state the obvious, but attaching to the process with gdb will produce the stopped state. Was this ps snap taken before or after attaching with gdb? My fault - bad order of info gathering. Here's a ps snap after sending the process -CONT signal: [EMAIL PROTECTED] ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs Darn it - bad paste. Trying again: [EMAIL PROTECTED] ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Is??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 fu_msg Is??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs robert. The part which confuses me (I'm sure others can explain this part) is that the parent PID is 1, which is init. This would indicate that the process is actually a zombie whose parent has been killed off, and the child's parent has been assigned to init. You might try doing a kill -CONT on the process to see what happens. I don't think truss or ktrace are going to help here, because something is explicitly stopping the process (SIGSTOP or some other means). ___ 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: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck
On Wed, May 07, 2008 at 10:22:09AM -0500, Matt wrote: On Wed, May 7, 2008 at 9:53 AM, Matt [EMAIL PROTECTED] wrote: On Wed, May 7, 2008 at 9:48 AM, Robert Noland [EMAIL PROTECTED] wrote: On Wed, 2008-05-07 at 07:30 -0700, Jeremy Chadwick wrote: On Wed, May 07, 2008 at 09:19:24AM -0500, Matt wrote: Sorry - should have been more specific than the generic stuck description. Top shows the process state as fu_msg and it is not consuming any processor resources, just seemingly sits there idling. Output from ps is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1000 4019 1 0 44 0 6324 2528 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto The T flag under State says that the process is stopped. It's as if the process was running in the foreground, and was ^Z'd -- same behaviour. I don't want to state the obvious, but attaching to the process with gdb will produce the stopped state. Was this ps snap taken before or after attaching with gdb? My fault - bad order of info gathering. Here's a ps snap after sending the process -CONT signal: [EMAIL PROTECTED] ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 - Ts??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs Darn it - bad paste. Trying again: [EMAIL PROTECTED] ~]$ ps -axlH | grep vfs 1000 4019 1 0 46 0 6324 2412 uwait Is??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs 1000 4019 1 0 44 0 6324 2412 fu_msg Is??0:00.00 /usr/local/libexec//gvfs-fuse-daemon /home/mtosto/.gvfs Now can you run truss or ktrace on PID 4019? The previous time you ran ktrace/truss, the process was suspended and the event name was -, so no syscalls seen makes sense. This may end up being one of those situations where one needs to launch gvfs-fuse-daemon via truss -o /tmp/truss.out -f gvfs-fuse-daemon args, to see what it's doing from initial startup to the time it idles. -a and -D might also come in handy here. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trying for a duplex printer
On Tue, 06 May 2008 12:43:08 -0400 Chuck Robey [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have been scouring all the data I can, to find printers that do duplex printing (that means doublesided printing). I found 3 models, but two of them (the HP C7280 and the Canon PIXMA MX850) have no public drivers I can find. The third, which is the Epson RX680, seems to be supported via drivers from Avasys (http://avasys.jp/hp/menu00900/hpg00859.htm) called PIPS drivers, but while there is are ports for various versions of PIPS in the print dir of ports, and I can find that the Avasys site lists supporting the RX680, I have two problems: 1) I can't determine which (if any) of the PIPS ports support the RX680, and 2) right now, none of them build because of an error you get about a linuxwrapper not handling symbol versioning. Is there any way to rely on any FreeBSD port to be able to use the RX680 from Epson? I'm using a Kyocera FS-1030D (the 'D' means duplex). Yes, it works. It works just fine with CUPS. It could be that one of the printers which you're looking at would also work with CUPS. What you need to find is a PPD file which describes your printer. Mine uses Kyocera_FS-1030_en.ppd. There's a Linux-specific site which has these PPDs available, which is pretty easy to find with google. --- Gary Jennejohn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems building the latest ghostscript-gpl
On Wednesday 07 May 2008 17:13:59 Sean C. Farley wrote: On Wed, 7 May 2008, Aryeh M. Friedman wrote: /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC On amd64, you need to remove the FT_BRIDGE option to compile. I have not had time to look into what is actually happening or needs to be fixed. Makes no difference here, I get the same error with: _OPTIONS_READ=ghostscript-gpl-8.62_1 WITHOUT_FONTCONFIG=true WITHOUT_FT_BRIDGE=true WITHOUT_GS_lvga256=true WITHOUT_GS_vgalib=true . . all other items are WITH_foo=true -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [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: problems building the latest ghostscript-gpl
On Wed, 7 May 2008, Andy Fawcett wrote: On Wednesday 07 May 2008 17:13:59 Sean C. Farley wrote: On Wed, 7 May 2008, Aryeh M. Friedman wrote: /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC On amd64, you need to remove the FT_BRIDGE option to compile. I have not had time to look into what is actually happening or needs to be fixed. Makes no difference here, I get the same error with: _OPTIONS_READ=ghostscript-gpl-8.62_1 WITHOUT_FONTCONFIG=true WITHOUT_FT_BRIDGE=true WITHOUT_GS_lvga256=true WITHOUT_GS_vgalib=true . . all other items are WITH_foo=true That is what I have. Maybe a rebuild of freetype2 (v2.3.5 here) would help? Are you using a port builder that sets the environment variable BATCH and have portconf installed? That may bypass the setting in the options file. Those are my only guesses. Sean -- [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: problems building the latest ghostscript-gpl
On Wednesday 07 May 2008 19:42:31 Sean C. Farley wrote: On Wed, 7 May 2008, Andy Fawcett wrote: On Wednesday 07 May 2008 17:13:59 Sean C. Farley wrote: On Wed, 7 May 2008, Aryeh M. Friedman wrote: /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC On amd64, you need to remove the FT_BRIDGE option to compile. I have not had time to look into what is actually happening or needs to be fixed. Makes no difference here, I get the same error with: _OPTIONS_READ=ghostscript-gpl-8.62_1 WITHOUT_FONTCONFIG=true WITHOUT_FT_BRIDGE=true WITHOUT_GS_lvga256=true WITHOUT_GS_vgalib=true . . all other items are WITH_foo=true That is what I have. Maybe a rebuild of freetype2 (v2.3.5 here) would help? Are you using a port builder that sets the environment variable BATCH and have portconf installed? That may bypass the setting in the options file. Those are my only guesses. I'm using portupgrade, BATCH is not set, portconf isn't installed, and all dependency ports are up to date. This is with a csup just before I sent the mail, so pretty up to date. Andy -- Andy Fawcett | [EMAIL PROTECTED] | [EMAIL PROTECTED] In an open world without walls and fences, | [EMAIL PROTECTED] we wouldn't need Windows and Gates. -- anon | [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: Little valgrind issue
On May 7, 2008, at 4:04 AM, Andrew W. Nosenko wrote: On Tue, May 6, 2008 at 6:05 PM, Gé Weijers [EMAIL PROTECTED] wrote: Hello, I tried to build 'valgrind' in a jail environment. The Makefile tries to make sure that /proc is mounted before it build valgrind, which is fine, but the way it does it won't work in a jail because /sbin/mount does not show anything useful. A quick workaround: define the environment variable 'PACKAGE_BUILDING=yes' and then run 'make' and 'make install' It would be better if the Makefile would just look for, say, the existence of '/proc/curproc' in stead of relying on /sbin/mount. I'm very surprised. Just because unable to build valgring at all since FreeBSD-7.0... :-( (New threading implementation related issue?) -- Andrew W. Nosenko [EMAIL PROTECTED] ... or because of the new compiler and its relevant libc link-ins? -Garrett___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trying for a duplex printer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Jeremy wrote: On Tue, May 06, 2008 at 12:43:08PM -0400, Chuck Robey wrote: 1) I can't determine which (if any) of the PIPS ports support the RX680, and Based on a quick look at the pips ports, the RX680 is not currently supported. I suspect it wouldn't be terribly difficult to get running. 2) right now, none of them build because of an error you get about a linuxwrapper not handling symbol versioning. This is a bigger issue. The linuxpluginwrapper maintainer is not responding to emails about it so I doubt it will get fixed anytime soon. I've had a quick look at it and decided that I don't understand enough about how the symbol aliasing used to work or how the symbol versioning broke it. So, I guess that means that if I want to get this printer working, I either have to try to fix that myself, or forget using FreeBSD to print with that Epson RX680? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIfLaz62J6PPcoOkRAoh7AKCFjJO4ELi6JgSoD3oODy528u5BMACeIkF9 iFrorlnzPcPAemBym36Abyo= =ibUA -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trying for a duplex printer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Jennejohn wrote: On Tue, 06 May 2008 12:43:08 -0400 Chuck Robey [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have been scouring all the data I can, to find printers that do duplex printing (that means doublesided printing). I found 3 models, but two of them (the HP C7280 and the Canon PIXMA MX850) have no public drivers I can find. The third, which is the Epson RX680, seems to be supported via drivers from Avasys (http://avasys.jp/hp/menu00900/hpg00859.htm) called PIPS drivers, but while there is are ports for various versions of PIPS in the print dir of ports, and I can find that the Avasys site lists supporting the RX680, I have two problems: 1) I can't determine which (if any) of the PIPS ports support the RX680, and 2) right now, none of them build because of an error you get about a linuxwrapper not handling symbol versioning. Is there any way to rely on any FreeBSD port to be able to use the RX680 from Epson? I'm using a Kyocera FS-1030D (the 'D' means duplex). Yes, it works. It works just fine with CUPS. It could be that one of the printers which you're looking at would also work with CUPS. What you need to find is a PPD file which describes your printer. Mine uses Kyocera_FS-1030_en.ppd. There's a Linux-specific site which has these PPDs available, which is pretty easy to find with google. --- Gary Jennejohn -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIfZpz62J6PPcoOkRAjI2AJ96uxdoX1ZhAimAFEotkeNTMU2FEwCgl8vB ps34akd9ZgHXwN0bjAM3Vf4= =tYlI -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trying for a duplex printer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Jennejohn wrote: On Tue, 06 May 2008 12:43:08 -0400 Chuck Robey [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have been scouring all the data I can, to find printers that do duplex printing (that means doublesided printing). I found 3 models, but two of them (the HP C7280 and the Canon PIXMA MX850) have no public drivers I can find. The third, which is the Epson RX680, seems to be supported via drivers from Avasys (http://avasys.jp/hp/menu00900/hpg00859.htm) called PIPS drivers, but while there is are ports for various versions of PIPS in the print dir of ports, and I can find that the Avasys site lists supporting the RX680, I have two problems: 1) I can't determine which (if any) of the PIPS ports support the RX680, and 2) right now, none of them build because of an error you get about a linuxwrapper not handling symbol versioning. Is there any way to rely on any FreeBSD port to be able to use the RX680 from Epson? I'm using a Kyocera FS-1030D (the 'D' means duplex). Yes, it works. It works just fine with CUPS. It could be that one of the printers which you're looking at would also work with CUPS. What you need to find is a PPD file which describes your printer. Mine uses Kyocera_FS-1030_en.ppd. There's a Linux-specific site which has these PPDs available, which is pretty easy to find with google. Thanks, Gary. Took me quite a while to find this baby, because it seems that Kyocera's main site doesn't acknowledge of the Kyocera-Mita's products. I finally found out that it's a fairly big monochrome laser. I rather like the color I get from the cheaper inkjets, although I sure would rather get one with a FreeBSD driver. Further, from what I could find, I couldn't tell if it was a postscript native printer, and I am dead-set against any postscript native printers, because I used to have one, and when compared to any innkset that must use a translator such as ghostscript, the postscript native printers are (or, at least used to be) dead slow. Maybe it took them too long to transfer big postscript files, or maybe it took the internal processors too long to translate, I dunno, but when I had one of the original old HP laserjets with a postscript cartridge, and I converted to using ghostscript about a year after I got it, I was shocked that my print rate went up about 4-5 times as fast. I could actually get the advertised print rates. I suppose my next trick is to attempt to find out about glib's symbol versioning, enough so that it could be added to the linuxwrapper. Then (I hope) I get the PIPS driver that exists for the Epson RX680. --- Gary Jennejohn -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIfhUz62J6PPcoOkRArz4AKCR7giZyxfH6iju6U1L08uq1vigBwCgnxtd nzQqaTxkCmkxW4d5kXfZQhM= =hMy6 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
perl5.8 - perlio.c:2919: error: dereferencing pointer to incomplete type
`sh cflags optimize='-O2 -pipe -march=pentiumpro -fno-strict-aliasing' globals.o` -DPIC -fPIC globals.c CCCMD = cc -DPERL_CORE -c -DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.8/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -O2 -pipe -march=pentiumpro -fno-strict-aliasing -Wall `sh cflags optimize='-O2 -pipe -march=pentiumpro -fno-strict-aliasing' perlio.o` -DPIC -fPIC perlio.c CCCMD = cc -DPERL_CORE -c -DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.8/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -O2 -pipe -march=pentiumpro -fno-strict-aliasing -Wall perlio.c: In function 'PerlIOStdio_invalidate_fileno': perlio.c:2919: error: dereferencing pointer to incomplete type *** Error code 1 am i doing something wrong? randy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cfengine port update?
Yes, they updated the port yesterday apparently. On May 6, 2008, at 12:34 AM, Boris Samorodov wrote: My tinderbox gives: - phase 7: make package === Building package for cfengine-2.2.6 Creating package /tmp/packages/All/cfengine-2.2.6.tbz Registering depends: db46-4.6.21.1. Creating bzip'd tar ball in '/tmp/packages/All/cfengine-2.2.6.tbz' Deleting cfengine-2.2.6 === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 65830181 12 -r--r--r--1 root wheel4788 May 6 07:25 usr/local/man/man8/cfagent.8 658301824 -r--r--r--1 root wheel 764 May 6 07:25 usr/local/man/man8/cfenvd.8 658301834 -r--r--r--1 root wheel1441 May 6 07:25 usr/local/man/man8/cfenvgraph.8 658301844 -r--r--r--1 root wheel 774 May 6 07:25 usr/local/man/man8/cfexecd.8 658301854 -r--r--r--1 root wheel 505 May 6 07:25 usr/local/man/man8/cfkey.8 658301864 -r--r--r--1 root wheel1730 May 6 07:25 usr/local/man/man8/cfrun.8 658301874 -r--r--r--1 root wheel 863 May 6 07:25 usr/local/man/man8/cfservd.8 658301884 -r--r--r--1 root wheel1632 May 6 07:25 usr/local/man/man8/cfshow.8 65830189 24 -r--r--r--1 root wheel 10391 May 6 07:25 usr/local/man/man8/ cfetoolcheck.8 65830190 16 -r--r--r--1 root wheel7293 May 6 07:25 usr/local/man/man8/ cfetooldump.8 65830191 16 -r--r--r--1 root wheel6390 May 6 07:25 usr/local/man/man8/ cfetoolimport.8 65830192 24 -r--r--r--1 root wheel 10258 May 6 07:25 usr/local/man/man8/ cfetoolupdate.8 65830193 16 -r--r--r--1 root wheel7535 May 6 07:25 usr/local/man/man8/ cfetoolcreate.8 65830194 16 -r--r--r--1 root wheel7039 May 6 07:25 usr/local/man/man8/ cfetoolgraph.8 65830195 16 -r--r--r--1 root wheel6269 May 6 07:25 usr/local/man/man8/ cfetoolinfo.8 658515964 drwxr-xr-x4 root wheel 512 May 6 07:25 usr/local/share/cfengine 658515974 drwxr-xr-x2 root wheel 512 May 6 07:25 usr/local/share/cfengine/doc 658515984 drwxr-xr-x2 root wheel 512 May 6 07:25 usr/local/share/cfengine/html Deleting db46-4.6.21.1 - -- WBR, bsam -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
