Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/
On Sat, Feb 25, 2012 at 12:19 AM, grant schoep [email protected]
wrote:
I’m on CentOS 5.7
gcc 4.1.2 20080704 (Red Hat 4.1.2-51)
Ruby 1.9.2p290
Note, that I am on a 64 bit machine, and I see it did compile all with
-fPIC. I did a bit of google to trying to figure out what this message
means. Saw some things that hinted at issues with global name space
issues,
but nothing helped. I can drop out the 3 changes from your commit and
all
builds fine.
I think GTK_TYPE_MESSAGE_TYPE should be defined as Gtk::MessageType.
(similar to Gtk::PositionType and others)
Just for your information, I’ve attached enum list.
I think GTK_TYPE_RESPONSE_TYPE should be defined as Gtk::ResponseType.
I get a link problem now with this addition. Everything gets done
compiling, then at the link step it bombs
/usr/bin/ld: init.o: relocation R_X86_64_PC32 against `Init_gtk_infobar’
can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[1]: *** [gtk2.so] Error 1
I’m on CentOS 5.7
gcc 4.1.2 20080704 (Red Hat 4.1.2-51)
Ruby 1.9.2p290
Thank for this report. I have no clue at the moment on how to fix this
error.
Futhermore I am on a 32 bits machine.
Which kernel are you using ? (uname -a)
Did you try to compile from a clean tree?
(
make realclean
ruby1.9 extconf.rb gtk2
make
)
Can someone using a 64 bits machine confirm this bug ?
Thanks for your compliment.
I agree that GTK_TYPE_MESSAGE_TYPE should be defined as Gtk::MessageType
but they are all ready defined as Gtk::MessageDialog::Type that is why I
redefined it as Gtk::InfoBar::Type.
I propose to define GTK_TYPE_MESSAGE_TYPE as Gtk::MessageType,
keep Gtk::MessageDialog::Type for compatibility sake and remove
Gtk::InfoBar::Type as no one except me should have write code
including this constant.
I agree that GTK_TYPE_MESSAGE_TYPE should be defined as Gtk::MessageType
but they are all ready defined as Gtk::MessageDialog::Type that is why I
redefined it as Gtk::InfoBar::Type.
I propose to define GTK_TYPE_MESSAGE_TYPE as Gtk::MessageType,
keep Gtk::MessageDialog::Type for compatibility sake and remove
Gtk::InfoBar::Type as no one except me should have write code
including this constant.
also focuses on allowing computing to be delivered as a service.
error.
Futhermore I am on a 32 bits machine.
Which kernel are you using ? (uname -a)
Did you try to compile from a clean tree?
(
make realclean
ruby1.9 extconf.rb gtk2
make
)
Can someone using a 64 bits machine confirm this bug ?