devil-linux-develop

[Devil-linux-develop] ddt didnt compile

[Oliver J. <oli...@mo...>]

looks like a problem between libgcrypt and ddt... 


Making all in packets
make[2]: Entering directory `/build/tmp/ddt-0.5.9/framework/packets'
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"ddt\"
-DVERSION=\"0.5.9\" -DDDT_CLIENT=1 -DCONF_DIR=\"/etc\"
-DPID_DIR=\"/var/run\" -DLOG_DIR=\"/dev/null\" -DVAR_DIR=\"/var/lib\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
-DHAVE_UNISTD_H=1 -DHAVE_DAEMON=1 -DHAVE_LIBDL=1  -I. -I. 
-I../include   -I/usr/include  -I/usr/include -I/usr/include   -g -O2 -c
DdtCipher.cc
In file included from DdtCipher.cc:12:
DdtCipher.h:61: warning: `GCRY_CIPHER_HD' is deprecated (declared at
   /usr/include/gcrypt.h:580)
DdtCipher.cc: In constructor
`DdtCipher::DdtCipher(DdtCipher::CipherAlgos,
   DdtCipher::CipherModes)':
DdtCipher.cc:27: error: cannot convert `gcry_cipher_algos' to `
   gcry_cipher_handle**' for argument `1' to `gcry_error_t
   gcry_cipher_open(gcry_cipher_handle**, int, int, unsigned int)'
make[2]: *** [DdtCipher.o] Error 1
make[2]: Leaving directory `/build/tmp/ddt-0.5.9/framework/packets'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/build/tmp/ddt-0.5.9/framework'
make: *** [all-recursive] Error 1

Re: [Devil-linux-develop] ddt didnt compile

[Heiko Z. <he...@zu...>]

Oliver Jehle wrote:
> looks like a problem between libgcrypt and ddt... 
> 

Yes, the bug is already reported on SF.

It looks to me, that ddt isn't maintained anymore. I wanted to wait 
until we get closer to the next major DL release and nuke it, in case 
there's no update available.

Heiko

Re: [Devil-linux-develop] ddt didnt compile

[Diego T. <dt...@co...>]

On Sat, Jan 31, 2004 at 10:20:57AM -0500, Heiko Zuerker wrote:
> 
> Yes, the bug is already reported on SF.
> 
> It looks to me, that ddt isn't maintained anymore. I wanted to wait 
> until we get closer to the next major DL release and nuke it, in case 
> there's no update available.

it's a pitty, but since ddt servers where hackedm nothing has been the same.

i vote for nuking it.

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España

Re: [Devil-linux-develop] ddt didnt compile

[Heiko Z. <he...@zu...>]

Diego Torres wrote:
> On Sat, Jan 31, 2004 at 10:20:57AM -0500, Heiko Zuerker wrote:
> 
>>Yes, the bug is already reported on SF.
>>
>>It looks to me, that ddt isn't maintained anymore. I wanted to wait 
>>until we get closer to the next major DL release and nuke it, in case 
>>there's no update available.
> 
> 
> it's a pitty, but since ddt servers where hackedm nothing has been the same.
> 
> i vote for nuking it.
> 

Wasn't it you who contributed that piece?

Heiko

[Devil-linux-develop] python compile

[Oliver J. <oli...@mo...>]

hi heiko..

ich habe ja nur 2.6 builds am laufen hier... und Python hat er gemacht
und installiert.. ich habs extra nochmals von hand mit 

configure ...
make
make install

durchprobiert... fehlerfrei... 





On Mon, 2004-02-02 at 00:33, Heiko Zuerker wrote:
> Diego Torres wrote:
> > On Sat, Jan 31, 2004 at 10:20:57AM -0500, Heiko Zuerker wrote:
> > 
> >>Yes, the bug is already reported on SF.
> >>
> >>It looks to me, that ddt isn't maintained anymore. I wanted to wait 
> >>until we get closer to the next major DL release and nuke it, in case 
> >>there's no update available.
> > 
> > 
> > it's a pitty, but since ddt servers where hackedm nothing has been the same.
> > 
> > i vote for nuking it.
> > 
> 
> Wasn't it you who contributed that piece?
> 
> Heiko
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Re: [Devil-linux-develop] ddt didnt compile

[Diego T. <dt...@co...>]

On Sun, Feb 01, 2004 at 06:33:28PM -0500, Heiko Zuerker wrote:
> >it's a pitty, but since ddt servers where hacked nothing has been the 
> >same.
> >
> >i vote for nuking it.
> 
> Wasn't it you who contributed that piece?

yes, thats why i say it should be nuked :) if now it doesn't compile and the
servers aren't working very well (and if no one uses this app), maybe it could
be nuked?

i'm using it on some 0.6 and 0.5 dl boxes that won't/can't be upgraded.
-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España

Re: [Devil-linux-develop] ddt didnt compile

[Oliver J. <oli...@mo...>]

debian use the 1.11 of libgcrypt for compiling it... fyi... 

but i think, if its not maintained, there must be another solution
around for the same functionality...


On Sun, 2004-02-01 at 23:56, Diego Torres wrote:
> On Sat, Jan 31, 2004 at 10:20:57AM -0500, Heiko Zuerker wrote:
> > 
> > Yes, the bug is already reported on SF.
> > 
> > It looks to me, that ddt isn't maintained anymore. I wanted to wait 
> > until we get closer to the next major DL release and nuke it, in case 
> > there's no update available.
> 
> it's a pitty, but since ddt servers where hackedm nothing has been the same.
> 
> i vote for nuking it.

Re: [Devil-linux-develop] ddt didnt compile

[Diego T. <dt...@co...>]

On Mon, Feb 02, 2004 at 09:06:16AM +0100, Oliver Jehle wrote:
> debian use the 1.11 of libgcrypt for compiling it... fyi... 
> 
> but i think, if its not maintained, there must be another solution
> around for the same functionality...

no, there isn't.

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España