make test failures on solaris5.10

[Richard Hubbell <ri...@yahoo.com>]

I ran "make test"

Safe to ignore? Bugs? Something mis-configured? 

testflock: \ld.so.1: tryread: fatal: libgcc_s.so.1: open failed: No such file or directory -ld.so.1: tryread: fatal: libgcc_s.so.1: open failed: No such file or directory
FAILED 2 of 3

testoc: -ld.so.1: occhild: fatal: libgcc_s.so.1: open failed: No such file or directory SUCCESS

testpipe :|/bin/bash: line 1: 19228 Broken Pipe ./$prog




      

Re: make test failures on solaris5.10

[Richard Hubbell <ri...@yahoo.com>]

--- On Mon, 9/22/08, Paul Querna <ch...@force-elite.com> wrote:

> From: Paul Querna <ch...@force-elite.com>
> Subject: Re: make test failures on solaris5.10
> To: dev@httpd.apache.org
> Date: Monday, September 22, 2008, 3:46 PM
> Richard Hubbell wrote:
> > I ran "make test"
> > 
> > Safe to ignore? Bugs? Something mis-configured? 
> > 
> > testflock: \ld.so.1: tryread: fatal:
> libgcc_s.so.1: open failed: No such file or directory
> -ld.so.1: tryread: fatal: libgcc_s.so.1: open failed: No
> such file or directory
> > FAILED 2 of 3
> > 
> > testoc: -ld.so.1: occhild: fatal: libgcc_s.so.1: open
> failed: No such file or directory SUCCESS
> > 
> > testpipe :|/bin/bash: line 1: 19228 Broken Pipe
> ./$prog
> 
> I believe these are the tests for APR?

Yes.

> 
> dev@apr.apache.org is likely a better place.

Didn't know there was a separate list. But everything has it's own list.
apr comes in the httpd tar ball....

> 
> But, it appears perhaps you need to hack with your LD Path
> since you 
> compiled with GCC on solaris 10, which can cause pain.....
> as you seem 
> to have found :-)

Yes, turns out I needed to run crle -u -l /usr/local/lib
(Thanks to Peter for that!)

Thanks.

> 
> If you hack the ld path to find libgcc_s, and still get
> errors, it would 
> be good to bring them up on the dev@apr list.
> 
> Thanks,
> Paul


      

Re: make test failures on solaris5.10

[Paul Querna <ch...@force-elite.com>]

Richard Hubbell wrote:
> I ran "make test"
> 
> Safe to ignore? Bugs? Something mis-configured? 
> 
> testflock: \ld.so.1: tryread: fatal: libgcc_s.so.1: open failed: No such file or directory -ld.so.1: tryread: fatal: libgcc_s.so.1: open failed: No such file or directory
> FAILED 2 of 3
> 
> testoc: -ld.so.1: occhild: fatal: libgcc_s.so.1: open failed: No such file or directory SUCCESS
> 
> testpipe :|/bin/bash: line 1: 19228 Broken Pipe ./$prog

I believe these are the tests for APR?

dev@apr.apache.org is likely a better place.

But, it appears perhaps you need to hack with your LD Path since you 
compiled with GCC on solaris 10, which can cause pain..... as you seem 
to have found :-)

If you hack the ld path to find libgcc_s, and still get errors, it would 
be good to bring them up on the dev@apr list.

Thanks,
Paul