RSS/Atom feed Twitter
Site is read-only, email is disabled

building from cvs

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

building from cvs Roberto Winter 06 Mar 04:37
building from cvs William Skaggs 06 Mar 16:51
  building from cvs Roberto Winter 07 Mar 06:21
  building from cvs Sven Neumann 07 Mar 08:40
Roberto Winter
2006-03-06 04:37:45 UTC (about 18 years ago)

building from cvs

hello to all,
tried to build the cvs gimp on debian unstable and got this:

gcc -g -O2 -Wall -o .libs/gimp-2.3 app_procs.o main.o batch.o errors.o sanity.o units.o gui/libappgui.a actions/libappactions.a dialogs/libappdialogs.a menus/libappmenus.a display/libappdisplay.a tools/libapptools.a widgets/libappwidgets.a pdb/libapppdb.a vectors/libappvectors.a plug-in/libappplug-in.a core/libappcore.a paint/libapppaint.a xcf/libappxcf.a text/libapptext.a file/libappfile.a config/libappconfig.a
paint-funcs/libapppaint-funcs.acomposite/libappcomposite.a base/libappbase.a
../libgimpwidgets/.libs/libgimpwidgets-2.0.so../libgimpmodule/.libs/libgimpmodule- 2.0.so ../libgimpcolor/.libs/libgimpcolor-2.0.so../libgimpthumb/.libs/libgimpthumb- 2.0.so ../libgimpmath/.libs/libgimpmath-2.0.so../libgimpconfig/.libs/libgimpconfig- 2.0.so ../libgimpbase/.libs/libgimpbase-2.0.so -L/usr/X11R6/lib /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so -lXrandr -lXi -lXinerama -lXext /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so /usr/lib/libXcursor.so /usr/lib/libcairo.so /usr/lib/libXrender.so -lX11 /usr/lib/libart_lgpl_2.so /usr/lib/libpangoft2- 1.0.so /usr/lib/libpango-1.0.so /usr/lib/libgobject-2.0.so/usr/lib/libgmodule- 2.0.so -ldl -lfontconfig /usr/lib/libfreetype.so -lz -pthread /usr/lib/libgthread-2.0.so /usr/lib/libglib-2.0.so -Wl,--rpath -Wl,/opt/gimp/lib
gui/libappgui.a(gui.o)(.text+0x9cb): In function `gui_restore_callback': /home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui.c:396: undefined reference to `actions_init'
gui/libappgui.a(gui.o)(.text+0x9d3):/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui.c:397: undefined reference to `global_action_factory' gui/libappgui.a(gui.o)(.text+0xdd1): In function `gui_exit_after_callback': /home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui.c:520: undefined reference to `actions_exit'
gui/libappgui.a(gui.o)(.text+0xb9d): In function `gui_restore_after_callback':
/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui.c:452: undefined reference to `dialogs_show_toolbox'
gui/libappgui.a(gui.o)(.text+0x1085): In function `gui_image_disconnect': /home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui.c:638: undefined reference to `dialogs_show_toolbox'
gui/libappgui.a(gui-vtable.o)(.text+0x8c2): In function `gui_menus_create_item':
/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui-vtable.c:503: undefined reference to `plug_in_actions_add_path' gui/libappgui.a(gui-vtable.o
)(.text+0x91e):/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui- vtable.c:499: undefined reference to `plug_in_actions_add_proc' gui/libappgui.a(gui-vtable.o)(.text+0x98a): In function `gui_menus_delete_item':
/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui-vtable.c:531: undefined reference to `plug_in_actions_remove_proc' gui/libappgui.a(gui-vtable.o)(.text+0x9e5): In function `gui_menus_create_branch':
/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/gui/gui-vtable.c:547: undefined reference to `plug_in_actions_add_branch' tools/libapptools.a(gimpvectortool.o)(.text+0x2c1a): In function `gimp_vector_tool_stroke_vectors':
/home/rhwinter/docs/programacao/gimp/cvs/gimp/app/tools/gimpvectortool.c:1897: undefined reference to `stroke_dialog_new' collect2: ld returned 1 exit status
make[3]: ** [gimp-2.3] Erro 1
make[3]: Leaving directory
`/home/rhwinter/docs/programacao/gimp/cvs/gimp/app' make[2]: ** [all-recursive] Erro 1
make[2]: Leaving directory
`/home/rhwinter/docs/programacao/gimp/cvs/gimp/app' make[1]: ** [all-recursive] Erro 1
make[1]: Leaving directory `/home/rhwinter/docs/programacao/gimp/cvs/gimp' make: ** [all] Erro 2

can anyone help me with this?

thanks a lot in advance, roberto

William Skaggs
2006-03-06 16:51:18 UTC (about 18 years ago)

building from cvs

Roberto Winter wrote:

tried to build the cvs gimp on debian unstable and got this:

Please file a Bugzilla report about this. There are several possible explanations, and it would be good to be able to deal with them in a more systematic way than this mailing list.

Also, in your bug report, it would be helpful for you to tell us what verions of gcc you are using, and what kind of hardware you are running on.

Thanks, -- Bill


______________ ______________ ______________ ______________ Sent via the CNPRC Email system at primate.ucdavis.edu

Roberto Winter
2006-03-07 06:21:49 UTC (about 18 years ago)

building from cvs

mmm...
I updated earlier today from cvs and tried to build again. all went smoothly this time.
thanks anyway.
roberto

On 3/6/06, William Skaggs wrote:

Roberto Winter wrote:

tried to build the cvs gimp on debian unstable and got this:

Please file a Bugzilla report about this. There are several possible explanations, and it would be good to be able to deal with them in a more systematic way than this mailing list.

Also, in your bug report, it would be helpful for you to tell us what verions of gcc you are using, and what kind of hardware you are running on.

Thanks, -- Bill

______________ ______________ ______________ ______________ Sent via the CNPRC Email system at primate.ucdavis.edu

Sven Neumann
2006-03-07 08:40:27 UTC (about 18 years ago)

building from cvs

Hi,

"William Skaggs" writes:

Roberto Winter wrote:

tried to build the cvs gimp on debian unstable and got this:

Please file a Bugzilla report about this. There are several possible explanations, and it would be good to be able to deal with them in a more systematic way than this mailing list.

It is more than appropriate to ask on the mailing-list in such a case. The likelihood that this is a bug is very small. It is most likely just a problem with either the CVS checkout or the build environment. Having bug reports for such problems would be rather annoying. Our bug-tracker is not a help forum. Please don't encourage people to use it as such.

Sven