problimata me compile kai pico

[petros ppap]

Geia sas
Erotisi 1)
pedeuome edo kai kairo me to na kano compile to GTK+-2.3.2
dokimasa to gtk+-2.4.2 alla eixe problimata kai den ginotan compile
meta eipa na dokimaso to gtk+-2.3.2 loipon auto pou den katalabeno einai pos
8a sundeso ti glib-2.3.2 mazi me to gtk xreiazete to pkg-config
+ allon ta opoia ta egkatestisa,
to pkg-config briski apo oti katalaba kati arxeia .pc
opou lene pou einai egkatestimena ta lib (dior8osteme an kano la8os)
auta briskonte sto /usr/lib/pkgconfig, ta atk, pango, kai kapoia alla pou 
xreiazontan to gtk ta ebala dinontas --prefix=/usr kai automatos ta ebrikse 
to
pkg-config tora omos auto den ginete me ti glib
mipos mporei kapoios na me boi8isi kai na mou eksigisi an ginete,
oste na katalabo pos leitourgei h oli upo8esi?
dhl pou prepei na balo ti glib kai pos oste na tin brei to pkg-config?

Erotisi 2)
to mandrake9.2 den exei pine/pico
prospa8isa na to egkatastiso to pine4.58 alla diabasa to parakato kai eipa 
na rotiso prin sunexiso

-----------------------------------------------------------------------
BUILD SYNTAX
-----------------------------------------------------------------------

A shell interpreter script called "build" is used to compile Pine and the
other programs in the distribution. The build script is also responsible
for building operating system specific symbolic links into the
imap/c-client source tree.

Usage: build <make-options> <target-platform>

<target-platform> may be one of the ports listed in doc/pine-ports or
  clean   Clean up object files and such.
          Also, a good way to rebuild Pine/Pico from scratch.

"Build" by itself with no arguments is the same as typing in the previous
build command with the arguments used then.

To build Pine and Pico the command "build xxx" should work where xxx
is one of the targets. For example "build gul" to build Pine for Ultrix.

There are three pieces of Pine which are optionally included. When
you build Pine, the three lines

       Including SSL functionality
       Including LDAP functionality
       Including Kerberos5 functionality

should be printed early in the build process if the corresponding
piece is being included.  (See below for more about these options.)
-------------------------------------------------------------------


tora sto  doc/pine-ports  exei + allon auta gia to linux
(ta alla pou exei einai gia alla sustimata)

Linux
	lnx	Linux using crypt from the C library
	lnp	Linux using Pluggable Authentication Modules (PAM)
	slx	Linux using -lcrypt to get the crypt function
	sl4	Linux using -lshadow to get the crypt() function
	sl5	Linux using shadow passwords, no extra libraries
	lrh	RedHat 7.2 or later. Same as lnp but with SSLDIR=/usr/share/ssl,
		  SSLINCLUDE=/usr/include/openssl, SSLLIB=/usr/lib, GSSDIR=/usr/kerberos
	lsu     SuSE Linux.  Same as lnp but with SSLDIR=/usr/ssl,
		  SSLINCLUDE=/usr/include/openssl, SSLLIB=/usr/lib

tora ego ti bazo gia to <target-platform>?
kai fusika ti bazo gia to <make-options> pou den anaferei tipota

kai den anafero sxetika gia to  SSL  LDAP  Kerberos5  :>

tora to pine to 8elo gia to pico
mi me baresete omos an sas po giati to 8elo,
to 8elo giati den ksero kanenan allo editor gia tin consola.
Euxaristo.
(kai mi barate akoma ma8enoume)

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail