"Paul Swartz" <[EMAIL PROTECTED]> writes:

> On 3 Jan 2003 at 21:40, Niels M�ller wrote:
> 
> > Do you have <stdint.h> instead? I would expect both files to be
> > included with cygwin's gcc package, but I don't know.
> 
> I don't have either.  I hacked one together that's based off <sys/types.h> 
> however, and it seems to work pretty well, except...

Odd. stdint.h is required by C99, but I'm not sure if it's gcc or some
other package that is responsible for it. Which version of gcc are you
using? 

> Trying with a CVS checkout version of nettle, the linking fails on aes-
> text.exe, with _aes_encrypt_ and _aes_decrypt undefined.

Try disabling the assembler files (./configure --disable-assembler).
To use the assembler files, it seems we need a configure test to try
if there should be a leading underscore on external symbols. The
current assembler build system assumes there are no leading
underscores, like on ELF systems.

> Another bug is that nettle/desdata.c compiled twice, first without the -D 
> flags, the second time with them.  I worked around this by removing the #if 
> HAVE_CONFIG_H around the #include.

I don't understand this. Can you quote the commands executed by make,
any errors, and tell me in exactly which file you removed #if
HAVE_CONFIG_H?

My best guess is that it's the name "desdata.exe" (instead of
"desdata", on unix systems) that confuses the makefile. You could try
the following patch.

*** Makefile.am.~1.54.~ Thu Nov 21 21:38:54 2002
--- Makefile.am Sat Jan  4 13:32:50 2003
***************
*** 135,142 ****

  # Generate DES headers.
  $(des_headers): desdata.c
!       $(MAKE) desdata
!       ./desdata $(@F) > $@T
        test -s $@T && mv -f $@T $@

  des.o: des.c des.h $(des_headers)
--- 135,142 ----

  # Generate DES headers.
  $(des_headers): desdata.c
!       $(MAKE) desdata$(EXEEXT)
!       ./desdata$(EXEEXT) $(@F) > $@T
        test -s $@T && mv -f $@T $@

  des.o: des.c des.h $(des_headers)

Also, in general, it is helpful if you include full error messages,
versions of related tools (in particular gcc), and configure output.

Regards,
/Niels
_______________________________________________
lsh-bugs mailing list
[EMAIL PROTECTED]
http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs

Reply via email to