RE: Fixing malloc.h related warning

2003-09-15 Thread Boehne, Robert
Bob, I agree, and would approve such a patch if one were posted. Robert -Original Message- From: Bob Friesenhahn [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 1:38 PM To: Boehne, Robert Cc: Dalibor Topic; [EMAIL PROTECTED] Subject: RE: Fixing malloc.h related warning On Mo

RE: Fixing malloc.h related warning

2003-09-15 Thread Bob Friesenhahn
On Mon, 15 Sep 2003, Boehne, Robert wrote: > Dalibor, > > Ok, I checked that both headers are checked for, and they are, so > the only unresolved issue would be if some platform needed both > headers. Does anyone out there know one way or the other? I suggest implementing this change, and we wil

RE: Fixing malloc.h related warning

2003-09-15 Thread Bob Friesenhahn
On Mon, 15 Sep 2003, Boehne, Robert wrote: > Dalibor, > > This would require a patch that looks for whatever malloc.h is #included for > in stdlib.h and prefers it in stdlib.h. So it isn't as simple as s/malloc/stdlib/. The question is how necessary is it to support non-ANSI C. Stdlib.h is ANSI

RE: Fixing malloc.h related warning

2003-09-15 Thread Boehne, Robert
Dalibor, Ok, I checked that both headers are checked for, and they are, so the only unresolved issue would be if some platform needed both headers. Does anyone out there know one way or the other? Robert -Original Message- From: Dalibor Topic [mailto:[EMAIL PROTECTED] Sent: Monday, Sept

Re: Fixing malloc.h related warning

2003-09-15 Thread Dalibor Topic
Hi Robert, what about /* * Include the header defining malloc. * * On K&R C compilers, that's , * on ANSI C and ISO C compilers, that's * . * */ #if HAVE_STDLIB_H # include #else # if HAVE_MALLOC_H #include # endif #endif cheers, dalibor topic Boehne, Robert wrote: Dalibor, This

RE: Fixing malloc.h related warning

2003-09-15 Thread Boehne, Robert
Dalibor, This would require a patch that looks for whatever malloc.h is #included for in stdlib.h and prefers it in stdlib.h. So it isn't as simple as s/malloc/stdlib/. Robert -Original Message- From: Dalibor Topic [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 11:36 AM To:

RE: Compiling 32-bit code on 64-bit HP-UX

2003-09-15 Thread Boehne, Robert
Martin, Ok, it sounds like the problem is that Libtool/config.guess/? is using a C compiler to test certain things. Because that is the case, you may also need to set CC, CFLAGS & CPPFLAGS as appropriate. The reason I suggest setting +DA in CXXCPPFLAGS is that "+DA2.0w" will cause __LP64__ to be

Fixing malloc.h related warning

2003-09-15 Thread Dalibor Topic
Hi, bulding code that uses libtool 1.5 on i386-FreeBSD 4.8, I noticed a compiler warning: gcc -DHAVE_CONFIG_H -I. -I../../kaffe-1.1.1/libltdl -I. -g -O2 -c ../../kaffe-1.1.1/libltdl/ltdl.c -fPIC -DPIC -o .libs/ltdl.o In file included from ../../kaffe-1.1.1/libltdl/ltdl.c:57: /usr/include/mall

Re: Compiling 32-bit code on 64-bit HP-UX

2003-09-15 Thread Martin Frydl
Boehne, Robert wrote: Martin, Even on a 64-bit capable machine, aCC defaults to 32-bit libraries. Having config.guess return hppa2.0w does not change the output that is produced, aCC will produce whatever you tell it to (32-bit by default). When you're running a configure script you want to set bo

hey.. my name is jenny <333

2003-09-15 Thread optin
45h3arf6v10819k1 r6i405186ong103p023g9q57841376yi 66955es4507043mwThe ip of the person who subscribed to receive this email is: 12.222.57.3 ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool