|
osdir.com mailing list archive |
|
Subject: problems building gnome_print - msg#00447List: os.netbsd.helpgnome_core lately. Eventualy it arived at /usr/pkgsrc/print/gnome_print en it stopped with: cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl -I../intl -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/usr/pkgsrc/print/gnome-print/work/.buildlink/lib/gnome-libs/include -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/gtk-1.2 -I/usr/p kgsrc/print/gnome-print/work/.buildlink/include/glib/glib-1.2 -I/usr/pkgsrc/print/gnome-print/work/.buildlink/lib/glib/include -I/usr/pkg/share/ x11-links/include -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/gdk-pixbuf-1.0 -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include / -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/gnome-xml -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include -DPROFILEDIR=\"/usr/ pkg/share/gnome-print/profiles/\" -DGNOMEPRINT_LIBDIR=\"/usr/pkg/lib\" -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include -I/usr/pkg/share/ x11-links/include -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/gtk-1.2 -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include/glib/g lib-1.2 -I/usr/pkgsrc/print/gnome-print/work/.buildlink/lib/glib/include -I/usr/pkg/share/x11-links/include -DGNOMELOCALEDIR=\"/usr/pkg/share/lo cale\" -DBINDIR=\"/usr/pkg/bin\" -DDATADIR=\"/usr/pkg/share\" -DFONTMAPDIR_STATIC=\"/usr/pkg/share/gnome/fonts\" -DFONTMAPDIR_DYNAMIC=\"/usr/pkg /etc/gnome/fonts\" -I/usr/pkgsrc/print/gnome-print/work/.buildlink/include -O2 -I/usr/pkg/share/x11-links/include -Wall -Wunused -c gnome-print- ps2.c -fPIC -DPIC -o .libs/gnome-print-ps2.o In file included from gnome-print-ps2.c:51: ../libgnomeprint/gnome-font-private.h:25: freetype/freetype.h: No such file or directory *** Error code 1 Stop. make: stopped in /usr/pkgsrc/print/gnome-print/work/gnome-print-0.35/libgnomeprint Now I've cheked if freetype2 is there and it is (installed with xfree86) also when I check the work dir it has root@gonzo /usr/pkgsrc/print/gnome-print/work/.buildlink/include/freetype2/freetype> lrwxr-xr-x 1 root wheel 48 Sep 23 20:37 freetype.h -> /usr/X11R6/include/freetype2/freetype/freetype.h And I also checked that root@gonzo /usr/X11R6/include/freetype2/freetype> -r--r--r-- 1 root 35 162017 Mar 1 2002 freetype.h is there (and as you see it is). Now I've tried everything I could think of (make clean from /usr/pkgsrc) pkg_delete's and I also updated to 1.6 with a brandnew /usr/pkgsrc but everytime it comes back with the same error. So it looks like I have to look somewhere else :) But I haven't got Aa clue where to look. Also. this is not the only pakages wich I encounterd problems with. There these days (on my system) many packages which stop make 'cause of some link says it looks like to be moved durin the build. ala: libtool: link: warning: `/usr/pkgsrc/devel/pango/work/.buildlink/lib/libgobject-2.0.la' seems to be moved libtool: link: warning: `/usr/pkgsrc/devel/pango/work/.buildlink/lib/libgmodule-2.0.la' seems to be moved libtool: link: warning: `/usr/pkgsrc/devel/pango/work/.buildlink/lib/libglib-2.0.la' seems to be moved libtool: link: warning: `/usr/pkgsrc/devel/pango/work/.buildlink/lib/libiconv.la' seems to be moved libtool: link: warning: `/usr/pkgsrc/devel/pango/work/.buildlink/lib/libintl.la' seems to be moved But On the other hand I also experienced the perfect building of mozilla (I know. Not wise) which also depends on freetype2. Can anyone give me a clue of where to look, what to check or anything? Bjorn Schothuis Thread at a glance:
Previous Message by Date: click to view message previewRe: now using rsa key, so zapped password; is that okay?On Wed, 25 Sep 2002, henry nelson wrote: > Question2: > is there a "better" or more "standard" way of blocking logins with a plain > password? TIA look in sshd.conf: DenyUsers DenyGroups If you are using SSH in a private subnet (or with hosts with statical IPs) you can even filter access to ssh port with ipf by IP-Addresses. -- Ein Mann, der von pltzlichem Regen berrascht wird, rennt die Strae hinunter um nicht na und durchtrnkt zu werden. Wenn man es aber einmal als natrlich hinnimmt im Regen na zu werden, kann man mit unbewegtem Geist bis auf die Haut durchnt werden. -- Yamamoto Tsunetomo [http://www.net-tex.de] Next Message by Date: click to view message previewRe: where does time come from?On 25 Sep 2002 01:58:57 -0400, "Perry E. Metzger" <perry@xxxxxxxxxxxx> wrote: > > "James K. Lowden" <jklowden@xxxxxxxxxxxxxxx> writes: > > AFAICT, my ancient 1.4.2 i386 firewall-cum-mailhub went south at 6:04 > > AM > [...] > > I didn't realize anything was wrong until 13 hours later, at ~19:00. > > I'd strongly suggest upgrading to 1.6 by the way. 1.4.2 has more > security holes than I can name. You're inviting horror. Acknowledged, thanks. It's on the todo list, higher now. > > Is the TOD clock initialized from time information on the root > > filesystem, or is it possible my system was compromised and tampered > > with? > > See sys/arch/i386/isa/clock.c::inittodr() > > Did you ignore the following boot message? > > printf("WARNING: clock time much less than file system > time\n"); printf("WARNING: using file system time\n"); Well, no, not as far as I can tell: # zcat /var/log/messages.* |grep WARN Sep 24 06:10:56 home root: WARNING: /etc/sendmail.cf not readable; sendmail not started. # cat /var/log/messages |grep WARN # The machine itself is quite new; I doubt the battery is shot. The paranoid part of me -- obviously not very big, or I would already have heeded your strong advice -- is disconcerted: it leads me to think the system clock had been reset, something I definitely didn't do. OTOH, it might be I wasn't paying close attention; there are no messages from ntpd in /var/log/message* going back to 15 September. Still, 12 hours of drift? That's a lot of drift and a lot not to notice. Thanks for the reply. --jkl Previous Message by Thread: click to view message previewnow using rsa key, so zapped password; is that okay?The more I use ssh, the more I like it, but the more I find I don't understand. So today I got rsa authorization to work, and realized I don't need a password anymore (this particular user never logs in via the console, only remotely via ssh). I did vipw as root and replaced the password string with '*' as it seemed like it would make things only that more secure for users like that. Question1: will that cause trouble in some unforeseen way? Question2: is there a "better" or more "standard" way of blocking logins with a plain password? TIA -- henry nelson Next Message by Thread: click to view message previewBridging firewall?I want to set up a bridging firewall, meaning a firewall that has no IP address and simply resides between the main default router (a combo DSL modem/router box) and the rest of the net. The IPF HowTo indicates this can be kind of done with OpenBSD. Can this be done with ipf under NetBSD? Or, is there some other firewall package under NetBSD that does this? I don't need much out of this box, just some simple host blocking and some NATP for some boxes. --Paul Hoffman Loading Comments...
|
|
