pg.ddx.io  pgsql-testers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables
4+ messages / 3 participants
[nested] [flat]

* PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables
@ 2010-03-26 14:18  Lou Picciano <loupicciano@comcast.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Lou Picciano @ 2010-03-26 14:18 UTC (permalink / raw)
  To: pgsql-testers




Testing Friends: 


Having a wee bit of trouble ./configure-ing on openSolaris snv_134 (x86) 
Ultimately, we are running into the much-dreaded 'C compiler cannot create executables' wall... 
Some snippets from config.log: 







Reading specs from /usr/local/lib/gcc/i386-pc-solaris2.10/3.4.6/specs 



Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared --enable-languages=c,c++,f77 



Thread model: posix 



gcc version 3.4.6 



configure:3260: $? = 0 



configure:3267: gcc -V >&5 



gcc: `-V' option must have argument 



configure:3271: $? = 1 



configure:3294: checking for C compiler default output file name 



configure:3316: gcc conftest.c >&5 



ld: fatal: file values-Xa.o: open failed: No such file or directory 



ld: fatal: file processing errors. No output written to a.out 



collect2: ld returned 1 exit status 



configure:3320: $? = 1 



configure:3358: result: 



configure: failed program was: 



| /* confdefs.h. */ 



| #define PACKAGE_NAME "PostgreSQL" 



| #define PACKAGE_TARNAME "postgresql" 



| #define PACKAGE_VERSION "9.0alpha4" 



| #define PACKAGE_STRING "PostgreSQL 9.0alpha4" 



| #define PACKAGE_BUGREPORT "pgsql-bugs@postgresql.org" 



| #define PG_VERSION "9.0alpha4" 



| #define PG_MAJORVERSION "9.0" 



| #define USE_INTEGER_DATETIMES 1 



| #define DEF_PGPORT 5432 



| #define DEF_PGPORT_STR "5432" 



| #define BLCKSZ 8192 



| #define RELSEG_SIZE 131072 



| #define XLOG_BLCKSZ 8192 



| #define XLOG_SEG_SIZE (16 * 1024 * 1024) 



| /* end confdefs.h. */ 



| 



| int 



| main () 



| { 



| 



| ; 



| return 0; 



| } 



configure:3364: error: in `</path/to/source/tree>/postgresql-9.0alpha4': 



configure:3366: error: C compiler cannot create executables 




However, later in the log: 






configure_args=' '\''--with-as=/usr/local/bin/as'\'' '\''--with-ld=/usr/local/bin/ld'\'' '\''--enable-shared'\'' '\''--enable-languages=c,c++,f77'\''' 




I do have 'supporting' applications, like as, gnu ld and bison, in /usr/local/bin - in priority in my PATH: how does this jibe with the line?: 






Reading specs from /usr/local/lib/gcc/i386-pc-solaris2.10/3.4.6/specs 




I'm heading now into lines 3316, 3364 and 3366 to see what's up... 


Or is using SunStudio a must on openSolaris? 


Regards, Lou Picciano 

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

* Re: PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables
@ 2010-03-26 17:58  Josh Berkus <josh@agliodbs.com>
  parent: Lou Picciano <loupicciano@comcast.net>
  0 siblings, 0 replies; 4+ messages in thread

From: Josh Berkus @ 2010-03-26 17:58 UTC (permalink / raw)
  To: Lou Picciano <loupicciano@comcast.net>; +Cc: pgsql-testers@postgresql.org, Zdenek Kotala <Zdenek.Kotala@Sun.COM>; Bjorn Munch <Bjorn.Munch@Sun.COM>

On 3/26/10 7:18 AM, Lou Picciano wrote:
> Or is using SunStudio a must on openSolaris?

In my experience?  Yes.

However, cc'ing Zdenek and Bjorn who have way more Solaris-compile-fu
than me.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com



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

* Re: PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables
@ 2010-03-26 19:41  Lou Picciano <loupicciano@comcast.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Lou Picciano @ 2010-03-26 19:41 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-testers@postgresql.org, Zdenek Kotala <Zdenek.Kotala@Sun.COM>; Bjorn Munch <Bjorn.Munch@Sun.COM>

Josh, 


Many thanks for getting back. Some new information to add to the mix: 


Imagine, if you will, that our openSolaris 10 x86 snv_134 is a very 'standard' install of the OS. 


On top of it, we've added key packages from Steve Christensen's SunFreeware - into /usr/local - 
and then favored those applications/libraries within the environment with: 




PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin 


This brought us to my last email: C compiler cannot create executables. 


Stubbornly (and granted, academically at this point), we've been trying to find what tools may be missing, and have installed a few which may be needed - to achieve the build without SunStudio. All the usual suspects are there in /usr/local/bin: grep, ar, awk, gcc, sed, readline, perl - and ld. What other(s) may we be missing? 


Still, could not get a successful compile. 


- I did install SunStudio12u1 and, (you know where this is headed!) 


PostgreSQL configures and builds beautifully! So, is it safe to assume configure is 'finding' one or more tools outside of /usr/local? Probably...? 


...strangely, though, configure still reports it's using Solaris ld, even though --with-gnu-ld has been specified: 






checking for ld used by GCC... /usr/ccs/bin/ld 

checking if the linker (/usr/ccs/bin/ld) is GNU ld... no 


- - - - But now, to make things a bit more complicated: The real point to the whole exercise: 


Is to build and run PostgreSQL inside an open Solaris ipkg-branded zone. To effect this test, a simple zone has been set up with /usr/local as a loopback (lofs) device. Of course, this zone doesn't 'see' anything in the /opt path. 



As in the root zone, configure starts to fail at about line 3316: 





configure:3316: gcc conftest.c >&5 

ld: fatal: file values-Xa.o: open failed: No such file or directory 

ld: fatal: file processing errors. No output written to a.out 

collect2: ld returned 1 exit status 


suggesting to me that I've got one or two utilities missing. I'll have to develop my script reading skills to deconstruct this; meanwhile... Hoping Zdenek or Bjorn will have an idea. Wonder if there's a way to direct configure to gnu-ld directly? 


Yes, a very long email - but hopefully this will be useful to others moving down the same road... 


Regards, Lou Picciano 

--- 
Subject: Re: [TESTERS] PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables 

On 3/26/10 7:18 AM, Lou Picciano wrote: 
> Or is using SunStudio a must on openSolaris? 

In my experience? Yes. 

However, cc'ing Zdenek and Bjorn who have way more Solaris-compile-fu 
than me. 

-- Josh Berkus 
PostgreSQL Experts Inc. 
http://www.pgexperts.com 

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

* Re: PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables
@ 2010-03-29 08:03  Zdenek Kotala <Zdenek.Kotala@Sun.COM>
  parent: Lou Picciano <loupicciano@comcast.net>
  0 siblings, 0 replies; 4+ messages in thread

From: Zdenek Kotala @ 2010-03-29 08:03 UTC (permalink / raw)
  To: Lou Picciano <loupicciano@comcast.net>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-testers@postgresql.org, Bjorn Munch <Bjorn.Munch@Sun.COM>

There is my answer. I hope that it helps:

You use own tools in /usr/local like grep and so on. But all these tools
are already on the system in /usr/gnu/bin directory. Most of them are
patched for better integration with solaris. Use own compiled version is
risky and IIRC only gmake is what you really need for build. All other
original Solaris tools works fine.

I run buildfarm on Solaris snv and it works fine. You can see
configuration here:

http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=luna_moth&dt=2010-03-26%2022:06:00

	Zdenek


Lou Picciano píše v pá 26. 03. 2010 v 19:41 +0000:
> Josh,
> 
> 
> Many thanks for getting back.  Some new information to add to the mix:
> 
> 
> Imagine, if you will, that our openSolaris 10 x86 snv_134 is a very
> 'standard' install of the OS.
> 
> 
> On top of it, we've added key packages from Steve Christensen's
> SunFreeware - into /usr/local - 
> and then favored those applications/libraries within the environment
> with:
> 
> 
>         PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> 
> 
> This brought us to my last email: C compiler cannot create
> executables.
> 
> 
> Stubbornly (and granted, academically at this point), we've been
> trying to find what tools may be missing, and have installed a few
> which may be needed - to achieve the build without SunStudio.  All the
> usual suspects are there in /usr/local/bin: grep, ar, awk, gcc, sed,
> readline, perl - and ld.  What other(s) may we be missing?
> 
> 
> Still, could not get a successful compile.
> 
> 
>  - I did install SunStudio12u1 and, (you know where this is headed!)
> 
> 
> PostgreSQL configures and builds beautifully!  So, is it safe to
> assume configure is 'finding' one or more tools outside
> of /usr/local?  Probably...?
> 
> 
> ...strangely, though, configure still reports it's using Solaris ld,
> even though --with-gnu-ld has been specified:
> 
> 
>         checking for ld used by GCC... /usr/ccs/bin/ld
>         checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
> 
> 
> - - - - But now, to make things a bit more complicated: The real point
> to the whole exercise:
> 
> 
> Is to build and run PostgreSQL inside an open Solaris ipkg-branded
> zone.  To effect this test, a simple zone has been set up
> with /usr/local as a loopback (lofs) device.  Of course, this zone
> doesn't 'see' anything in the /opt path.
> 
> 
> As in the root zone, configure starts to fail at about line 3316:
> 
> 
>         configure:3316: gcc    conftest.c  >&5
>         ld: fatal: file values-Xa.o: open failed: No such file or
>         directory
>         ld: fatal: file processing errors. No output written to a.out
>         collect2: ld returned 1 exit status
> 
> 
> suggesting to me that I've got one or two utilities missing.  I'll
> have to develop my script reading skills to deconstruct this;
> meanwhile...  Hoping Zdenek or Bjorn will have an idea.  Wonder if
> there's a way to direct configure to gnu-ld directly?
> 
> 
> Yes, a very long email - but hopefully this will be useful to others
> moving down the same road...
> 
> 
> Regards,  Lou Picciano
> 
> ---
> Subject: Re: [TESTERS] PostgreSQL 9.0alpha4: openSolaris 10 x86
> snv_134: configure issues: C compiler cannot create executables
> 
> On 3/26/10 7:18 AM, Lou Picciano wrote:
> > Or is using SunStudio a must on openSolaris?
> 
> In my experience?  Yes.
> 
> However, cc'ing Zdenek and Bjorn who have way more Solaris-compile-fu
> than me.
> 
>                                   -- Josh Berkus
>                                      PostgreSQL Experts Inc.
>                                      http://www.pgexperts.com
> 





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


end of thread, other threads:[~2010-03-29 08:03 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-03-26 14:18 PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables Lou Picciano <loupicciano@comcast.net>
2010-03-26 17:58 ` Josh Berkus <josh@agliodbs.com>
2010-03-26 19:41 Re: PostgreSQL 9.0alpha4: openSolaris 10 x86 snv_134: configure issues: C compiler cannot create executables Lou Picciano <loupicciano@comcast.net>
2010-03-29 08:03 ` Zdenek Kotala <Zdenek.Kotala@Sun.COM>

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