> Hi. > > The ARC Cases for the WebStack NG Project have been > submitted for review (and > hopefully approval), and i would like to ask our > community's input regarding two > important questions which have come up during our > discussions: > > 1. Should the initial components released for this > project include the 64-bit > bits in the initial Integration ? > > 2. The currently proposed Apache 2.2.4 integration > installs Apache in > /usr/apache2, thereby _overwriting_ the existing > Apache 2.0.x. Valid arguments > have been made pro, and against this approach, with > the suggestion that Apache > 2.2.4 installs in /usr/apache2.2, thereby preserving > the existing /usr/apache2. > However, this alternate location would *not* alter > the EOF/EOL timeout announced > for Apache 2.0.x. > > What are the community's views on this ?
I've hit a problem very recently with the stock /usr/apache2/ and Subversion. When it was time to link, I got the infamous "WRONG ELf CLASS: ELF32" error, whereby upon inspection I determined that all the libraries in /usr/apache2/ are 32-bit! The problem is, there did not seem to be any 64-bit libraries delivered with the stock Apache2 in Solaris. So may I suggest to deliver both 32-bit (lib/) and 64-bit (sparcv9/ and amd64/) libraries? I know it's more work. On the other hand, delivering one or the other is a double edged sword: on sparc, 32-bit code is faster in most cases, but almost everything else is compiled 64-bit, so it becomes a problem when it's time to link; on i86pc, 64-bit code is faster, but there needs to be support for 32-bit binaries as well, since that platform must still support both 32- and 64-bit binaries and libraries. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
