pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
error on build from source
6+ messages / 3 participants
[nested] [flat]

* error on build from source
@ 2004-01-18 00:52  kdyke@keycomputerconsultants.com
  0 siblings, 1 reply; 6+ messages in thread

From: kdyke@keycomputerconsultants.com @ 2004-01-18 00:52 UTC (permalink / raw)
  To: pgsql-admin


Hi,

Postgres will not build on a Slackware-9.1 system.

make[3]: *** [utf8_and_gb18030.o] Error 1
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_gb18030'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/postgresql-7.4.1/src'
make: *** [all] Error 2

At this point I am looking suspiciously at gcc, which is...

gcc (GCC) 3.2.3

Have others run into this? Or do I need to look elsewhere to get it to 
build?
-- 
Ken Dyke,
406.581.0495



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: error on build from source
@ 2004-01-18 03:30  Tom Lane <tgl@sss.pgh.pa.us>
  parent: kdyke@keycomputerconsultants.com
  0 siblings, 1 reply; 6+ messages in thread

From: Tom Lane @ 2004-01-18 03:30 UTC (permalink / raw)
  To: kdyke@keycomputerconsultants.com; +Cc: pgsql-admin

kdyke@keycomputerconsultants.com writes:
> Postgres will not build on a Slackware-9.1 system.

> make[3]: *** [utf8_and_gb18030.o] Error 1
> make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_gb18030'

You have omitted all trace of what the actual problem is :-(

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: error on build from source
@ 2004-01-18 06:59  kdyke@keycomputerconsultants.com
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 6+ messages in thread

From: kdyke@keycomputerconsultants.com @ 2004-01-18 06:59 UTC (permalink / raw)
  To: pgsql-admin

On Sat, Jan 17, 2004 at 10:30:13PM -0500, Tom Lane (tgl@sss.pgh.pa.us) wrote:
> You have omitted all trace of what the actual problem is :-(

[snip many screenfuls of compiler output]
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_cyrillic'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_cyrillic.o utf8_and_cyrillic.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared -Wl,-soname,libutf8_and_cyrillic.so.0 utf8_and_cyrillic.o -L../../../../../../src/port   -o libutf8_and_cyrillic.so.0.0
rm -f libutf8_and_cyrillic.so.0
ln -s libutf8_and_cyrillic.so.0.0 libutf8_and_cyrillic.so.0
rm -f libutf8_and_cyrillic.so
ln -s libutf8_and_cyrillic.so.0.0 libutf8_and_cyrillic.so
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_cyrillic'
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_cn'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_euc_cn.o utf8_and_euc_cn.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared -Wl,-soname,libutf8_and_euc_cn.so.0 utf8_and_euc_cn.o -L../../../../../../src/port   -o libutf8_and_euc_cn.so.0.0
rm -f libutf8_and_euc_cn.so.0
ln -s libutf8_and_euc_cn.so.0.0 libutf8_and_euc_cn.so.0
rm -f libutf8_and_euc_cn.so
ln -s libutf8_and_euc_cn.so.0.0 libutf8_and_euc_cn.so
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_cn'
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_jp'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_euc_jp.o utf8_and_euc_jp.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared -Wl,-soname,libutf8_and_euc_jp.so.0 utf8_and_euc_jp.o -L../../../../../../src/port   -o libutf8_and_euc_jp.so.0.0
rm -f libutf8_and_euc_jp.so.0
ln -s libutf8_and_euc_jp.so.0.0 libutf8_and_euc_jp.so.0
rm -f libutf8_and_euc_jp.so
ln -s libutf8_and_euc_jp.so.0.0 libutf8_and_euc_jp.so
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_jp'
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_kr'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_euc_kr.o utf8_and_euc_kr.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared -Wl,-soname,libutf8_and_euc_kr.so.0 utf8_and_euc_kr.o -L../../../../../../src/port   -o libutf8_and_euc_kr.so.0.0
rm -f libutf8_and_euc_kr.so.0
ln -s libutf8_and_euc_kr.so.0.0 libutf8_and_euc_kr.so.0
rm -f libutf8_and_euc_kr.so
ln -s libutf8_and_euc_kr.so.0.0 libutf8_and_euc_kr.so
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_kr'
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_tw'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_euc_tw.o utf8_and_euc_tw.c
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared -Wl,-soname,libutf8_and_euc_tw.so.0 utf8_and_euc_tw.o -L../../../../../../src/port   -o libutf8_and_euc_tw.so.0.0
rm -f libutf8_and_euc_tw.so.0
ln -s libutf8_and_euc_tw.so.0.0 libutf8_and_euc_tw.so.0
rm -f libutf8_and_euc_tw.so
ln -s libutf8_and_euc_tw.so.0.0 libutf8_and_euc_tw.so
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_euc_tw'
make[3]: Entering directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_gb18030'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -I../../../../../../src/include -D_GNU_SOURCE   -c -o utf8_and_gb18030.o utf8_and_gb18030.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html; for instructions.
make[3]: *** [utf8_and_gb18030.o] Error 1
make[3]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs/utf8_and_gb18030'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/postgresql-7.4.1/src/backend/utils/mb/conversion_procs'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/postgresql-7.4.1/src'
make: *** [all] Error 2

Looking closer at the tail of the make output it looks like it is going 
through support for a bunch of character sets which are not install.

I recall nothing about turning off character support from my reading of 
the INSTALL file (or the README or any of the other docs I read).
-- 
Ken Dyke,
406.581.0495



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: error on build from source
@ 2004-01-18 10:10  Peter Eisentraut <peter_e@gmx.net>
  parent: kdyke@keycomputerconsultants.com
  0 siblings, 1 reply; 6+ messages in thread

From: Peter Eisentraut @ 2004-01-18 10:10 UTC (permalink / raw)
  To: kdyke@keycomputerconsultants.com; pgsql-admin

kdyke@keycomputerconsultants.com wrote:
> Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <URL:http://gcc.gnu.org/bugs.html; for instructions.

There you go.




^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: error on build from source
@ 2004-01-18 10:44  kdyke@keycomputerconsultants.com
  parent: Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 1 reply; 6+ messages in thread

From: kdyke@keycomputerconsultants.com @ 2004-01-18 10:44 UTC (permalink / raw)
  To: pgsql-admin

On Sun, Jan 18, 2004 at 11:10:58AM +0100, Peter Eisentraut (peter_e@gmx.net) wrote:
> kdyke@keycomputerconsultants.com wrote:
> > Internal error: Killed (program cc1)
> > Please submit a full bug report.
> > See <URL:http://gcc.gnu.org/bugs.html; for instructions.
> 
> There you go.

Postgres killed it.  I'm in the final stages of building a new server.  I 
have built a new kernel, postfix, and numerous system utilities with this 
same gcc.  Make check and testing all came out OK.

My initial post was in hopes that others had seen this and had a workaround 
for this issue.

I am running further tests including building an upgraded gcc.
-- 
Ken Dyke,
406.581.0495



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: error on build from source
@ 2004-01-18 18:54  Tom Lane <tgl@sss.pgh.pa.us>
  parent: kdyke@keycomputerconsultants.com
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2004-01-18 18:54 UTC (permalink / raw)
  To: kdyke@keycomputerconsultants.com; +Cc: pgsql-admin

kdyke@keycomputerconsultants.com writes:
> On Sun, Jan 18, 2004 at 11:10:58AM +0100, Peter Eisentraut (peter_e@gmx.net) wrote:
>> kdyke@keycomputerconsultants.com wrote:
>>> Internal error: Killed (program cc1)
>>> Please submit a full bug report.
>>> See <URL:http://gcc.gnu.org/bugs.html; for instructions.
>> 
>> There you go.

> Postgres killed it.

No, you have a buggy version of gcc.  We are not the people to report
the bug to.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2004-01-18 18:54 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-01-18 00:52 error on build from source kdyke@keycomputerconsultants.com
2004-01-18 03:30 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-01-18 06:59   ` kdyke@keycomputerconsultants.com
2004-01-18 10:10     ` Peter Eisentraut <peter_e@gmx.net>
2004-01-18 10:44       ` kdyke@keycomputerconsultants.com
2004-01-18 18:54         ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox