Hi every one,
I'm having a weird time compiling postgresql 7.3.x on uw 713.
No matter what I put after .configure, it's not taken into account :?
Works fine on uw 711
the neat exemple is that it can't find readline even with
--with-includes=/usr/local/include
--with-java doesn't event check fo
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> Depending on the version of Solaris and the compiler flags the third
>> argument can be a pointer to socklen_t, void, size_t or int.
> I think what I'm going to do is this: The argument is question cannot
> possibly be o
Peter Eisentraut writes:
> [EMAIL PROTECTED] writes:
>
> > Depending on the version of Solaris and the compiler flags the
> > third argument can be a pointer to socklen_t, void, size_t or
> > int.
>
> The argument is question cannot possibly be of a different width
> than int, unless som
[EMAIL PROTECTED] writes:
> Depending on the version of Solaris and the compiler flags the third
> argument can be a pointer to socklen_t, void, size_t or int.
I think what I'm going to do is this: The argument is question cannot
possibly be of a different width than int, unless someone is *rea
Tom Lane writes:
> If socklen_t exists, it's presumably the right thing to use, so if
> we just hardwire "void -> socklen_t", I think it'd be OK. If we're
> wrong, we'll hear about it...
Ah, if only life were that simple ;-/
Depending on the version of Solaris and the compiler flags the thir
On Mié 08 Nov 2000 19:34, Tom Lane wrote:
>
> Well, maybe. But is it worth the trouble? Hard to believe anyone else
> did the same thing.
>
> If socklen_t exists, it's presumably the right thing to use, so if we
> just hardwire "void -> socklen_t", I think it'd be OK. If we're wrong,
> we'll he
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Not sure what to do about this. It will clearly not do to define
>> ACCEPT_TYPE_ARG3 as void. Perhaps we need a special case for
>> Solaris 7: if we detect that accept() is declared with "void *",
>> assume that socklen_t is the thing to use. Pete
On Mié 08 Nov 2000 18:17, Tom Lane wrote:
>
> I guess we not only need a hack, but a nastygram or three sent off to
> the Solaris people. void *? What in heavens name were they thinking?
> That essentially means you've got no parameter type checking at all
> on calls to accept() --- or any other
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> No. Forgot to tell my latest experience.
> 1) postgres 7.0.2 compiles great on Solaris 7 and Solaris 8.
> 2) postgres cvs (latest download) doesn't compile (same error on both) on
> Solaris 7 nor Solaris 8.
Ah so. 7.0.*'s configure didn't try t
On Mié 08 Nov 2000 18:01, Tom Lane wrote:
>
> Well, that tells the tale all right: the critical lines are
>
> typedef uint32_tsocklen_t;
>
> typedef void*Psocklen_t;
>
> extern int accept(int, struct sockaddr *, Psocklen_t);
>
> What brainless idiot decided it
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
Is there any kind of info you would need that I could provide?
>>
>> If you could put
>> #include
>> #include
>> into a file temp.c, and then send the output of "gcc -E temp.c",
>> it might shed some light.
> There it goes!!
Well, that tell
On Lun 06 Nov 2000 18:25, Peter Eisentraut wrote:
> > Martin A. Marques writes:
> > Is there any kind of info you would need that I could provide? If you
> > want I can send the config.log, output of the configure execution, etc.
> > Even the socket.h and the types.h.
> > BTW, I didn't find diffs
On Lun 06 Nov 2000 13:28, Tom Lane wrote:
> "Martin A. Marques" <[EMAIL PROTECTED]> writes:
> >> Hmm ... is it possible that his compiler distinguishes between
> >> "extern int foo(...)" and "extern foo(...)" ? Why don't we
> >> have the return type there, anyway?
> >
> > If it's of any help, I'm
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
>> Hmm ... is it possible that his compiler distinguishes between
>> "extern int foo(...)" and "extern foo(...)" ? Why don't we
>> have the return type there, anyway?
> If it's of any help, I'm on Solaris 7, SPARC, gcc-2.95.2, latest
> Postgres CVS
On Lun 06 Nov 2000 12:06, Tom Lane wrote:
> "Martin A. Marques" <[EMAIL PROTECTED]> writes:
> > Well, mine looks like:
> > extern int accept(int, struct sockaddr *, Psocklen_t);
> >
> > This is what I have in the configure:
> > extern accept ($ac_cv_func_accept_arg1, $ac_cv_func_accept_arg2,
> > $
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> Well, mine looks like:
> extern int accept(int, struct sockaddr *, Psocklen_t);
> This is what I have in the configure:
> extern accept ($ac_cv_func_accept_arg1, $ac_cv_func_accept_arg2,
> $ac_cv_func_accept_arg3 *);
Hmm ... is it possible that
On Vie 03 Nov 2000 20:37, Peter Eisentraut wrote:
> Martin A. Marques writes:
> > checking types of arguments for accept()... configure: error: could not
> > determine argument types
>
> According to the documentation for Solaris 7 it should be 'accept(int,
> struct sockaddr *, socklen_t *)', whic
On Sáb 04 Nov 2000 18:54, Tom Lane wrote:
> "Martin A. Marques" <[EMAIL PROTECTED]> writes:
> > On Vie 03 Nov 2000 22:16, Tom Lane wrote:
> >> Hm, how do your system's include files declare accept()?
> >
> > The config.log file starts given fails at this point:
> > configure:5475: conflicting type
Martin A. Marques writes:
> checking types of arguments for accept()... configure: error: could not determine
>argument types
According to the documentation for Solaris 7 it should be 'accept(int,
struct sockaddr *, socklen_t *)', which is the same on my system, so the
problem is elsewhere. On
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> On Vie 03 Nov 2000 22:16, Tom Lane wrote:
>> Hm, how do your system's include files declare accept()?
> The config.log file starts given fails at this point:
> configure:5475: conflicting types for `accept'
> /usr/include/sys/socket.h:384: previou
On Vie 03 Nov 2000 22:16, Tom Lane wrote:
>
> Hm, how do your system's include files declare accept()?
>
> It would help to see the part of the config.log file that shows the
> errors configure gets while trying to find workable input types for
> accept().
The config.log file starts given fails a
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> I'm trying to compile the CVS (fresh download) of postgres and I get this
> running the configure script:
> checking types of arguments for accept()... configure: error: could not
> determine argument types
Hm, how do your system's include fil
I'm trying to compile the CVS (fresh download) of postgres and I get this
running the configure script:
checking for tzname... yes
checking for union semun... no
checking for struct sockaddr_un... yes
checking for int timezone... yes
checking types of arguments for accept()... configure: error:
23 matches
Mail list logo
