Re: compilation difficulties on BeOS

2000-12-02 Thread rbb
> Yep... this bug crept in last night; it showed up in a gcc warning on > FreeBSD in the wee hours... sizeof(* void *) is undefined. > > You can't do > > void *x; > sizeof(*x) ARGH! This is my fault. It compiled cleanly on my Linux box. I'll try to get to it today unless somebody beats

Re: compilation difficulties on BeOS

2000-12-02 Thread Jeff Trawick
Sam TH <[EMAIL PROTECTED]> writes: > Then I encounter this error: > > cc -DBEOS -DBEOS -c -I../../include -Imm shmem.c > ### mwcc Compiler Error: > # MM *newmm = mm_create(reqsize + sizeof(*newmm), file, > MM_ALLOCATE_ENOUGH); > # ^ > # il

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Sat, Dec 02, 2000 at 07:07:59PM -, David Reid wrote: > Sam, > > Now I'm really confused. You shouldn't be getting these errors if there > isn't a networkio.h file in your beos directories. Can you make sure that > you don't have a networkio.h in ANY beos directory that's referenced, i.e.

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Sat, Dec 02, 2000 at 09:04:27AM -0800, [EMAIL PROTECTED] wrote: > > > On Sat, Dec 02, 2000 at 12:57:01AM -0800, Greg Stein wrote: > > > That is generated by ./buildconf in the APR directory. It is created by > > > autoconf or autoheader (I forget which). Something must have happened to > > > i

Re: compilation difficulties on BeOS

2000-12-02 Thread rbb
> On Sat, Dec 02, 2000 at 12:57:01AM -0800, Greg Stein wrote: > > That is generated by ./buildconf in the APR directory. It is created by > > autoconf or autoheader (I forget which). Something must have happened to it > > after you ran buildconf. > > Thanks. My problem was not running buildconf.

Re: compilation difficulties on BeOS

2000-12-02 Thread Greg Stein
On Sat, Dec 02, 2000 at 07:33:39AM -0600, Sam TH wrote: > On Sat, Dec 02, 2000 at 03:38:02AM -0800, Greg Stein wrote: > > users don't need the autoconf tool). IOW, the right answer is to expect the > > developers to know, or to have a README.dev or something. > > Attached is just such a README.dev

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Sat, Dec 02, 2000 at 03:38:02AM -0800, Greg Stein wrote: > users don't need the autoconf tool). IOW, the right answer is to expect the > developers to know, or to have a README.dev or something. Attached is just such a README.dev file. sam th [EMAIL

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Sat, Dec 02, 2000 at 03:38:02AM -0800, Greg Stein wrote: > I would think that configure would barf when it tries to use > apr_private.h.in, but I could easily imagine that it got buried in some > output and just wasn't easily seen. It wouldn't be hard to add a test, but > it is important to rec

Re: compilation difficulties on BeOS

2000-12-02 Thread Greg Stein
On Sat, Dec 02, 2000 at 04:51:46AM -0600, Sam TH wrote: > On Sat, Dec 02, 2000 at 12:57:01AM -0800, Greg Stein wrote: > > That is generated by ./buildconf in the APR directory. It is created by > > autoconf or autoheader (I forget which). Something must have happened to it > > after you ran buildco

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Sat, Dec 02, 2000 at 12:57:01AM -0800, Greg Stein wrote: > That is generated by ./buildconf in the APR directory. It is created by > autoconf or autoheader (I forget which). Something must have happened to it > after you ran buildconf. Thanks. My problem was not running buildconf. Too bad thi

Re: compilation difficulties on BeOS

2000-12-02 Thread Greg Stein
On Sat, Dec 02, 2000 at 01:28:36AM -0600, Sam TH wrote: > On Fri, Dec 01, 2000 at 08:13:30PM -0800, [EMAIL PROTECTED] wrote: > > > > I looks like stdlib isn't being included, so the compiler is assuming that > > malloc is defined as "int malloc(int)", but it has to return a void *, so > > it is co

Re: compilation difficulties on BeOS

2000-12-02 Thread Sam TH
On Fri, Dec 01, 2000 at 08:13:30PM -0800, [EMAIL PROTECTED] wrote: > > I looks like stdlib isn't being included, so the compiler is assuming that > malloc is defined as "int malloc(int)", but it has to return a void *, so > it is complaining. Could you look in apr_private.h, and ensure that > HAV

Re: compilation difficulties on BeOS

2000-12-02 Thread rbb
I looks like stdlib isn't being included, so the compiler is assuming that malloc is defined as "int malloc(int)", but it has to return a void *, so it is complaining. Could you look in apr_private.h, and ensure that HAVE_STDLIB_H is being defined to be 1. Thanks, Ryan On Fri, 1 Dec 2000, Sam

compilation difficulties on BeOS

2000-12-02 Thread Sam TH
I was trying to compile apr on a powerpc-apple-beos machine, and ran into the following quite strange error: ake[1]: Entering directory `/boot/home/apr/lib' cc -DBEOS -DBEOS -c -I../include -I../include/arch/beos apr_pools.c ### mwcc Compiler Error: # return malloc(reqsize); #