shibaniahegde / tweetx

Automatically exported from code.google.com/p/tweetx
0 stars 0 forks source link

compile error on Ubuntu #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. ./configure
2. make
3. fatal error in ma face

What version of the product are you using? On what operating system?
Ubuntu 11.10

Please provide any additional information below.

make[4]: Wejście do katalogu 
`/home/pawel/src/tweetx-0.1/src/libsrc/timestamper'
/bin/bash ../../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
-I../../..     -g -O2 -MT timestamper.lo -MD -MP -MF .deps/timestamper.Tpo -c 
-o timestamper.lo timestamper.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I../../.. -g -O2 -MT timestamper.lo -MD 
-MP -MF .deps/timestamper.Tpo -c timestamper.cc  -fPIC -DPIC -o 
.libs/timestamper.o
In file included from timestamper.cc:1:0:
timestamper.h: In member function ‘void TimeStamper::EndTime(size_t&)’:
timestamper.h:44:5: error: cannot call constructor ‘log::Log::Log’ directly 
[-fpermissive]
timestamper.h:44:5: error:   for a function-style cast, remove the redundant 
‘::Log’ [-fpermissive]
make[4]: *** [timestamper.lo] Błąd 1

Original issue reported on code.google.com by pawel.ol...@gmail.com on 22 Jan 2012 at 5:16

Attachments:

GoogleCodeExporter commented 9 years ago
I'm having the same issue on gentoo amd64

Original comment by y...@blesmrt.net on 10 Feb 2012 at 1:23

GoogleCodeExporter commented 9 years ago
This is happens in source from tweetx-0.1.tar.gz

I patched the log.h (patch attached, though idk if it can be applied with 
patch), then i was able to build the program, configure my user/pwd and then 
was greeted with screen as can be seen 
http://code.google.com/p/tweetx/wiki/Screenshots Just the only text i saw was 
the "tweetx 0.1" header and i couldnt figure out how to do anything in it.

Original comment by y...@blesmrt.net on 10 Feb 2012 at 1:45

Attachments:

GoogleCodeExporter commented 9 years ago
This issue has been solved: https://code.google.com/p/tweetx/issues/detail?id=21

Original comment by tom.hima...@gmail.com on 4 Jul 2013 at 11:15