Subject: RE: guru needed -- diagnosing configure problems on Win32
From: Alexey Sinutin (megabyte@salesexplosion.com)
Date: Mon Jan 31 2000 - 03:08:18 CST
Hello guys!
The problem is not in ABI_XX_ROOT, the problem is in extra 0x0d character at
the end of the following line
INCLUDES= -I$(ABI_XX_ROOT)/../libiconv/include
delete the character from the line and from the next empty line and
everything will be fine.
>
> At 12:05 PM 1/29/00 +0100, Henrik Berg wrote:
> >I looked in ..../ev/win/Makefile and there is a:
> >
> >INCLUDES= -I$(ABI_XX_ROOT)/../libiconv/include
> >
> >in it. It's in my cleen copy of the CVS too so it shouldn't be any
> >problem. I was planing to make a UT_* function, so not every
> file needs to
> >include 'iconv.h', but thats irrelevant, it should work.
> >
> >Tom, can you please have a look in your
> abi/src/af/ev/win/Makefile to see
> >if it has the above INCLUDES line. If it has, can you fiddle
> with it to
> >make it work for you. Possible changing the ABI_XX_ROOT to
> ABI_ROOT. The
> >ABI_XX_ROOT is without driveletter isn't it? Paul?
> That didn't work for me, so I took the road of least
> resistance
> and simply copied the libiconv headers into the win directory...
>
>
> LDR
>
>
This archive was generated by hypermail 2b25 : Mon Jan 31 2000 - 03:08:52 CST