Re: [Gimp-developer] help compiling babl
On Thu, Aug 22, 2019 at 03:43:25PM -0600, Akkana Peck wrote: > Marco Ciampa via gimp-developer-list writes: > > On Tue, Aug 13, 2019 at 02:26:50AM +0200, Marco Ciampa via > > gimp-developer-list wrote: > > > On Mon, Aug 12, 2019 at 08:38:45PM +0300, Alexandre Prokoudine via > > > gimp-developer-list wrote: > > > > Hello, > > > > > > > > You should be using the Meson build system now. > > > > > > Doh, I missed that! > > > It works now, thank you! > > > > I talked too quickly... now it is GIMP that does not compile (due to > > babl...): > > I had a lot of trouble adjusting my build scripts for babl's meson > build. So once I got it working, I ended up rewriting the GIMP wiki > build instructions to reflect what worked for me. > > https://wiki.gimp.org/wiki/Hacking:Building > > There are also some additions in the Hacking:Building/Linux page > (linked at the bottom) but it's mostly a discussion of why PREFIX > is important (I didn't write it, someone else did, but it seemed > worth keeping) and a discussion of how to run the GIMP you just built. > > Try it out -- and if it turns out that it's still incomplete, let > me know what needs to be changed (or update it yourself, if you > prefer). > > I know nothing of the Windows and Mac building pages: I don't > build on those platforms, but it would be great if someone who > does could keep them up to date. > > I should mention that my build page rewrites are from shortly after > babl switched to meson, but don't reflect any meson instructions for > gegl or gimp, so eventually Hacking:Building will need to be updated again. > > ...Akkana I re-read the wiki and found it very informative THANKS. I managed to get GIMP compiled and working in /usr/local but I'll definitely want to follow the wiki advices and have it compiled locally in my home. Now that it works I can do some experiments. Thanks again for your patience... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On Wed, Aug 28, 2019 at 01:17:33PM +0200, Michael Schumacher wrote: > Am 28.08.19 um 13:09 schrieb Marco Ciampa via gimp-developer-list: > > >> Retry: now (that apparently devs switched to meson also in GEGL, now it > >> does not compile > > > Found! Apparetly it was missing a package, whose lack, meson was not able > > to detect ... resolved with: > > > > sudo apt install libgirepository1.0-dev > > You could make it a habit to be on the #gimp IRC channel - we've gone > through this some weeks ago, and you'd likely have had someone suggest > it the moment you asked about it :) Yes, you are right, of course, sometimes I just do not do what I know I should do (for various reasons). > > perhaps gegl devs should add a test or something? > > > > Anyway now I have a problem with the GIMP compilation... > > > > CCLD script-fu > > //usr/local/lib/libgegl-0.4.so.0: undefined reference to > > `babl_format_get_n_components@V0_1_0' > > //usr/local/lib/libgegl-0.4.so.0: undefined reference to > > `babl_model_with_space@V0_1_0' > > Are you sure the correct babl is picked up? Threre where some old versions that were picked up before the newer ones... again you were right! > Figuring this out would also be something more easily done in a more > interactive medium. Yes (again) of course, sorry and thanks for the patience... PS: I finally got GIMP compiled, thanks to you all... -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
Am 28.08.19 um 13:09 schrieb Marco Ciampa via gimp-developer-list: >> Retry: now (that apparently devs switched to meson also in GEGL, now it does >> not compile > Found! Apparetly it was missing a package, whose lack, meson was not able > to detect ... resolved with: > > sudo apt install libgirepository1.0-dev You could make it a habit to be on the #gimp IRC channel - we've gone through this some weeks ago, and you'd likely have had someone suggest it the moment you asked about it :) > perhaps gegl devs should add a test or something? > > Anyway now I have a problem with the GIMP compilation... > > CCLD script-fu > //usr/local/lib/libgegl-0.4.so.0: undefined reference to > `babl_format_get_n_components@V0_1_0' > //usr/local/lib/libgegl-0.4.so.0: undefined reference to > `babl_model_with_space@V0_1_0' Are you sure the correct babl is picked up? Figuring this out would also be something more easily done in a more interactive medium. -- Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On Fri, Aug 23, 2019 at 02:17:10AM +0200, Marco Ciampa via gimp-developer-list wrote: > Retry: now (that apparently devs switched to meson also in GEGL, now it does > not compile > also gegl grrr) > > ninja > [9/529] Generating Gegl-0.4.gir with a custom command. > FAILED: gegl/Gegl-0.4.gir > /usr/bin/g-ir-scanner --no-libtool --namespace=Gegl --nsversion=0.4 > --warn-all --output gegl/Gegl-0.4.gir --c-include=gegl.h > -I/home/marco/git/gitlab/gnome/gegl/gegl > -I/home/marco/git/gitlab/gnome/gegl/build/gegl -I./. -I../. -I./gegl/. > -I../gegl/. -I./gegl/buffer -I../gegl/buffer -I./gegl/graph -I../gegl/graph > -I./gegl/module -I../gegl/module -I./gegl/opencl -I../gegl/opencl > -I./gegl/operation -I../gegl/operation -I./gegl/process -I../gegl/process > -I./gegl/property-types -I../gegl/property-types > --filelist=/home/marco/git/gitlab/gnome/gegl/build/gegl/2cd4258@@gegl-0.4@sha/Gegl_0.4_gir_filelist > --include=GLib-2.0 --include=GObject-2.0 --include=Babl-0.1 > --symbol-prefix=gegl --identifier-prefix=Gegl --cflags-begin -DHAVE_CONFIG_H > -Winit-self -Wmissing-declarations -Wmissing-prototypes > -Wold-style-definition -Wpointer-arith -Wno-deprecated-declarations > -mfpmath=sse -mmmx -msse -msse2 -msse4.1 -I./. -I../. -I./gegl/. -I../gegl/. > -I./gegl/buffer -I../gegl/buffer -I./gegl/graph -I > ../gegl/graph -I./gegl/module -I../gegl/module -I./gegl/opencl > -I../gegl/opencl -I./gegl/operation -I../gegl/operation -I./gegl/process > -I../gegl/process -I./gegl/property-types -I../gegl/property-types > -I/usr/local/include/babl-0.1 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0/ > --cflags-end --library gegl-0.4 > -L/home/marco/git/gitlab/gnome/gegl/build/gegl > -L/usr/local/lib/x86_64-linux-gnu -L/usr/local/lib/x86_64-linux-gnu > --extra-library=babl-0.1 --extra-library=glib-2.0 --extra-library=gio-2.0 > --extra-library=gobject-2.0 --extra-library=m --extra-library=gmodule-2.0 > Couldn't find include 'GLib-2.0.gir' (search path: > '['/home/marco/.local/share/flatpak/exports/share/gir-1.0', > '/var/lib/flatpak/exports/share/gir-1.0', > '/usr/share/gnome-flashback-metacity/gir-1.0', > '/home/marco/.local/share/flatpak/exports/share/gir-1.0', > '/var/lib/flatpak/exports/share/gir-1.0', '/usr/local/share/gir-1.0', > '/usr/share/gir-1.0', '/var/lib/snapd/desktop/gir-1.0', '/usr/share/gir-1.0', > '/usr/share/gir-1.0', '/usr/share/gir-1.0']') > [14/529] Generating module_common_gpl3.c with a meson_exe.py custom command. > ninja: build stopped: subcommand failed. Found! Apparetly it was missing a package, whose lack, meson was not able to detect ... resolved with: sudo apt install libgirepository1.0-dev perhaps gegl devs should add a test or something? Anyway now I have a problem with the GIMP compilation... CCLD script-fu //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_n_components@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_model_with_space@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_fish@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_icc_make_space@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_palette_set_palette@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_process@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_get_model_flags@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_type@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_has_alpha@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_new_palette@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_with_space@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_exit@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_init@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_is_palette@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_exists@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_bytes_per_pixel@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_get_name@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_encoding@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_space@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_model@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_ticks@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_model@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to
Re: [Gimp-developer] help compiling babl
> > Elle Stone writes: > > Thanks! for updating the wiki. In case it helps, the paths for setting up > > the prefix vary from one distribution to the next, for example are very > > different for Debian Sid compared to Gentoo. > > Thanks, Elle, If the paths are distro-dependent, they're almost > certainly wrong for Win and Mac too, so I'll add a note that the paths > are just examples and need to be adjusted for each system. Thanks to you both for that, I was surprised that it needed the $PREFIX/lib/x86_64-linux-gnu paths. This was on a LM-19.2 and I followed the Wiki which had Elle's suggestions. Owen ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
Elle Stone writes: > Thanks! for updating the wiki. In case it helps, the paths for setting up > the prefix vary from one distribution to the next, for example are very > different for Debian Sid compared to Gentoo. Thanks, Elle, If the paths are distro-dependent, they're almost certainly wrong for Win and Mac too, so I'll add a note that the paths are just examples and need to be adjusted for each system. On my Debian system (Testing), I didn't need the to add the $PREFIX/lib/x86_64-linux-gnu library directories; everything was installed in $GIMP_PREFIX/lib. But if you needed them, I'm sure other people will as well. I think what I'll do is change the main build page to say the variables there are just an example, then add a section to the Linux build page with the two variable lists you gave for Sid and Gentoo as well as my Testing list. It's a bummer that these vary so much and there's no easy way to predict them. Also, I found that gegl's new meson build doesn't source the $PREFIX/share/config.site automatically the way the old build did: gegl complained about not being able to find babl until I sourced $PREFIX/share/config.site in the shell before running the meson build. So I should probably just remove the suggestion of using config.site entirely, and tell people to export the variables in the shell before starting the build. ...Akkana ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On 8/22/19 5:43 PM, Akkana Peck wrote: I had a lot of trouble adjusting my build scripts for babl's meson build. So once I got it working, I ended up rewriting the GIMP wiki build instructions to reflect what worked for me. https://wiki.gimp.org/wiki/Hacking:Building Hi Akkana, Thanks! for updating the wiki. In case it helps, the paths for setting up the prefix vary from one distribution to the next, for example are very different for Debian Sid compared to Gentoo. In a fresh install of Debian Sid, after a lot of trial and error I finally managed to build babl (meson)/GEGL (meson)/GIMP-2.10 using these lines to set up the prefix: PREFIX=$HOME/code-install/gimp210/install export SRC_DIR=/home/elle/code-build/gimp210/build export PATH=$PREFIX/bin:$PATH export ACLOCAL_FLAGS="-I $PREFIX/share/aclocal" export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH=$PREFIX/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH export PKG_CONFIG_PATH=$PREFIX/lib/x86_64-linux-gnu:$PKG_CONFIG_PATH export PKG_CONFIG_PATH=$PREFIX/lib/x86_64-linux-gnu/pkgconfig:$PKG_CONFIG_PATH export PKG_CONFIG_PATH=$PREFIX/share/pkgconfig:$PKG_CONFIG_PATH export XDG_DATA_DIRS="$XDG_DATA_DIRS:$PREFIX/share:/usr/local/share/:/usr/share/" Notice on Debian Sid the "64-bit" folder where GEGL puts its ".so" files is "$PREFIX/lib/x86_64-linux-gnu". On Gentoo, the equivalent folder is "$PREFIX/lib64". These lines worked for setting up the prefix in Gentoo: PREFIX=$HOME/code-install/gimp210/install export SRC_DIR=/hdd/data1/code-build/gimp210/build export PATH=$PREFIX/bin:$PATH export ACLOCAL_FLAGS="-I $PREFIX/share/aclocal" export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH=$PREFIX/lib64:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH export PKG_CONFIG_PATH=$PREFIX/lib64/pkgconfig:$PKG_CONFIG_PATH export PKG_CONFIG_PATH=$PREFIX/install/share/pkgconfig:$PKG_CONFIG_PATH export GIO_EXTRA_MODULES=/usr/lib/gio/modules #above line probably isn't needed as I'm no longer build glib in the prefix export XDG_DATA_DIRS="$XDG_DATA_DIRS:$PREFIX/share" Best, Elle ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On Thu, Aug 22, 2019 at 03:43:25PM -0600, Akkana Peck wrote: > Marco Ciampa via gimp-developer-list writes: > > On Tue, Aug 13, 2019 at 02:26:50AM +0200, Marco Ciampa via > > gimp-developer-list wrote: > > > On Mon, Aug 12, 2019 at 08:38:45PM +0300, Alexandre Prokoudine via > > > gimp-developer-list wrote: > > > > Hello, > > > > > > > > You should be using the Meson build system now. > > > > > > Doh, I missed that! > > > It works now, thank you! > > > > I talked too quickly... now it is GIMP that does not compile (due to > > babl...): > > I had a lot of trouble adjusting my build scripts for babl's meson > build. So once I got it working, I ended up rewriting the GIMP wiki > build instructions to reflect what worked for me. > > https://wiki.gimp.org/wiki/Hacking:Building > > There are also some additions in the Hacking:Building/Linux page > (linked at the bottom) but it's mostly a discussion of why PREFIX > is important (I didn't write it, someone else did, but it seemed > worth keeping) and a discussion of how to run the GIMP you just built. > > Try it out -- and if it turns out that it's still incomplete, let > me know what needs to be changed (or update it yourself, if you > prefer). > > I know nothing of the Windows and Mac building pages: I don't > build on those platforms, but it would be great if someone who > does could keep them up to date. > > I should mention that my build page rewrites are from shortly after > babl switched to meson, but don't reflect any meson instructions for > gegl or gimp, so eventually Hacking:Building will need to be updated again. > > ...Akkana Retry: now (that apparently devs switched to meson also in GEGL, now it does not compile also gegl grrr) ninja [9/529] Generating Gegl-0.4.gir with a custom command. FAILED: gegl/Gegl-0.4.gir /usr/bin/g-ir-scanner --no-libtool --namespace=Gegl --nsversion=0.4 --warn-all --output gegl/Gegl-0.4.gir --c-include=gegl.h -I/home/marco/git/gitlab/gnome/gegl/gegl -I/home/marco/git/gitlab/gnome/gegl/build/gegl -I./. -I../. -I./gegl/. -I../gegl/. -I./gegl/buffer -I../gegl/buffer -I./gegl/graph -I../gegl/graph -I./gegl/module -I../gegl/module -I./gegl/opencl -I../gegl/opencl -I./gegl/operation -I../gegl/operation -I./gegl/process -I../gegl/process -I./gegl/property-types -I../gegl/property-types --filelist=/home/marco/git/gitlab/gnome/gegl/build/gegl/2cd4258@@gegl-0.4@sha/Gegl_0.4_gir_filelist --include=GLib-2.0 --include=GObject-2.0 --include=Babl-0.1 --symbol-prefix=gegl --identifier-prefix=Gegl --cflags-begin -DHAVE_CONFIG_H -Winit-self -Wmissing-declarations -Wmissing-prototypes -Wold-style-definition -Wpointer-arith -Wno-deprecated-declarations -mfpmath=sse -mmmx -msse -msse2 -msse4.1 -I./. -I../. -I./gegl/. -I../gegl/. -I./gegl/buffer -I../gegl/buffer -I./gegl/graph -I ../gegl/graph -I./gegl/module -I../gegl/module -I./gegl/opencl -I../gegl/opencl -I./gegl/operation -I../gegl/operation -I./gegl/process -I../gegl/process -I./gegl/property-types -I../gegl/property-types -I/usr/local/include/babl-0.1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0/ --cflags-end --library gegl-0.4 -L/home/marco/git/gitlab/gnome/gegl/build/gegl -L/usr/local/lib/x86_64-linux-gnu -L/usr/local/lib/x86_64-linux-gnu --extra-library=babl-0.1 --extra-library=glib-2.0 --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=m --extra-library=gmodule-2.0 Couldn't find include 'GLib-2.0.gir' (search path: '['/home/marco/.local/share/flatpak/exports/share/gir-1.0', '/var/lib/flatpak/exports/share/gir-1.0', '/usr/share/gnome-flashback-metacity/gir-1.0', '/home/marco/.local/share/flatpak/exports/share/gir-1.0', '/var/lib/flatpak/exports/share/gir-1.0', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', '/var/lib/snapd/desktop/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0']') [14/529] Generating module_common_gpl3.c with a meson_exe.py custom command. ninja: build stopped: subcommand failed. why "fixing" something that just works I wonder... Ok next gimp versions will be without the Italian translation updated because the translator is now no more able to compile GIMP from sources... Regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
Marco Ciampa via gimp-developer-list writes: > On Tue, Aug 13, 2019 at 02:26:50AM +0200, Marco Ciampa via > gimp-developer-list wrote: > > On Mon, Aug 12, 2019 at 08:38:45PM +0300, Alexandre Prokoudine via > > gimp-developer-list wrote: > > > Hello, > > > > > > You should be using the Meson build system now. > > > > Doh, I missed that! > > It works now, thank you! > > I talked too quickly... now it is GIMP that does not compile (due to babl...): I had a lot of trouble adjusting my build scripts for babl's meson build. So once I got it working, I ended up rewriting the GIMP wiki build instructions to reflect what worked for me. https://wiki.gimp.org/wiki/Hacking:Building There are also some additions in the Hacking:Building/Linux page (linked at the bottom) but it's mostly a discussion of why PREFIX is important (I didn't write it, someone else did, but it seemed worth keeping) and a discussion of how to run the GIMP you just built. Try it out -- and if it turns out that it's still incomplete, let me know what needs to be changed (or update it yourself, if you prefer). I know nothing of the Windows and Mac building pages: I don't build on those platforms, but it would be great if someone who does could keep them up to date. I should mention that my build page rewrites are from shortly after babl switched to meson, but don't reflect any meson instructions for gegl or gimp, so eventually Hacking:Building will need to be updated again. ...Akkana ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On Tue, Aug 13, 2019 at 02:26:50AM +0200, Marco Ciampa via gimp-developer-list wrote: > On Mon, Aug 12, 2019 at 08:38:45PM +0300, Alexandre Prokoudine via > gimp-developer-list wrote: > > Hello, > > > > You should be using the Meson build system now. > > Doh, I missed that! > It works now, thank you! I talked too quickly... now it is GIMP that does not compile (due to babl...): make[4]: ingresso nella directory "/home/marco/git/gitlab/gnome/gimp/plug-ins/script-fu" CCLD script-fu //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_n_components@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_model_with_space@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_fish@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_icc_make_space@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_palette_set_palette@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_process@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_get_model_flags@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_type@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_has_alpha@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_new_palette@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_with_space@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_exit@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_init@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_is_palette@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_exists@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_bytes_per_pixel@V0_1_0' ../../libgimp/.libs/libgimp-2.0.so: undefined reference to `babl_get_name@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_encoding@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_format_get_space@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_format_get_model@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_ticks@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_model@V0_1_0' ../../libgimpcolor/.libs/libgimpcolor-2.0.so: undefined reference to `babl_type@V0_1_0' ../../libgimpwidgets/.libs/libgimpwidgets-2.0.so: undefined reference to `babl_format@V0_1_0' //usr/local/lib/libgegl-0.4.so.0: undefined reference to `babl_process_rows@V0_1_0' collect2: error: ld returned 1 exit status Makefile:827: recipe for target 'script-fu' failed make[4]: *** [script-fu] Error 1 make[4]: uscita dalla directory "/home/marco/git/gitlab/gnome/gimp/plug-ins/script-fu" Makefile:882: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: uscita dalla directory "/home/marco/git/gitlab/gnome/gimp/plug-ins/script-fu" Makefile:701: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: uscita dalla directory "/home/marco/git/gitlab/gnome/gimp/plug-ins" Makefile:852: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: uscita dalla directory "/home/marco/git/gitlab/gnome/gimp" Makefile:753: recipe for target 'all' failed make: *** [all] Error 2 marco@marco-N24-25JU:~/git/gitlab/gnome/gimp$ -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On Mon, Aug 12, 2019 at 08:38:45PM +0300, Alexandre Prokoudine via gimp-developer-list wrote: > Hello, > > You should be using the Meson build system now. Doh, I missed that! It works now, thank you! -- Marco Ciampa I know a joke about UDP, but you might not get it. GNU/Linux User #78271 FSFE fellow #364 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On 08/12/2019 03:38 PM, Ken Moffat via gimp-developer-list wrote:
On Mon, Aug 12, 2019 at 02:33:42PM -0400, Elle Stone wrote:
On 08/12/2019 01:38 PM, Alexandre Prokoudine via gimp-developer-list wrote:
Hello,
You should be using the Meson build system now.
In case it helps anyone, here are the lines I've been using with meson to
build babl:
cd $SRC_DIR/babl
git status
rm -r build
git checkout build
cd build
CFLAGS="-march=native -O3 -ffast-math -ftree-vectorize -pipe"
CXXFLAGS="${CFLAGS}" meson --prefix=$PREFIX ..
ninja install
Here are some questions about meson:
1. Any suggestions to modify my lines?
Hi Ken, and thanks much! for the very helpful information.
Adding '-Dbuildtype=release' to a meson package will turn off debug
assertions, if any (e.g. mesa) and (usually) use -O3 (ISTR that at
least pango uses -O2 for a release build).
2. Do the CFLAGS lines actually do anything when using meson?
Do a verbose build using 'ninja -v' to see what flags and defines
are used. I usually do separate steps for 'ninja' and 'ninja
install', but whatever works for you. Verbose builds will produce a
_lot_ more output, teeing it to a log so you can read it afterwards
helps (but I'm sure you know that).
3. How do I tell meson to use "something" equivalent to the following "make"
lines?
./autogen.sh --prefix=$PREFIX --enable-avx2=false --enable-mmx=no
--enable-sse=no --enable-sse2=no --enable-sse3=no --enable-sse4_1=no
--enable-f16c=no --enable-altivec=no --disable-docs
I very much doubt you are on ppc/powerpc, so altivec cannot be used.
In general, meson uses defines (-Dsomething=value, rather like
cmake) for things which are not covered by --prefix= --sysconfdir=.
To see the options for a particular package, look in the
meson_options.txt file. That might have an option to disable docs,
or it might even be automatic if the deps are missing.
With -march=native I would tend to let gcc sort out sse and similar
options. I'm assuming you are on x86_64.
Regarding my "make" options for babl, I disabled anything to do with CPU
code because at one point the only thing that code in babl did was make
the TRC transforms faster, and I was building babl for my "CCE" version
of GIMP, which has no TRC transforms. So I just disabled any and all
options related to the CPU (and for good measure ripped the relevant
code out of the CCE version of babl).
I guess I should check to see what the babl CPU code does today. But if
the code is hard-coded to the sRGB TRC, it still won't work with the
somewhat modified version of GIMP I build for actual editing (as opposed
to the versions I build for keeping up with and testing the default GIMP
code).
The gcc manual gives some options (for X86) about what you can put
in CFLAGS|CXXFLAGS, see the -mfpath= section.
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
(That is for 9.2, probably the only big change from 9.1 is adding
znver2). And more generally, the -f options are linked from
.../gcc/Option-Index.html
Docs for the latest point release of each gcc version are at
https://gcc.gnu.org/onlinedocs/ if you are using an earlier major
version.
OTOH, if you have the (lots of) time needed to try playing with
these options, and scripts which you can run using 'time' (several
runs for each different build) then perhaps tuning out some of these
things might be worthwhile. I spent a lot of time in the past couple
of months doing whole-system builds with different flags (mostly for
slight hardening) and ended up concluding there was just too much
variation between runs to get much meaningful data on timing. And I
didn't have any runtime scripts for gimp-related actions.
I wasn't actually trying to optimize this or that using timings or
anything sophisticated, just relying on some flags that were posted to
the developer's list a long time ago in response to the general question
"how to make GIMP go faster". That was back maybe around 2015 or so -
there was other advice also, I wonder how much is still pertinent after
all this time.
I have no idea whether these flags actually did or still do make GIMP go
faster or not. But given the source of the recommendations - someone who
seems to know what they are doing - I was and still am inclined to keep
using the flags. Though given the many versions of gcc that have come
and gone in the meantime, maybe the flags no longer make any sense.
Updated general advice on cflags is very welcome! If it matters, my CPU
is an Intel Core i7-4790K.
ĸen
Ken, again, thank you so much! That meson stuff was/is very puzzling.
Next time I build babl I'll try to put your pointers to good use.
Best,
Elle
--
https://ninedegreesbelow.com
Color management and free/libre photography
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:
Re: [Gimp-developer] help compiling babl
On Mon, Aug 12, 2019 at 02:33:42PM -0400, Elle Stone wrote:
> On 08/12/2019 01:38 PM, Alexandre Prokoudine via gimp-developer-list wrote:
> > Hello,
> >
> > You should be using the Meson build system now.
>
> In case it helps anyone, here are the lines I've been using with meson to
> build babl:
>
>
> cd $SRC_DIR/babl
> git status
> rm -r build
> git checkout build
> cd build
> CFLAGS="-march=native -O3 -ffast-math -ftree-vectorize -pipe"
> CXXFLAGS="${CFLAGS}" meson --prefix=$PREFIX ..
> ninja install
>
> Here are some questions about meson:
>
> 1. Any suggestions to modify my lines?
>
Adding '-Dbuildtype=release' to a meson package will turn off debug
assertions, if any (e.g. mesa) and (usually) use -O3 (ISTR that at
least pango uses -O2 for a release build).
> 2. Do the CFLAGS lines actually do anything when using meson?
>
Do a verbose build using 'ninja -v' to see what flags and defines
are used. I usually do separate steps for 'ninja' and 'ninja
install', but whatever works for you. Verbose builds will produce a
_lot_ more output, teeing it to a log so you can read it afterwards
helps (but I'm sure you know that).
> 3. How do I tell meson to use "something" equivalent to the following "make"
> lines?
>
> ./autogen.sh --prefix=$PREFIX --enable-avx2=false --enable-mmx=no
> --enable-sse=no --enable-sse2=no --enable-sse3=no --enable-sse4_1=no
> --enable-f16c=no --enable-altivec=no --disable-docs
>
I very much doubt you are on ppc/powerpc, so altivec cannot be used.
In general, meson uses defines (-Dsomething=value, rather like
cmake) for things which are not covered by --prefix= --sysconfdir=.
To see the options for a particular package, look in the
meson_options.txt file. That might have an option to disable docs,
or it might even be automatic if the deps are missing.
With -march=native I would tend to let gcc sort out sse and similar
options. I'm assuming you are on x86_64.
The gcc manual gives some options (for X86) about what you can put
in CFLAGS|CXXFLAGS, see the -mfpath= section.
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
(That is for 9.2, probably the only big change from 9.1 is adding
znver2). And more generally, the -f options are linked from
.../gcc/Option-Index.html
Docs for the latest point release of each gcc version are at
https://gcc.gnu.org/onlinedocs/ if you are using an earlier major
version.
OTOH, if you have the (lots of) time needed to try playing with
these options, and scripts which you can run using 'time' (several
runs for each different build) then perhaps tuning out some of these
things might be worthwhile. I spent a lot of time in the past couple
of months doing whole-system builds with different flags (mostly for
slight hardening) and ended up concluding there was just too much
variation between runs to get much meaningful data on timing. And I
didn't have any runtime scripts for gimp-related actions.
ĸen
--
Adopted by dwarfs, brought up by dwarfs. To dwarfs I'm a dwarf, sir.
I can do the rite of k'zakra, I know the secrets of h'ragna, I can
ha'lk my g'rakha correctly ... I am a dwarf
Captain Carrot Ironfoundersson (in The Fifth Elephant)
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
On 08/12/2019 01:38 PM, Alexandre Prokoudine via gimp-developer-list wrote:
Hello,
You should be using the Meson build system now.
In case it helps anyone, here are the lines I've been using with meson
to build babl:
cd $SRC_DIR/babl
git status
rm -r build
git checkout build
cd build
CFLAGS="-march=native -O3 -ffast-math -ftree-vectorize -pipe"
CXXFLAGS="${CFLAGS}" meson --prefix=$PREFIX ..
ninja install
Here are some questions about meson:
1. Any suggestions to modify my lines?
2. Do the CFLAGS lines actually do anything when using meson?
3. How do I tell meson to use "something" equivalent to the following
"make" lines?
./autogen.sh --prefix=$PREFIX --enable-avx2=false --enable-mmx=no
--enable-sse=no --enable-sse2=no --enable-sse3=no --enable-sse4_1=no
--enable-f16c=no --enable-altivec=no --disable-docs
Alex
On Mon, Aug 12, 2019 at 8:36 PM Marco Ciampa via gimp-developer-list
wrote:
Hi devs, I have a prolem compiling babl...
from master git I do:
./configure
make
make: *** No rule to make target 'Makefile.am', needed by 'Makefile.in'. Stop.
but with a:
git checkout BABL_0_1_68
it works...
what's going on here?
TIA
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
GNU/Linux User #78271
FSFE fellow #364
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
--
https://ninedegreesbelow.com
Color management and free/libre photography
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] help compiling babl
Hello, You should be using the Meson build system now. Alex On Mon, Aug 12, 2019 at 8:36 PM Marco Ciampa via gimp-developer-list wrote: > > Hi devs, I have a prolem compiling babl... > > from master git I do: > > ./configure > make > make: *** No rule to make target 'Makefile.am', needed by 'Makefile.in'. > Stop. > > but with a: > > git checkout BABL_0_1_68 > > it works... > > what's going on here? > > TIA > > -- > > > Marco Ciampa > > I know a joke about UDP, but you might not get it. > > > > GNU/Linux User #78271 > FSFE fellow #364 > > > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
