Thread: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Keith F Irwin
Date:
I just downloaded the src rpm for postgres 7.1.2

    postgresql-7.1.2-4PGDG.src.rpm

and tried to rebuild it:

    rpm --rebuild postgresql-7.1.2-4PGDG.src.rpm --target=i686

and got the following compile error!  (I'm compiling on RH7.1.)  Is
there anything I can do or can someone let the folks responsible for the
package know?

(Note: I was able to rebuild the 7.1.1 RPMS no prob.)

Keith

----
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
-march=i686 -Wno-error -I../../../src/include   -c -o gram.o gram.c
gram.y:968:52: warning: null character(s) ignored
gram.y: In function `yyparse':
gram.y:969: `l' undeclared (first use in this function)
gram.y:969: (Each undeclared identifier is reported only once
gram.y:969: for each function it appears in.)
gram.y:970: parse error before `:'
make[3]: *** [gram.o] Error 1
make[3]: Leaving directory
`/usr/src/redhat/BUILD/postgresql-7.1.2/src/backend/parser'
make[2]: *** [parser-recursive] Error 2
make[2]: Leaving directory
`/usr/src/redhat/BUILD/postgresql-7.1.2/src/backend'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/postgresql-7.1.2/src'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.61518 (%build)
----



Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Keith F Irwin
Date:
On a hunch, I tried the --rebuild command without the i686 target, and
got a lot farther: but still an error:

<quote>
make[3]: Leaving directory
`/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/libpgeasy'
make[3]: Entering directory
`/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/odbc'
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
-march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
-DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c

Cannot allocate 3473903228 bytes after allocating 1767100 bytes
</quote>

What does that allocate error mean?  I've got 1/2 gig of Ram.  Does it
take more than that to compile?

Keith

On 16 Jun 2001 09:57:20 -0700, Keith F Irwin wrote:
> I just downloaded the src rpm for postgres 7.1.2
>
>     postgresql-7.1.2-4PGDG.src.rpm
>
> and tried to rebuild it:
>
>     rpm --rebuild postgresql-7.1.2-4PGDG.src.rpm --target=i686
>
> and got the following compile error!  (I'm compiling on RH7.1.)  Is
> there anything I can do or can someone let the folks responsible for the
> package know?
>
> (Note: I was able to rebuild the 7.1.1 RPMS no prob.)
>
> Keith
>
> ----
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> -march=i686 -Wno-error -I../../../src/include   -c -o gram.o gram.c
> gram.y:968:52: warning: null character(s) ignored
> gram.y: In function `yyparse':
> gram.y:969: `l' undeclared (first use in this function)
> gram.y:969: (Each undeclared identifier is reported only once
> gram.y:969: for each function it appears in.)
> gram.y:970: parse error before `:'
> make[3]: *** [gram.o] Error 1
> make[3]: Leaving directory
> `/usr/src/redhat/BUILD/postgresql-7.1.2/src/backend/parser'
> make[2]: *** [parser-recursive] Error 2
> make[2]: Leaving directory
> `/usr/src/redhat/BUILD/postgresql-7.1.2/src/backend'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/usr/src/redhat/BUILD/postgresql-7.1.2/src'
> make: *** [all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.61518 (%build)
> ----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org



Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
teg@redhat.com (Trond Eivind Glomsrød)
Date:
Keith F Irwin <kirwin14@home.com> writes:

> make[3]: Leaving directory
> `/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/libpgeasy'
> make[3]: Entering directory
> `/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/odbc'
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c
>
> Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> </quote>
>
> What does that allocate error mean?

That somethings weird...

> I've got 1/2 gig of Ram.  Does it take more than that to compile?

Take a look at what it's trying to allocate. I'm not sure what's
happening, but something seems bad... have you installed another
compiler, glibc, kernel or something similar? Or overclocked?
It's known to be compiling, so I'm not sure why you're seeing thing problem.

That said, you can download postgresql rpms for Red Hat Linux 7.1 from
http://people.redhat.com/teg/pg/

This is the above RPMs, with some more fixes Lamar and I haven't
merged yet.

--
Trond Eivind Glomsrød
Red Hat, Inc.

Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Tom Lane
Date:
Keith F Irwin <kirwin14@home.com> writes:
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c

> Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> </quote>

> What does that allocate error mean?  I've got 1/2 gig of Ram.  Does it
> take more than that to compile?

No.  I'm thinking something's awfully broken about your machine...
have you had trouble compiling things in the past?

            regards, tom lane

Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Keith F Irwin
Date:
On 16 Jun 2001 13:54:06 -0400, Tom Lane wrote:
> Keith F Irwin <kirwin14@home.com> writes:
> > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> > -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> > -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c
>
> > Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> > </quote>
>
> > What does that allocate error mean?  I've got 1/2 gig of Ram.  Does it
> > take more than that to compile?

> No.  I'm thinking something's awfully broken about your machine...
> have you had trouble compiling things in the past?

I've not had trouble compiling anything (including the mozilla source
rpm).  About the only thing different about my machine is that I used
the XFS installer from SGI.  Perhaps there's something odd there.

Incidentally, I tried rerunning the rpm --rebuild command, and this time
it worked.  Got a complete set of RPMS, which I then installed.

Then I tried it again with the --target=i686, and it ALSO worked this
time. Very odd.  Compilation was VERY clean, no warnings, etc.

Alas, I think I've wasted bandwidth posting my comment!

Keith


Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Keith F Irwin
Date:
Trond--

Thanks for the advice.  I simple reran the rpm --rebuild command and,
for, some reason, it now works just fine.  Very clean compiles for both
normal and --target=i686.

About the only thing different about my system from a purely stock
install of RH7.1 is that I used SGIs XFS installer.  Perhaps there was
some lag on a buffere somewhere?  My understanding of how XFS interacts
with other systems is dim at best.

Keith

On 16 Jun 2001 13:51:44 -0400, Trond Eivind Glomsrød wrote:
> Keith F Irwin <kirwin14@home.com> writes:
>
> > make[3]: Leaving directory
> > `/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/libpgeasy'
> > make[3]: Entering directory
> > `/usr/src/redhat/BUILD/postgresql-7.1.2/src/interfaces/odbc'
> > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> > -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> > -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c
> >
> > Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> > </quote>
> >
> > What does that allocate error mean?
>
> That somethings weird...
>
> > I've got 1/2 gig of Ram.  Does it take more than that to compile?
>
> Take a look at what it's trying to allocate. I'm not sure what's
> happening, but something seems bad... have you installed another
> compiler, glibc, kernel or something similar? Or overclocked?
> It's known to be compiling, so I'm not sure why you're seeing thing problem.
>
> That said, you can download postgresql rpms for Red Hat Linux 7.1 from
> http://people.redhat.com/teg/pg/
>
> This is the above RPMs, with some more fixes Lamar and I haven't
> merged yet.
>
> --
> Trond Eivind Glomsrød
> Red Hat, Inc.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly



Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
teg@redhat.com (Trond Eivind Glomsrød)
Date:
Keith F Irwin <kirwin14@home.com> writes:

> On 16 Jun 2001 13:54:06 -0400, Tom Lane wrote:
> > Keith F Irwin <kirwin14@home.com> writes:
> > > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> > > -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> > > -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c
> >
> > > Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> > > </quote>
> >
> > > What does that allocate error mean?  I've got 1/2 gig of Ram.  Does it
> > > take more than that to compile?
>
> > No.  I'm thinking something's awfully broken about your machine...
> > have you had trouble compiling things in the past?
>
> I've not had trouble compiling anything (including the mozilla source
> rpm).  About the only thing different about my machine is that I used
> the XFS installer from SGI.  Perhaps there's something odd there.

I've used that (Red Hat Linux 7.1 w/SGI XFS)  for a long time, and
have compiled lots of packages with it - no problems.

> Incidentally, I tried rerunning the rpm --rebuild command, and this time
> it worked.

I would be very suspicious of your hardware after that. Very
suspicious. If you're overclocking, turn it down - otherwise, check
your memory.

http://reality.sgi.com/cbrady/nmemtest86/


--
Trond Eivind Glomsrød
Red Hat, Inc.

Re: Unable to --rebuild postgresql-7.1.2-4PGDG.src.rpm

From
Keith F Irwin
Date:
As it turns out, you were right about the memory.  I used the memchecker
you referenced and indeed, it seems that one of my 128mg simms had some
bad spots in it.  I had it placed above the 256meg simm, so I imagine it
would be rare if things went wrong.  I've got a Duron 900, but I don't
over clock it, so of course that isn't it.

If I recall correctly, that simm had a life time warranty.  Now to see
if I can figure out how to make good on that...

Thanks!

Keith

On 16 Jun 2001 14:49:27 -0400, Trond Eivind Glomsrød wrote:
> Keith F Irwin <kirwin14@home.com> writes:
>
> > On 16 Jun 2001 13:54:06 -0400, Tom Lane wrote:
> > > Keith F Irwin <kirwin14@home.com> writes:
> > > > gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -O2
> > > > -march=i386 -mcpu=i686 -fpic -I. -I../../../src/include  -DHAVE_CONFIG_H
> > > > -DODBCINSTDIR='"/etc/pgsql"'  -c -o info.o info.c
> > >
> > > > Cannot allocate 3473903228 bytes after allocating 1767100 bytes
> > > > </quote>
> > >
> > > > What does that allocate error mean?  I've got 1/2 gig of Ram.  Does it
> > > > take more than that to compile?
> >
> > > No.  I'm thinking something's awfully broken about your machine...
> > > have you had trouble compiling things in the past?
> >
> > I've not had trouble compiling anything (including the mozilla source
> > rpm).  About the only thing different about my machine is that I used
> > the XFS installer from SGI.  Perhaps there's something odd there.
>
> I've used that (Red Hat Linux 7.1 w/SGI XFS)  for a long time, and
> have compiled lots of packages with it - no problems.
>
> > Incidentally, I tried rerunning the rpm --rebuild command, and this time
> > it worked.
>
> I would be very suspicious of your hardware after that. Very
> suspicious. If you're overclocking, turn it down - otherwise, check
> your memory.
>
> http://reality.sgi.com/cbrady/nmemtest86/
>
>
> --
> Trond Eivind Glomsrød
> Red Hat, Inc.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html