On Mon, 2 Oct 2023 19:13:21 +0200 daniel antoine said:
> When I arrive to launch an enlightenment wayland session I have notice
> errors in the .e_log.log file. I Have a lot of loop time errors like:
> Eccore: Trying to set loop time (58,36538400) 0,3410s too far in the
> future Eccore: Tryin
When I arrive to launch an enlightenment wayland session I have notice
errors in the .e_log.log file. I Have a lot of loop time errors like:
Eccore: Trying to set loop time (58,36538400) 0,3410s too far in the future
Eccore: Trying to set loop time (58,38621500) 0,3231s too far in the futur
On 19/02/2022 00:33, Ross Vandegrift wrote:
[...]
apt is trying to first fix the partially installed packages. You might
have better luck with dpkg. Here's some ideas.
Thank you so much for this.
First try to use dpkg to do the removal:
dpkg --remove terminology terminology-data
That w
On Fri, Feb 18, 2022 at 10:46:33PM +, Peter Flynn wrote:
> On 18/02/2022 17:01, Ross Vandegrift wrote:
> > On Fri, Feb 18, 2022 at 03:58:49PM +, Peter Flynn wrote:
> > > > Unpacking terminology-data (1.12.1-0bionic0) ...
> > > > dpkg: error processing archive [...]
> >
> > tl, dr: Probably
On 18/02/2022 17:01, Ross Vandegrift wrote:
On Fri, Feb 18, 2022 at 03:58:49PM +, Peter Flynn wrote:
Unpacking terminology-data (1.12.1-0bionic0) ...
dpkg: error processing archive [...]
>
tl, dr: Probably the easiest fix is to manually remove all of the
erroring packages and then reinstal
On Fri, Feb 18, 2022 at 03:58:49PM +, Peter Flynn wrote:
> > Unpacking terminology-data (1.12.1-0bionic0) ...
> > dpkg: error processing archive
> > /tmp/apt-dpkg-install-N4vzQO/098-terminology-data_1.12.1-0bionic0_all.deb
> > (--unpack):
> > trying to overwrite '/usr/share/locale/ca/LC_MESS
I just dug out an old laptop running Linux Mint 19.2 and unused for six
months or so, and did
sudo apt update
sudo apt upgrade
I got the following errors:
Errors were encountered while processing:
/tmp/apt-dpkg-install-N4vzQO/013-enlightenment-data_0.25.1-0bionic3_all.deb
/tmp/apt-dpkg-inst
I thought someone more experienced would chip in, so I didn't reply.
Anyway, if you're getting undefined references in the linking phase, it's
showing that the linker doesn't know where your libraries are located, or the
libraries it finds don't have the required function. From the looks of it,
talking to myself:> I see the 1.7.7 debs are in debian unstable
now and I will abandon this, possibly trying to learn more about debian
packaging on a more modest task.
John Holland writes:
> I'm trying to build debs of the 1.7.8 versions of things, and I've
> worked my way up to edj
I'm trying to build debs of the 1.7.8 versions of things, and I've
worked my way up to edje. When I build it I am getting "undefined
reference" errors about a lot of items. the first few are
../../src/lib/.libs/libedje.so: undefined reference to
`ecore_fb_input_device_window_set'
../../src/lib/.l
On Mon, Apr 13, 2009 at 3:25 PM, Geoffrey wrote:
> mik firestone wrote:
> > You need to back-rev your libfribidi.
> >
> > I had to go from v0.19.1 back to v 0.10.9. At least on gentoo, that was
> > really only one version level.
>
> That worked for me as well, thanks. How did you know this would
mik firestone wrote:
> You need to back-rev your libfribidi.
>
> I had to go from v0.19.1 back to v 0.10.9. At least on gentoo, that was
> really only one version level.
That worked for me as well, thanks. How did you know this would resolve
your problem?
>
> Mik
>
> On Mon, Apr 13, 2009
You need to back-rev your libfribidi.
I had to go from v0.19.1 back to v 0.10.9. At least on gentoo, that was
really only one version level.
Mik
On Mon, Apr 13, 2009 at 11:57 AM, Geoffrey wrote:
> I'm receiving the following error when building ecore with easy_e17.sh:
>
> /opt/e17/lib/libevas.
I'm receiving the following error when building ecore with easy_e17.sh:
/opt/e17/lib/libevas.so.0: undefined reference to `fribidi_is_char_rtl'
Am I missing a header or library? I can't track this issue down in the
code or google.
I've got libfribidi-devel installed, so I'm not sure what else
yes, now it compile!
thanks to all guys :)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surv
I had the same problem... You may want to build ecore with the "dbus" USE
flag.
On 2/22/07, Agostino La Sorba <[EMAIL PROTECTED]> wrote:
>
> I am experiencing the following result when trying to compile e on my
> gentoo (in a simply PIV):
>
> ---
Sorry, my previous email was in error
I had disabled directfb, but had enabled dbus.
I also had to recompile dbus to include qt3 support, before I had
compiled e_core.
Also add to package.use the following:
sys-apps/dbus qt3
Sorry about the misleading info.
Lucas
On Thu, 2007-02-22 at 11:
Hi,
you can disable DBUS compile in e_core (I think it may not yet be
complete ??)
Had the same issue a few weeks back, als o had issues directly
afterwards with directfb.
Here is my /etc/portage/package.use settings
x11-plugins/e_modules -calendar
x11-libs/evas -directfb
x11-libs/ecore -direct
I am experiencing the following result when trying to compile e on my
gentoo (in a simply PIV):
In file included from e_user.c:4:
e.h:66:24: error: Ecore_DBus.h: No such file or directory
In file included from e_main.c:4:
e.h:66:24: erro
upgrade ecore
On 3/24/06, Brian Howe <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm running intel Linux redHat. Did a CVS CO today and I'm getting the
> following when I try to compile e:
>
> e_manager.c: In function `e_manager_new':
> e_manager.c:145: `ECORE_X_EVENT_SCREENSAVER_NOTIFY' undeclared (
Hi all,
I'm running intel Linux redHat. Did a CVS CO today and I'm getting the
following when I try to compile e:
e_manager.c: In function `e_manager_new':
e_manager.c:145: `ECORE_X_EVENT_SCREENSAVER_NOTIFY' undeclared (first
use in this function)
e_manager.c:145: (Each undeclared identifier is r
Hi again :)
While compiling e_modules i get a huge amount of errors:
In file included from /usr/include/enlightenment/e.h:39,
from e_mod_main.c:1:
/usr/include/enlightenment/config.h:47:1: warning: this is the location of the previous definition
In file included from e_mod_main.h
Just updated from CVS (sourceforge) and got this error:
checking for valgrind >= 2.4.0... yes
checking VALGRIND_CFLAGS... -mpreferred-stack-boundary=2
-I/usr/local/include/valgrind -I/usr/local/include/valgrind/x86
-I/usr/local/include/valgrind/linux
-I/usr/local/include/valgrind/x86-linux
checki
erss: error while loading shared libraries: libedje.so.0: cannot open
shared object file: No such file or directory
anybody know how to fix this. I know it's a common occurrence and I've
been told how to fix it, but a while back. I would appreciate some
help.
Justin
Hello,
I downloaded both the binary rpm and the source tarball from eterm.org
and ran into the following problems:
1. rpm install
. the install executes w/o errors
. But I get the following at startup:
Eterm: error while loading shared libraries:
/usr/lib/libEterm-0.9.2.so: undefin
25 matches
Mail list logo
