Installing only libraries of Qt 2.1?

[Ken Brakey]

Ivan Martinez wrote:
> 
> I am using gcc 2.95.2 19991024 (release). I think the right word is "fails" and
> not "crashes", sorry.
> This is what I do:
> Uncompress qt-2.1.0 in /usr/local
> Keep the changes in .profile as they were for qt-1.44
> Link qt to qt-2.1.0 in /usr/local
> Go to qt-2.1.0 directory
> Run ./configure
> Run make
> ...Get some warnings, I don't care
> ...After 45 minutes compiling I get this error:
> 
> /usr/bin/ld: cannot open output file widgets: Is a directory
> collect2: ld returned 1 exit status
> make[2]: *** [widgets] Error 1
> make[2]: Leaving directory '/usr/local/qt-2.1.0.19991215/examples/widgets'
> make[1]: *** [widgets] Error 2
> make[1]: Leaving directory '/usr/local/qt-2.1.0.19991215/examples'
> make: *** [examples] Error 2
> 
> Any solution? Thanks in advance.

NOT A SOLUTION, A workaround. The EXAMPLES don't matter.
Try 'make -k'. The LIB compiles, some examples do NOT.
Ken

> 
> Paul Derbyshire wrote:
> 
> > At 04:38 PM 2/6/00 +0000, you wrote:
> > >How to install only the libraries of Qt 2.1? What I have is a single
> > >package (qt-2.1.0-snapshot-19991215.tar.gz) and compilation crashes in my
> > >computer.
> >
> > Let me get this right, the *compilation* crashes?
> >
> > What compiler are you using? gcc, egcs, pgcc? what version? If the compiler
> > ever gives "internal compiler error" messages or segfaults that's incorrect
> > behavior and should probably be reported as a compiler bug, especially if
> > it is consistent every time you try to compile a certain source, but there
> > are different bug report addresses for gcc, egcs, and pgcc, and getting
> > them mixed up can get you flamed :-)
> >
> > (If the error is not consistent and happens sporadically compiling anything
> > large, it's a hardware problem -- flaky ram chip probably. A bad simm will
> > often first make its presence known by interfering with compute-intensive
> > things like large compilations, prime95/mprime, and seti at home, before
> > eventually causing frequent app faults for less compute-intensive and
> > eventually even for humdrum work. The same goes for an overheating cpu,
> > except that the problem isn't progressive, it's just there to some degree
> > or another, or absent. And huge compiles, e.g. kernel recompiles, will bomb
> > on a home PC perhaps one in every twenty times with perfect hardware due to
> > cosmic rays, that's how much CPU work is involved -- it is extremely
> > sensitive. NASA ought to be able to double the effectiveness of the Compton
> > Gamma Ray Observatory by replacing the expensive CCD array with a cheap
> > Linux box that keeps trying to compile copies of the kernel :-) -- there
> > are military grade hardware setups, e.g. Crays, Connection Machines, big
> > mainframes, and Macintoshes, that are better shielded and more robust ...
> > but you can't run linux on these :-) BTW that's why Macintosh computers are
> > so expensive -- it's the hardware and the export licensing. Macs are
> > subject to export control because of their usability in mission critical
> > military applications!)
> >
> > --
> >    .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
> > -()  <  circles, and bark is not smooth, nor does lightning travel in a
> >    `*'  straight line."    -------------------------------------------------
> >         -- B. Mandelbrot  |http://surf.to/pgd.net derbyshire at globalserve.net
> > _____________________ ____|________                          Paul Derbyshire
> > Programmer & Humanist|ICQ: 10423848|
> 
> --
> Ivan Martinez (Rodriguez)
> Bch in Computer Science - MSc student
> http://www.student.dtu.dk/~u990873