activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-970) Compiling fails under SuSe
Date Thu, 12 Oct 2006 03:08:16 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-970?page=all ]

Timothy Bish resolved AMQ-970.
------------------------------

    Resolution: Fixed

Removed the openwire compilation from the makefile, as this wasn;t supposed to be in yet,
my bad on that one.

We are phasing out the use of these makefiles though, so instead you should use the autogen.sh
and then ./configure to create the automake Makefiles.  This should result in a better build
experience.  Once we are done testing the new make system the old makefiles will be removed,
so its a good idea to start using the new ones now.  See the Readme.txt for details.

> Compiling fails under SuSe
> --------------------------
>
>                 Key: AMQ-970
>                 URL: https://issues.apache.org/activemq/browse/AMQ-970
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: CMS (C++ client)
>         Environment: gcc (GCC) 3.3.3 (SuSE Linux)
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> 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 for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> 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 build system type... x86_64-suse-linux
> checking host system type... x86_64-suse-linux
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld
> checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
> checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> 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 how to run the C++ preprocessor... g++ -E
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B 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/x86_64-suse-linux/bin/ld -m elf_x86_64) supports
shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/x86_64-suse-linux/bin/ld -m elf_x86_64
> checking if the linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the g++ linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports
shared libraries... yes
> 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/x86_64-suse-linux/bin/ld -m elf_x86_64) supports
shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works... yes
> checking if g77 supports -c -o file.o... yes
> checking whether the g77 linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports
shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking whether build environment is sane... yes
> checking whether byte ordering is bigendian... no
> checking for short... yes
> checking size of short... 2
> checking for int... yes
> checking size of int... 4
> checking for long... yes
> checking size of long... 8
> checking uuid.h usability... no
> checking uuid.h presence... no
> checking for uuid.h... no
> checking uuid/uuid.h usability... yes
> checking uuid/uuid.h presence... yes
> checking for uuid/uuid.h... yes
> checking objbase.h usability... no
> checking objbase.h presence... no
> checking for objbase.h... no
> checking repcdce.h usability... no
> checking repcdce.h presence... no
> checking for repcdce.h... no
> checking for pthread_create in -lpthread... yes
> checking for doxygen... no
> configure: WARNING: doxygen not found - will not generate any doxygen documentation
> checking for perl... /usr/bin/perl
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating activemq-cpp.pc
> config.status: creating src/main/Makefile
> config.status: creating src/examples/Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
>            Reporter: Tomas Lebovic
>         Assigned To: Timothy Bish
>
> Hi,
> Has anyone been able to compile the latest source under linux? The reason i ask is there
are some major issues (or is it just me) with paths/filenames:
> - g++ -frtti -pthread -O3 -DNDEBUG -D_REENTRANT 'src/main/activemq/connector/openwire/OpenWireFormatFactory.cpp'
> src/main/activemq/connector/openwire/OpenWireFormatFactory.cpp:18:63: activemq/connector/openwire/OpenwireFormatFactory.h:
No such file or directory
> the reason for this is the file is not actually named OpenwireFormatFactory.h but OpenWireFormatFactory.h
notice the capital W. hence *nix system doesn't pick it up. Same goes for OpenWireFormat.h
header file
> Next Issue.
> src/main/activemq/connector/openwire/OpenWireFormat.cpp:36:70: activemq/connector/openwire/marshal/v2/MarshallerFactory.h:
No such file or directory
> once again this is due the refrence being v2 but under the file system its actually V2.
> Next issue:
> - g++ -frtti -pthread -O3 -DNDEBUG -D_REENTRANT 'src/main/activemq/connector/openwire/OpenWireFormat.cpp'
> src/main/activemq/connector/openwire/OpenWireFormat.cpp: In member function `
>    activemq::connector::openwire::commands::DataStructure*
>    activemq::connector::openwire::OpenWireFormat::tightUnmarshalNestedObject(activemq::io::DataInputStream*,
>    activemq::connector::openwire::utils::BooleanStream*)':
> src/main/activemq/connector/openwire/OpenWireFormat.cpp:344: error: `byte'
>    undeclared (first use this function)
> src/main/activemq/connector/openwire/OpenWireFormat.cpp:344: error: (Each
>    undeclared identifier is reported only once for each function it appears
>    in.)
> src/main/activemq/connector/openwire/OpenWireFormat.cpp:344: error: syntax
>    error before `=' token
> src/main/activemq/connector/openwire/Ope
> Now either im doing something wrong and hopefully thats the case. But can someone please
post some more detailed instructions on the building process of the lib under linux?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message