LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   compiling parcellite on current (https://www.linuxquestions.org/questions/slackware-14/compiling-parcellite-on-current-4175425205/)

Habitual 09-01-2012 08:33 PM

compiling parcellite on current
 
I installed current from a clean-system on 13 and I went to install using sbopkg the parcellite utility and I get this output:
Code:

make[2]: Leaving directory `/tmp/SBo/parcellite-1.0.2rc2/po'
Making all in data
make[2]: Entering directory `/tmp/SBo/parcellite-1.0.2rc2/data'
LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po parcellite-startup.desktop.in parcellite-startup.desktop
Generating and caching the translation database
Merging translations into parcellite-startup.desktop.
LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po parcellite.desktop.in parcellite.desktop
Found cached translation database
Merging translations into parcellite.desktop.
make[2]: Leaving directory `/tmp/SBo/parcellite-1.0.2rc2/data'
Making all in src
make[2]: Entering directory `/tmp/SBo/parcellite-1.0.2rc2/src'
gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14    -O2 -march=i486 -mtune=i686 -I.. -DPARCELLITELOCALEDIR=\""/usr/share/locale"\" -O2 -march=i486 -mtune=i686 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
In file included from keybinder.h:23:0,
                from main.c:32:
/usr/include/glib-2.0/glib/gtypes.h:28:2: error: #error "Only <glib.h> can be included directly."
make[2]: *** [main.o] Error 1
make[2]: Leaving directory `/tmp/SBo/parcellite-1.0.2rc2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/parcellite-1.0.2rc2'
make: *** [all] Error 2

I ran
Code:

cd && /tmp/SBo/parcellite-1.0.2rc2
./configure

manually and configure ran. make fails.

Being vigilant I searched here and found several hits...
ponce suggests glibmm bump to 2.32.1 here... which I installed.

and here he said "starting with glib>=2.31, it is enforced that only the glib toplevel headers should be included".

Thank you for your time.

Edit: "make check" also fails.

shadowsnipes 09-01-2012 09:51 PM

In short, try 1.02rc5 or switch to clipit.

Most of those "only glib.h can be included directly" errors are fixed by doing just that- edit the source to include glib.h instead of glib/*.h. However, with this particular version, I seem to remember that there were other issues with building on Slackware 14 as well.

Up through Slackware 13.37 I've been the maintainer for the SlackBuild for parcellite. The project is dead now and has been superseded by a fork called clipit, which is already on SBo and works great on Slackware 14.0 RCx. I recommend that you check it out. Here are some of my brief comparison notes between clipit 1.4.2 and parcellite 1.0.2rc2:

--- Clipit 1.4.2 ---
+ offline mode (useful for when you expect you'll be highlighting/copying sensitive info)
+ Static history entries
+ better history management
- uses *slightly* more resources than parcellite 1.0.2rc2


--- parcellite 1.0.2rc2 ---
+ easier/quicker to clear history
+ easier/quicker to remove items

History item removal isn't as crucial if you correctly use offline mode. I do still like the stock GTK icons better since they match desktop themes, so I'll probably write a patch to clipit to make that an option (as I did for the parcellite SlackBuild).

I don't intend on maintaining the parcellite SlackBuild anymore, so if someone wants to pick it up for SW 14+ feel free to do so. I think 1.02rc5 will build on SW 14 RCx. But again, the sources are dead and the fork, clipit, has superseded it. Hope this helps.

Habitual 09-02-2012 07:18 AM

Quote:

Originally Posted by shadowsnipes (Post 4770353)
In short, try 1.02rc5 or switch to clipit...

.

That's why I love Linux, it allows us to be flexible with alternatives.

I used parcellite in the past because it just worked.

I could have saved some time by merely running
Code:

sbopkg -s clip*
"It was forked from Parcellite,".

Thank you for your time.

SergMarkov 09-02-2012 09:33 AM

Quote:

Originally Posted by shadowsnipes (Post 4770353)
But again, the sources are dead and the fork, clipit, has superseded it.

Unfortunately development clipit also terminated
Clipit author wrote in his blog "I switched to KDE for the time being (I don't think it's definitive, but I really couldn't get my work done properly with GNOME 3). For this reason, the development of ClipIt has been halted for now. I really hope to be able to get back to it, since I really use it every day, and I can't imagine doing my work without the aid of a clipboard manager, and I also still have a lot of ideas of improving the app. "

shadowsnipes 09-02-2012 10:47 AM

Quote:

Originally Posted by SergMarkov (Post 4770617)
Unfortunately development clipit also terminated
Clipit author wrote in his blog "I switched to KDE for the time being (I don't think it's definitive, but I really couldn't get my work done properly with GNOME 3). For this reason, the development of ClipIt has been halted for now. I really hope to be able to get back to it, since I really use it every day, and I can't imagine doing my work without the aid of a clipboard manager, and I also still have a lot of ideas of improving the app. "

He also wrote in the comments "...in any case, I will somehow continue the development of ClipIt, even if it’ll just be a Xorg app."

I wouldn't worry about clipit being obsolete any time too soon. However, if at the next Slackware release (after 14.0) it is obsolete (broken), I'll either fix it or find the next project that takes its place. I'm less concerned with new features as much as simply maintaining the current good functionality.


All times are GMT -5. The time now is 08:31 AM.