KDE

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • qt on solaris

    5 answers - 818 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    truename a :
    I have looked up much documents. This wrong means I
    don't install solaris cc compiler,but solaris cc compiler is not free
    software,
    how can I do? can i use gcc to replace cc,but how can i do it?
    1) Sunstudio10 (with cc, CC, f90) is free at
    <http://opensolaris.org/os/;
    2) The only version of Qt with modified files for solaris cc ("Stefan's
    packages") is the 3.4.1, if I'm not wrong : it means that for 3.4.3,
    3.4.4, etc. the best way is gcc. For this you need only to have it at
    the first place in your path and to launch directly ./configure.
    Regards,
    Sergio
    This message is from the kde-solaris mailing list.
    Account management:
    Archives: http://lists.kde.org/.
    More info: http://www.kde.org/faq.html.
  • No.1 | | 1143 bytes | |

    Monday 21 November 2005 09:43, Sergio wrote:
    truename a :
    I have looked up much documents. This wrong means I
    don't install solaris cc compiler,but solaris cc compiler is not free
    software,
    how can I do? can i use gcc to replace cc,but how can i do it?

    1) Sunstudio10 (with cc, CC, f90) is free at
    <http://opensolaris.org/os/;

    2) The only version of Qt with modified files for solaris cc ("Stefan's
    packages") is the 3.4.1, if I'm not wrong : it means that for 3.4.3,
    3.4.4, etc. the best way is gcc. For this you need only to have it at
    the first place in your path and to launch directly ./configure.

    you can use qt-3.3.4 to build kde-3.4.x. qt-3.3.5 is a bug fix release over
    3.3.4, but it still needs some (fewer than 3.3.4) patches for Sun Studio
    10/11.

    Sun Studio 11 is free for everyone, on both Solaris SPARC and X86. i believe
    there's also a Sun Studio 11 for Linux, also free (i haven't installed it
    yet). it's a very nice compiler (very strict). Lars' instructions for
    installation requirements are very correct and useful.
  • No.2 | | 11574 bytes | |

    Hi ,

    If you build qt from source you need to add flag "-thread" to configure which
    adds threading support for qt-libs.

    R

    wrote:
    hi,thanks to Lars Tunkrans <lars.tunkrans (AT) bredband (DOT) net,Stefan Teleman,Sergio and Narendra Kumar.S.S.

    First i try to use gcc to replace cc in .profile,but still failed, maybe to modify ./configure can do .

    I download sunstduio11 and I comfiled qt 3.3.4 successfully, and this is my profile setting:

    PATH=$

    export PATH

    PATH=$QTDIR/bin:$PATH

    MANPATH=$QTDIR/doc/man:$MANPATH

    LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH

    export QTDIR PATH MANPATH LD_LIBRARY_PATH

    note: because I just use solaris-cc to compile cc,so i delete the path which I set as Lars Tunkrans <lars.tunkrans (AT) bredband (DOT) netdescripted .

    then I begin to compile kdevelop 3.2.3,but wrong as follow when i use ./configure

    # ./configure

    checking build system type i386-pc-solaris2.10

    checking host system type i386-pc-solaris2.10

    checking target system type i386-pc-solaris2.10

    checking for a BSD-compatible install admin/install-sh -c

    checking for -p flag to install no

    checking whether build environment is sane yes

    checking for gawk no

    checking for mawk no

    checking for nawk nawk

    checking whether make sets $(MAKE) yes

    checking for kde-config /opt/csw/kde-gcc/bin/kde-config

    checking where to install /opt/csw/kde-gcc (as returned by kde-config)

    checking for style of include used by make GNU

    checking for gcc gcc

    checking for C compiler default output file name a.out

    checking whether the C compiler works yes

    checking whether we are cross compiling no

    checking for suffix of executables

    checking for suffix of object files o

    checking whether we are using the GNU C compiler yes

    checking whether gcc accepts -g yes

    checking for gcc option to accept ANSI C none needed

    checking dependency style of gcc gcc3

    checking how to run the C preprocessor gcc -E

    checking for g++ g++

    checking whether we are using the GNU C++ compiler yes

    checking whether g++ accepts -g yes

    checking dependency style of g++ gcc3

    checking whether gcc is blacklisted no

    checking whether g++ supports -Wundef yes

    checking whether g++ supports -Wno-long-long yes

    checking whether g++ supports -Wno-non-virtual-dtor yes

    checking whether g++ supports -fno-exceptions yes

    checking whether g++ supports -fno-check-new yes

    checking whether g++ supports -fno-common yes

    checking whether g++ supports -fexceptions yes

    checking how to run the C++ preprocessor g++ -E

    checking whether g++ supports yes

    not using lib directory suffix

    checking for a sed that does not truncate output /opt/csw/bin/gsed

    checking for egrep egrep

    checking for ld used by gcc /usr/ccs/bin/ld

    checking if the linker (/usr/ccs/bin/ld) is GNU ld no

    checking for /usr/ccs/bin/ld option to reload object files -r

    checking for BSD-compatible nm /usr/ccs/bin/nm -p

    checking whether ln -s works yes

    checking how to recognise dependent libraries pass_all

    checking for ANSI C header files yes

    checking for sys/types.h yes

    checking for sys/stat.h yes

    checking for stdlib.h yes

    checking for string.h yes

    checking for memory.h yes

    checking for strings.h yes

    checking for inttypes.h yes

    checking for stdint.h yes

    checking for unistd.h yes

    checking dlfcn.h usability yes

    checking dlfcn.h presence yes

    checking for dlfcn.h yes

    checking for g77 no

    checking for f77 no

    checking for xlf no

    checking for frt no

    checking for pgf77 no

    checking for fort77 no

    checking for fl32 no

    checking for af77 no

    checking for f90 no

    checking for xlf90 no

    checking for pgf90 no

    checking for epcf90 no

    checking for f95 no

    checking for fort no

    checking for xlf95 no

    checking for ifc no

    checking for efc no

    checking for pgf95 no

    checking for lf95 no

    checking for gfortran no

    checking whether we are using the GNU Fortran 77 compiler no

    checking whether accepts -g no

    checking the maximum length of command line arguments

    262144

    checking command to parse /usr/ccs/bin/nm -p output from gcc object ok

    checking for objdir .libs

    checking for ar ar

    checking for ranlib ranlib

    checking for strip strip

    checking if gcc static flag works yes

    checking if gcc supports -fno-rtti -fno-exceptions no

    checking for gcc option to produce PIC -fPIC

    checking if gcc PIC flag -fPIC works yes

    checking if gcc supports -c -o file.o yes

    checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries y es

    checking whether -lc should be explicitly linked in yes

    checking dynamic linker characteristics solaris2.10 ld.so

    checking how to hardcode library paths into programs immediate

    checking whether stripping libraries is possible no

    checking for shl_load no

    checking for shl_load in -ldld no

    checking for dlopen yes

    checking whether a program can dlopen itself yes

    checking whether a statically linked program can dlopen itself yes

    checking if libtool supports shared libraries yes

    checking whether to build shared libraries yes

    checking whether to build static libraries no

    configure: creating libtool

    appending configuration tag "CXX" to libtool

    checking for ld used by g++ /usr/ccs/bin/ld

    checking if the linker (/usr/ccs/bin/ld) is GNU ld no

    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries y es

    checking for g++ option to produce PIC -fPIC

    checking if g++ PIC flag -fPIC works yes

    checking if g++ supports -c -o file.o yes

    checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries y es

    checking dynamic linker characteristics solaris2.10 ld.so

    checking how to hardcode library paths into programs immediate

    checking whether stripping libraries is possible no

    checking for shl_load (cached) no

    checking for shl_load in -ldld (cached) no

    checking for dlopen (cached) yes

    checking whether a program can dlopen itself (cached) yes

    checking whether a statically linked program can dlopen itself (cached) yes

    appending configuration tag "F77" to libtool

    checking for msgfmt msgfmt

    checking for gmsgfmt /opt/csw/bin/gmsgfmt

    checking for xgettext /usr/bin/xgettext

    found xgettext programs is not GNU xgettext; ignore it

    checking if C++ programs can be compiled yes

    checking for strlcat yes

    checking if strlcat needs custom prototype no

    checking for strlcpy yes

    checking if strlcpy needs custom prototype no

    checking for main in -lutil no

    checking for main in -lcompat no

    checking for crypt in -lcrypt yes

    checking for socklen_t yes

    checking for dnet_ntoa in -ldnet no

    checking for dnet_ntoa in -ldnet_stub no

    checking for inet_ntoa no

    checking for inet_ntoa in -lnsl yes

    checking for connect no

    checking for connect in -lsocket yes

    checking for remove yes

    checking for shmat yes

    checking for sys/types.h (cached) yes

    checking for stdint.h (cached) yes

    checking sys/bitypes.h usability no

    checking sys/bitypes.h presence no

    checking for sys/bitypes.h no

    checking for poll in -lpoll no

    checking Carbon/Carbon.h usability no

    checking Carbon/Carbon.h presence no

    checking for Carbon/Carbon.h no

    checking CoreAudio/CoreAudio.h usability no

    checking CoreAudio/CoreAudio.h presence no

    checking for CoreAudio/CoreAudio.h no

    checking if res_init needs -lresolv yes

    checking for res_init yes

    checking if res_init needs custom prototype no

    checking for killpg in -lucb no

    checking for int yes

    checking size of int 4

    checking for short yes

    checking size of short 2

    checking for long yes

    checking size of long 4

    checking for char * yes

    checking size of char * 4

    checking for dlopen in -ldl yes

    checking for shl_unload in -ldld no

    checking for size_t yes

    checking size of size_t 4

    checking for unsigned long yes

    checking size of unsigned long 4

    checking sizeof size_t == sizeof unsigned long yes

    checking crt_externs.h usability no

    checking crt_externs.h presence no

    checking for crt_externs.h no

    checking for _NSGetEnviron no

    checking for vsnprintf yes

    checking for snprintf yes

    checking for X libraries , headers

    checking for IceConnectionNumber in -lICE yes

    checking for libXext yes

    checking for pthread_create in -lpthread yes

    checking whether g++ supports -mt no

    checking for extra includes no

    checking for extra libs no

    checking for libz -lz

    checking for libpng -lpng -lz -lm

    checking for libjpeg6b no

    checking for libjpeg -ljpeg

    checking for perl /usr/bin/perl

    checking for Qt configure: error: Qt (>= Qt 3.2 and < 4.0) (library qt-mt) no t found. Please check your installation!

    For more details about this problem, look at the end of config.log.

    Make sure that you have compiled Qt with thread support!

    what's the matter?how can i compile qt with thread support?

    best whis to you!

    Linda


    >>you can use qt-3.3.4 to build kde-3.4.x. qt-3.3.5 is a bug fix release over



    >>3.3.4, but it still needs some (fewer than 3.3.4) patches for Sun Studio



    >>10/11.



    >>Sun Studio 11 is free for everyone, on both Solaris SPARC and X86. i believe



    >>there's also a Sun Studio 11 for Linux, also free (i haven't installed it



    >>yet). it's a very nice compiler (very strict). Lars' instructions for



    >>installation requirements are very correct and useful.



    >>



    >>Stefan Teleman 'Nobody Expects the Spanish Inquisition'



    >>steleman (AT) nyc (DOT) rr.com -Monty Python


    This message is from the kde-solaris mailing list.
    Account management:
    Archives: http://lists.kde.org/.
    More info: http://www.kde.org/faq.html.

    This message is from the kde-solaris mailing list.
    Account management:
    Archives: http://lists.kde.org/.
    More info: http://www.kde.org/faq.html.
  • No.3 | | 679 bytes | |

    Tuesday 22 November 2005 13:17, wrote:

    checking for Qt configure: error: Qt (>= Qt 3.2 and < 4.0) (library
    qt-mt) no t found. Please check your installation!

    For more details about this problem, look at the end of config.log.

    Make sure that you have compiled Qt with thread support!

    what's the matter?how can i compile qt with thread support?

    Did you check that there is no typo in the QTDIR-path?
    i.e.:

    ls /

    ?

    best regards
    rainald

    This message is from the kde-solaris mailing list.
    Account management:
    Archives: http://lists.kde.org/.
    More info: http://www.kde.org/faq.html.
  • No.4 | | 1181 bytes | |

    Tuesday 22 November 2005 22:57, wrote:
    Hi , I find this by type ./configure , after I ./configure -thread
    -debug , I type gmake,the wrong appeared as follow : cc -c -KPIC
    cc: unrecognized option ' -KPIC'
    cc1:error invalid option 't'

    What KPIC stand for? How can I continue my work?

    Hi.

    it looks like you are using gcc but are using CFLAGS/CXXFLAGS for SunStudio.

    this won't work. :-)
    -KPIC is a SunStudio compiler flag and it tells the compiler to generate
    Position Independent Code.

    the equivalent for gcc is -fPIC -DPIC

    the 't' invalid options comes from passing -mt to gcc/g -mt is also a
    SunStudio compiler flag, and it tells the compiler to use thread-safe API's
    and interfaces. it is usually used in conjunction with -D_REENTRANT. you can
    pass -D_REENTRANT to gcc, but gcc will not like '-mt' at all.

    i would recommend you check your , and make
    sure they are appropriate for gcc/g otherwise you will run into endless
    grief. the compiler flags for gcc/g++ and SunStudio10 are incompatible (with
    the exception of basic -I and -L).

    :-)
  • No.5 | | 1643 bytes | |

    schrieb:
    hi,thanks to Lars Tunkrans <lars.tunkrans (AT) bredband (DOT) net,Stefan Teleman,Sergio and Narendra Kumar.S.S.

    First i try to use gcc to replace cc in .profile,but still failed, maybe to modify ./configure can do .

    I download sunstduio11 and I comfiled qt 3.3.4 successfully, and this is my profile setting:

    PATH=$
    export PATH

    ^ typo?

    PATH=$QTDIR/bin:$PATH
    MANPATH=$QTDIR/doc/man:$MANPATH
    LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
    export QTDIR PATH MANPATH LD_LIBRARY_PATH
    []
    # ./configure
    []
    checking for kde-config /opt/csw/kde-gcc/bin/kde-config
    checking where to install /opt/csw/kde-gcc (as returned by kde-config)
    checking for style of include used by make GNU
    checking for gcc gcc
    []
    checking for g++ g++
    [] ^^^
    checking for Qt configure: error: Qt (>= Qt 3.2 and < 4.0) (library qt-mt) no t found. Please check your installation!
    For more details about this problem, look at the end of config.log.
    Make sure that you have compiled Qt with thread support!

    what's the matter?how can i compile qt with thread support?

    If you have built QT with SunStudio CC you also have to build all
    of the KDE-apps with SunStudio CC.
    This is because the C++ ABI of GNU g++ is different from that of
    SunStudio CC.

    To build a QT-library with thread support you have to add -thread to the
    list of options for configure.

    Gerhard

    This message is from the kde-solaris mailing list.
    Account management:
    Archives: http://lists.kde.org/.
    More info: http://www.kde.org/faq.html.

Re: qt on solaris


max 4000 letters.
Your nickname that display:
In order to stop the spam: 9 + 9 =
QUESTION ON "KDE"

EMSDN.COM