[OpenIndiana-discuss] Σχετ: Re: Σχετ: Taglib/cppunit for Mediatomb

[Stefan Müller-Wilken]

... if it is not for the good challenge, would it help to wrap a precompiled Mediatomb installation and put it somewhere?

Cheers
 Stefan
________________________________________
Von: Rainer Heilke [rheilke at dragonhearth.com]
Gesendet: Montag, 20. Januar 2014 11:21
An: openindiana-discuss at openindiana.org
Betreff: Re: [OpenIndiana-discuss] Σχετ: Re:  Σχετ:  Taglib/cppunit for Mediatomb

Based on Alan's comments, I installed a newer version of gcc from the
repository.
./configure CC=/usr/gcc/4.3/bin/gcc CXX=/usr/gcc/4.3/bin/gcc
LD=/usr/gcc/4.3/bin/gcc

died with:
  /usr/gcc/4.3/bin/gcc -DHAVE_CONFIG_H -I. -I../../config
-I../../include -I../../include -g -O2 -MT TestAssert.lo -MD -MP -MF
.deps/TestAssert.Tpo -c TestAssert.cpp -fPIC -DPIC -o .libs/TestAssert.o
In file included from ../../include/cppunit/portability/FloatingPoint.h:5,
                  from TestAssert.cpp:2:
/usr/gcc/4.3/lib/gcc/i386-pc-solaris2.11/4.3.3/include-fixed/math.h:46:26:
error: iso/math_iso.h: No such file or directory
/usr/gcc/4.3/lib/gcc/i386-pc-solaris2.11/4.3.3/include-fixed/math.h:353:27:
error: floatingpoint.h: No such file or directory
TestAssert.cpp: In function âvoid CppUnit::assertDoubleEquals(double,
double, double, CppUnit::SourceLine, const std::string&)â:
TestAssert.cpp:20: error: âfabsâ was not declared in this scope
gmake[2]: *** [TestAssert.lo] Error 1
gmake[2]: Leaving directory `/data/build/cppunit-1.12.1/src/cppunit'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/data/build/cppunit-1.12.1/src'
gmake: *** [all-recursive] Error 1

This is with:
gcc -v
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.11/3.4.3/specs
Configured with:
/home/jt/OIDEV/151A-PRESTABLE9/newbuilds/sfw/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as
--with-ld=/usr/ccs/bin/ld --without-gnu-ld
--enable-languages=c,c++,f77,objc --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-20050802)

So, no further ahead.

Rainer



On 1/19/2014 8:25 PM, Rainer Heilke wrote:
> My understanding was that the CC=/usr/bin/gcc defined what CC was for
> the rest of the line. It was one of my later efforts, after the first
> 67 failed. And I wouldn't be able to discern the flags; I was never
> much of a programmer (I did have my moments, but I was a sysadmin
> before anything else), and have been out of the game completely for
> almost 6 years.
>
> Rainer
>
> On 1/19/2014 5:25 PM, Alan Coopersmith wrote:
>> On 01/19/14 02:30 PM, Rainer Heilke wrote:
>>>   $ ./configure CC=/usr/bin/gcc CXX=CC CXXFLAGS=-pta
>>> -instances=static -mt -xtarget=pentium3 -g -features=no%transitions
>>> LD=CC
>>
>> Trying to mix the Gnu C compiler with the Studio C++ compiler like that
>> is most likely to end with a set of flags that works with neither.
>>
>> Either use CC=cc & CXX=CC for the Studio tools or CC=gcc CXX=g++ for
>> the GNU ones.  (Most of those CXXFLAGS look like Studio, not GNU ones.)
>>
>

--
Mind the Gap
Web: http://www.dragonhearth.com

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

________________________________
Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022