[opensuse-packaging] Missin gtk/gtk.h
I tried to package codelite in my home repo[1].
The build was succeeded except openSUSE Factory[2].
It can't find a gtk header file
* Mariusz Fik (fisiu82@jabster.pl) [20100412 15:43]:
It can't find a gtk header file
. How can I fix it?
Add gtk2-devel to BuildRequires . Phillip -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dnia poniedziałek, 12 kwietnia 2010 o 16:01:21 Philipp Thomas napisał(a):
* Mariusz Fik (fisiu82@jabster.pl) [20100412 15:43]:
It can't find a gtk header file
. How can I fix it? Add gtk2-devel to BuildRequires .
Phillip
Did You check spec file? I guess, no, You didn't. Here is a part of my spec file: BuildRequires: gcc-c++ gtk2-devel wxGTK-devel >= 2.8.10 -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
* Mariusz Fik (fisiu82@jabster.pl) [20100412 16:08]:
Did You check spec file? I guess, no, You didn't.
You could just as well have written that BuildRequires does contain gtk2-devel. BTW, codelite does build for factory. Seems like you just need to wait everything works again. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 4/12/2010 at 15:43, Mariusz Fik
wrote: I tried to package codelite in my home repo[1]. The build was succeeded except openSUSE Factory[2]. It can't find a gtk header file . How can I fix it?
Some debug: rpm -ql gtk2-devel | grep gtk.h /usr/include/gtk-2.0/gtk/gtk.h so you're missing a -I/usr/include/gtk-2.0 in your build command. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Some debug: rpm -ql gtk2-devel | grep gtk.h /usr/include/gtk-2.0/gtk/gtk.h
so you're missing a -I/usr/include/gtk-2.0 in your build command. But builds for <= 11.2 was successful. Btw, how can I add an additional 'include' path in %build? -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
On 4/12/2010 at 16:27, Mariusz Fik
wrote: Some debug: rpm -ql gtk2-devel | grep gtk.h /usr/include/gtk-2.0/gtk/gtk.h so you're missing a -I/usr/include/gtk-2.0 in your build command. But builds for <= 11.2 was successful. Btw, how can I add an additional 'include' path in %build?
That depends what exactly your app is doing... a 'blind' shot would be CFLAGS="-I[...]" but that can or can not work. i'll have a look at your package in the upcoming 30 minutes and hope to be able to tell you after what goes wrong and why. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 4/12/2010 at 16:27, Mariusz Fik
wrote: Some debug: rpm -ql gtk2-devel | grep gtk.h /usr/include/gtk-2.0/gtk/gtk.h so you're missing a -I/usr/include/gtk-2.0 in your build command. But builds for <= 11.2 was successful. Btw, how can I add an additional 'include' path in %build?
already back :: That was quick. As so often, the error is higher up in the build log. In your case: + ./configure --prefix=/usr --plugins-dir=/usr/lib64/codelite --disable-debian --disable-desktop_icon --disable-make_symlink Generating Makefile... Generating sdk/codelite_indexer/Makefile... Generating sdk/codelite_cppcheck/Makefile... Generating Debugger/Makefile... Generating Gizmos/Makefile... Generating cscope/Makefile... Generating Subversion2/Makefile... Generating CodeFormatter/Makefile... Generating Copyright/Makefile... Generating UnitTestCPP/Makefile... Generating ExternalTools/Makefile... Generating SnipWiz/Makefile... Generating wxformbuilder/Makefile... Generating abbreviation/Makefile... Generating SymbolView/Makefile... Generating ContinuousBuild/Makefile... Generating QmakePlugin/Makefile... Generating cppchecker/Makefile... + /usr/bin/make -j 4 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' 'CXXFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' Package libpng12 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpng12.pc' to the PKG_CONFIG_PATH environment variable Package 'libpng12', required by 'cairo', not found Package libpng12 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpng12.pc' to the PKG_CONFIG_PATH environment variable Package 'libpng12', required by 'cairo', not found Package libpng12 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpng12.pc' to the PKG_CONFIG_PATH environment variable Package 'libpng12', required by 'cairo', not found ./le_makerevision.sh So it all starts with libpng12.pc which is missing. (of course it is. Factory contains libpng14). Do you feel like having enough hints to get this sorted? Or shall I still look at it? Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dnia poniedziałek, 12 kwietnia 2010 o 16:27:43 Mariusz Fik napisał(a):
Some debug: rpm -ql gtk2-devel | grep gtk.h /usr/include/gtk-2.0/gtk/gtk.h
so you're missing a -I/usr/include/gtk-2.0 in your build command.
But builds for <= 11.2 was successful. Btw, how can I add an additional 'include' path in %build?
Ok, I found in gcc doc some tips and I added this part to spec file: %if 0%{?suse_version} > 1120 export CPATH=$CPATH:/usr/include/gtk-2.0 export CPATH=$CPATH:/usr/include/glib-2.0/ export CPATH=$CPATH:/usr/lib/glib-2.0/include/ export CPATH=$CPATH:/usr/include/pango-1.0/ export CPATH=$CPATH:/usr/lib/gtk-2.0/include/ export CPATH=$CPATH:/usr/include/atk-1.0/ export CPATH=$CPATH:/usr/include/cairo/ %endif Build was successful this time but is it OK to define 'include' path in this way? -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
On 4/12/2010 at 16:46, Mariusz Fik
wrote: Ok, I found in gcc doc some tips and I added this part to spec file: %if 0%{?suse_version} > 1120 export CPATH=$CPATH:/usr/include/gtk-2.0 export CPATH=$CPATH:/usr/include/glib-2.0/ export CPATH=$CPATH:/usr/lib/glib-2.0/include/ export CPATH=$CPATH:/usr/include/pango-1.0/ export CPATH=$CPATH:/usr/lib/gtk-2.0/include/ export CPATH=$CPATH:/usr/include/atk-1.0/ export CPATH=$CPATH:/usr/include/cairo/ %endif
Build was successful this time but is it OK to define 'include' path in this
That would just be an ugly way to work around a deeper problem (libpng12 / libpng14 upgrade... see my other mail). Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dnia poniedziałek, 12 kwietnia 2010 o 16:50:37 Dominique Leuenberger napisał(a):
On 4/12/2010 at 16:46, Mariusz Fik
wrote: Ok, I found in gcc doc some tips and I added this part to spec file:
%if 0%{?suse_version} > 1120 export CPATH=$CPATH:/usr/include/gtk-2.0 export CPATH=$CPATH:/usr/include/glib-2.0/ export CPATH=$CPATH:/usr/lib/glib-2.0/include/ export CPATH=$CPATH:/usr/include/pango-1.0/ export CPATH=$CPATH:/usr/lib/gtk-2.0/include/ export CPATH=$CPATH:/usr/include/atk-1.0/ export CPATH=$CPATH:/usr/include/cairo/ %endif
Build was successful this time but is it OK to define 'include' path in this
That would just be an ugly way to work around a deeper problem (libpng12 / libpng14 upgrade... see my other mail).
Dominique
I fund that my cairo package (also in my home repo) was build with libpng12. CodeLite needs cairo-devel (from my repo) and finally cairo needs libpng12. I'll rebuild cairo with libpng14. This should fix the problem You mentioned. -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
On 4/12/2010 at 17:06, Mariusz Fik
wrote: I fund that my cairo package (also in my home repo) was build with libpng12. CodeLite needs cairo-devel (from my repo) and finally cairo needs libpng12. I'll rebuild cairo with libpng14. This should fix the problem You mentioned.
your base problem seems to be that all buildings are disabled and as such all changes in Factory that happen will not trigger rebuilds for you. This probably brings you to the problem then. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dnia poniedziałek, 12 kwietnia 2010 o 17:15:07 Dominique Leuenberger napisał(a):
On 4/12/2010 at 17:06, Mariusz Fik
wrote: I fund that my cairo package (also in my home repo) was build with libpng12. CodeLite needs cairo-devel (from my repo) and finally cairo needs libpng12. I'll rebuild cairo with libpng14. This should fix the problem You mentioned.
your base problem seems to be that all buildings are disabled and as such all changes in Factory that happen will not trigger rebuilds for you. This probably brings you to the problem then.
Dominique
You're right. I didn't focus on obs for Factory. In the meantime there were many changes, updates, fixes... I enabled autobuilding for most of my packages for Factory. Need to prepare all of them to upcoming 11.3. When cairo got rebuilt, codelite was successful built ;) Sorry for troubles. -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member
* Mariusz Fik (fisiu82@jabster.pl) [20100412 16:47]:
%if 0%{?suse_version} > 1120 export CPATH=$CPATH:/usr/include/gtk-2.0 export CPATH=$CPATH:/usr/include/glib-2.0/ export CPATH=$CPATH:/usr/lib/glib-2.0/include/ export CPATH=$CPATH:/usr/include/pango-1.0/ export CPATH=$CPATH:/usr/lib/gtk-2.0/include/ export CPATH=$CPATH:/usr/include/atk-1.0/ export CPATH=$CPATH:/usr/include/cairo/ %endif
This is plain wrong! The correct way to get the neccessary paths is to call pkgconfig, which would succeed if you would call the right pkgconfig for libpng!
Build was successful this time but is it OK to define 'include' path in this way?
No! Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
* Philipp Thomas (pth@suse.de) [20100412 17:13]: It does build in the internal build system, so it's just a matter of waiting until a cairo that has been build with libpng14 is available. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Dominique Leuenberger
-
Mariusz Fik
-
Philipp Thomas