----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
on 6/22/2000 11:12 PM, "jan kad" <[EMAIL PROTECTED]> wrote:
> O.K. I now know what went wrong. Building a jserv DSO
> requires GNU ld version 2.9x.x. I had gcc/ld version
> 2.8.1 on my solaris. I spent a fair bit of time
> on this.
That is funny. I use Sun's ld and egcs and everything works fine. There is
no reason to use GNU ld on a Solaris system and it is probably better to use
Sun's ld since it probably knows the most about the system.
> I went back to the readme, install files to see if
> I missed reading something that states this
> requirement. No, I didn't missing anything that was
> documented. The requirement states that "(GCC version
> 2.7.2 is fine) or the EGCS C compiler".
No where in the installation documentation did it say to use GNU ld. It only
said to use gcc.
> What happens is that, when you run configure, it spits
> out a lot of information on the stdout. If the GNU ld
> version is anything less that 2.9.1, it outputs a
> message saying something to the effect "building DSO
> needs a more recent version of ld. Since you don't
> have it, shared object setting is turned off." Mind
> you, things scroll by faster. If you don't save this
> output to a file, you won't realize that there was a
> problem. The tail end of the configuration output
> indicates that everything was generated/configured
> O.K.
So, what you are complaining about is that you can't read fast enough and
were not clueful enough to actually bother reading the output...even AFTER
you had problems. Hmm...
> Thinking the configuration was fine
EVEN THOUGH IT GAVE YOU AN ERROR AS WELL AS THE DESCRIPTION OF HOW TO FIX
THE PROBLEM! DUH!
> Granted, I should have noticed the few lines that
> scrolled by fast during the configuration processes
> indicating the problem.
Uh. Yea.
> I do think that the configure
> script should have told me that I asked for DSO and
> that couldn't be done because of an older 'ld'
> present on the system.
Uh, it did. Need me to quote you on what it said?
> It should have also told me
> my options were to upgrade my GNU ld, or use the
> solaris (vendor) ld or generate a non-DSO version of
> jserv and aborted the configuration process.
Ok, the portion that does this checking is actually part of the
autoconf/libtool system and not under our control. You really should
complain to the people who make those tools, not us.
Also, that really isn't a complete failure. It is only a warning that that
version cannot be used (and that is what it gave you). The configure stuff
does a lot more than simply compile your C code.
> It was also plain wrong to simply copy a .a file
> as a .so file.
Well, it expected that you had a properly configured system. Not much we can
do about that. Especially given the fact that it gave you the warning
message.
> According to an earlier poster, a guestimated 100,000
> users have successfully downloaded and build jserv.
> It is not the software's fault if I am having
> trouble doing it. Right? ;-)
> --jk
So far, you have been the only person with this problem in 3 years.
Obviously everyone else got it right or at least bothered to read the output
of the configure scripts.
> (Don't get me wrong, I am thrilled about using jserv.
> I know I am getting it all for free, all the great
> work by great people. I don't mind having glitches
> like these. I know they get ironed out quickly with
> the community participation.)
Ok, so a glitch that was caused because you didn't read the output of the
configuration script is our fault? Give me a break dude.
Sorry to be so harsh on you, but your attempts at blaming JServ for
everything really are taken personally. I have worked my ass of for years on
this stuff and deserve a bit more credit than "i know i am getting it all
for free" and "i can't read the output of the configure script so it must be
JServ's fault and my boss won't let me use it because i couldn't configure
it".
cya,
-jon
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
