You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Mladen Turk <mt...@mappingsoft.com> on 2002/01/10 22:55:58 UTC
Solaris 2.5.1 builds?
Hi,
I got my hands on some archaic Sun IPX with Solaris 2.5.1, and I installed
the latest patch bundle, gcc302, binutils 2.11.2, libtool1.4 and automake.
Now building Apache1.3.22 goes well but latest 2.0 from CVS or 28 beta
fails.
Did someone build 2.0 on that platform?
Any leads would be more then welcome :-)
MT.
Re: Solaris 2.5.1 builds?
Posted by Ian Holsman <ia...@apache.org>.
Mladen Turk wrote:
> Hi,
>
> I got my hands on some archaic Sun IPX with Solaris 2.5.1, and I installed
> the latest patch bundle, gcc302, binutils 2.11.2, libtool1.4 and automake.
>
> Now building Apache1.3.22 goes well but latest 2.0 from CVS or 28 beta
> fails.
> Did someone build 2.0 on that platform?
>
Jees.. thats old.
sun is/has about to drop support for Solaris 2.6 soon/already.
> Any leads would be more then welcome :-)
>
> MT.
>
>
>
Re: Solaris 2.5.1 builds?
Posted by Mladen Turk <mt...@mappingsoft.com>.
----- Original Message -----
From: "Aaron Bannert" <aa...@clove.org>
To: <de...@httpd.apache.org>
Sent: Friday, January 11, 2002 6:47 PM
Subject: Re: Solaris 2.5.1 builds?
> >
> > Well core gets dumped for all test, but interesting almost all the test
are
> > passed except
> > the testsock which complains that libgcc_s.so.1 open failed.
>
> The core dumps are interesting, can you post a stack trace?
>
gdb ./.libs/testfile
(gdb) run
All tests passed OK
Program received signal SIGSEGV, Segmentation fault.
0xef787160 in __do_global_dtors_aux ()
(gdb) bt
#0 0xef787160 in __do_global_dtors_aux ()
#1 0xef79a778 in _fini ()
#2 0xef7cae30 in ?? ()
#3 0xef7caf14 in ?? ()
#4 0xef5dceb8 in _exithandle ()
(gdb)
MT.
Re: Solaris 2.5.1 builds?
Posted by Aaron Bannert <aa...@clove.org>.
On Fri, Jan 11, 2002 at 06:47:03PM +0100, Mladen Turk wrote:
[snip]
> using gcc3.0.2
> For a start just tried to build the apr.
>
> bash-2.05$ ./configure --prefix=/whatever \
> --build=sparc-sun-solaris2.251
> --with-gnu-ld \
> --disable-ipv6
> ...
> bash-2.05$ make
> ...
> bash-2.05$ make test
> ...
> bash-2.05$ setenv LD_LIBRARY_PATH /usr/local/lib
> bash-2.05$ ./testfile
Does libgcc_s.so* live in /usr/local/lib? I don't see your LDFLAGS line
in your posting, but I'm assuming you set it.
[snip]
> All tests passed OK
> Segmentation Fault (core dumped)
> bash-2.05$
>
>
>
> Well core gets dumped for all test, but interesting almost all the test are
> passed except
> the testsock which complains that libgcc_s.so.1 open failed.
The core dumps are interesting, can you post a stack trace?
As for testsock, it's simply not finding libgcc_s.so.1. Try running
ldd .libs/testsock (or ldd .libs/lt-testsock if you have it).
-aaron
Re: Solaris 2.5.1 builds?
Posted by Mladen Turk <mt...@mappingsoft.com>.
----- Original Message -----
From: "Justin Erenkrantz" <je...@ebuilt.com>
To: <de...@httpd.apache.org>
Sent: Friday, January 11, 2002 2:09 AM
Subject: Re: Solaris 2.5.1 builds?
> That should fix it. If not, find libgcc_s.so.1 and add
> -R/path/to/libgcc/dir to LDFLAGS. -- justin
OK... did
using gcc3.0.2
For a start just tried to build the apr.
bash-2.05$ ./configure --prefix=/whatever \
--build=sparc-sun-solaris2.251
--with-gnu-ld \
--disable-ipv6
...
bash-2.05$ make
...
bash-2.05$ make test
...
bash-2.05$ setenv LD_LIBRARY_PATH /usr/local/lib
bash-2.05$ ./testfile
APR File Functions Test
=======================
Initializing APR OK
Creating the main pool we'll use OK
Creating the second pool we'll use OK
Testing file functions.
Opening file OK
Checking filename test.fil
Writing to the file OK
Checking we wrote everything OK
Moving to the start of file OK
This platform supports files_like_sockets, testing...
Making file look like a socket OK
Checking for incoming data OK
End of files as sockets test.
Reading from the file OK
Checking what we read OK
Adding user data to the file OK
Getting user data from the file OK
Checking the data we got OK
Getting fileinfo OK
Closing the file OK
Stat'ing file OK
Getting groupname OK
Comparing group ID's OK
(gid's for other match)
Getting username OK
Comparing users OK
(uid's for root match)
Deleting the file OK
Making sure it's gone OK
Testing Directory functions.
Making directory OK
Creating a file in the new directory OK
Opening directory OK
Reading directory OK
Getting Information about the file...
File name OK
File type OK
File size OK
Done checking file information
Rewind directory OK
Closing directory OK
Removing file from directory OK
Removing directory OK
Creating the file OK
Closing the file OK
Removing the file OK
Checking it's gone OK
Testing file read functions.
Buffered file tests OK
Unbuffered file tests OK
More buffered file tests OK
More unbuffered file tests OK
Even more buffered file tests OK
Even more unbuffered file tests OK
All read tests OK
All tests passed OK
Segmentation Fault (core dumped)
bash-2.05$
Well core gets dumped for all test, but interesting almost all the test are
passed except
the testsock which complains that libgcc_s.so.1 open failed.
Any clues?
MT.
Re: Solaris 2.5.1 builds?
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Fri, Jan 11, 2002 at 01:55:31AM +0100, Mladen Turk wrote:
> dav/main -export-dynamic -o dftables dftables.lo -lm -lsocket -lnsl -ldl
> /export/home/mladent/apache/current/srclib/apr-util/xml/expat/lib/libexpat.l
> a
> ./dftables > /export/home/mladent/apache/current/srclib/pcre/chartables.c
> ld.so.1: dftables: fatal: libgcc_s.so.1: open failed: No such file or
> directory
> Killed
Ah, this affects all Solaris platforms. Configuration of libtool
should have emitted a warning about this - you should use GNU
binutils or follow these instructions. Something like this:
*** Warning: Releases of GCC earlier than version 3.0 cannot reliably
*** create self contained shared libraries on Solaris systems, without
*** introducing a dependency on libgcc.a. Therefore, libtool is disabling
*** -no-undefined support, which will at least allow you to build shared
*** libraries. However, you may find that when you link such libraries
*** into an application without using GCC, you have to manually add
*** \`gcc --print-libgcc-file-name\` to the link command. We urge you to
*** upgrade to a newer version of GCC. Another option is to rebuild your
*** current GCC to use the GNU linker from GNU binutils 2.9.1 or newer.
That should fix it. If not, find libgcc_s.so.1 and add
-R/path/to/libgcc/dir to LDFLAGS. -- justin
Re: Solaris 2.5.1 builds?
Posted by Mladen Turk <mt...@mappingsoft.com>.
----- Original Message -----
From: "Justin Erenkrantz" <je...@ebuilt.com>
To: <de...@httpd.apache.org>
Sent: Thursday, January 10, 2002 11:29 PM
Subject: Re: Solaris 2.5.1 builds?
> On Thu, Jan 10, 2002 at 10:55:58PM +0100, Mladen Turk wrote:
> > Hi,
> >
> > I got my hands on some archaic Sun IPX with Solaris 2.5.1, and I
installed
> > the latest patch bundle, gcc302, binutils 2.11.2, libtool1.4 and
automake.
>
> Well, it'd be nice if you told us what the error message was.
>
It fails on
/bin/sh
/export/home/mladent/apache/current/srclib/apr/libtool --silent --mode=link
gcc -pthreads -O2 -DSOLARIS2=5.1 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT
-DAP_HAVE_DESIGNATED_INITIALIZER -I. -I/export/home/mladent/apache/current
/os/unix -I/export/home/mladent/apache/current/server/mpm/prefork -I/export/
home/mladent/apache/current/modules/http -I/export/home/mladent/apache/curre
nt/modules/proxy -I/export/home/mladent/apache/current/include -I/export/hom
e/mladent/apache/current/srclib/apr/include -I/export/home/mladent/apache/cu
rrent/srclib/apr-util/include -I/export/home/mladent/apache/current/modules/
dav/main -export-dynamic -o dftables dftables.lo -lm -lsocket -lnsl -ldl
/export/home/mladent/apache/current/srclib/apr-util/xml/expat/lib/libexpat.l
a
./dftables > /export/home/mladent/apache/current/srclib/pcre/chartables.c
ld.so.1: dftables: fatal: libgcc_s.so.1: open failed: No such file or
directory
Killed
> Personally, I don't have access to anything less than a Solaris 7
> box, so I can't really be of any help. I'd recommend using NetBSD
> on the IPX rather than Solaris. I can't even begin to fathom how
> long it would take to compile httpd on there. -- justin
$ ./buildconf
15 minutes
$ CC="gcc" CFLAGS="-O2" \
./configure --prefix=/export/home/mladent/apache/build/2
26 minutes
$ make
...
fails with the previous error after 41 minutes.
Well, I think that the entire build would be finished in less then two
hours, can you beat that :-)
MT.
Re: Solaris 2.5.1 builds?
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Thu, Jan 10, 2002 at 10:55:58PM +0100, Mladen Turk wrote:
> Hi,
>
> I got my hands on some archaic Sun IPX with Solaris 2.5.1, and I installed
> the latest patch bundle, gcc302, binutils 2.11.2, libtool1.4 and automake.
>
> Now building Apache1.3.22 goes well but latest 2.0 from CVS or 28 beta
> fails.
> Did someone build 2.0 on that platform?
>
> Any leads would be more then welcome :-)
Well, it'd be nice if you told us what the error message was.
However, I'm not aware of any code requiring Solaris 2.6+. I know
several people who use Solaris 2.6 regularly with httpd-2.0, so we
definitely have support for Solaris 2.6 and beyond.
Personally, I don't have access to anything less than a Solaris 7
box, so I can't really be of any help. I'd recommend using NetBSD
on the IPX rather than Solaris. I can't even begin to fathom how
long it would take to compile httpd on there. -- justin