On 01/10/2017 10:00 PM, Ross Vandegrift wrote:
> On Tue, Jan 10, 2017 at 09:40:54PM +, Peter Flynn wrote:
[...]
>> delete, lather, rinse, repeat...
>
> Here's a trick to make this easier: sudo aptitude remove libeina1
> aptitude will suggest removing all of the packages which depend on eina.
>
On Tue, Jan 10, 2017 at 09:40:54PM +, Peter Flynn wrote:
> They appear to be part of e17, and perhaps e19, which apparently (in
> their Ubuntu incarnations) install themselves from a large number of
> discrete packages, and lack a monolithic driver. Working backwards, I
> found an actual *packa
On 01/09/2017 11:44 PM, Carsten Haitzler (The Rasterman) wrote:
> On Mon, 9 Jan 2017 23:14:30 + Peter Flynn said:
>> [...] How is EFL intended to build new versions and install them in
>> /usr/local/lib if /usr/lib/i386-linux-gnu/ is stuffed full of the
>> existing system-installed ones?
>
>
In the year 2017, of the month of January, on the 9th day, Peter Flynn wrote:
> There are copies of libecore.so and libecore_file.so (and other
> libecore*) in /usr/lib/i386-linux-gnu/, all version 1.8.6 whereas EFL is
> trying to create 1.18.99 There's also something called libecore1 which
> see
On Mon, 9 Jan 2017 23:14:30 + Peter Flynn said:
> On 01/09/2017 10:36 PM, Dave wrote:
> > OK, I did a little more looking, and the functions referenced are to be
> > found in the libecore.so library. So, seems like your libecore_file.so
> > can't find this library.
>
> Thanks very much for
On 01/09/2017 10:36 PM, Dave wrote:
> OK, I did a little more looking, and the functions referenced are to be
> found in the libecore.so library. So, seems like your libecore_file.so
> can't find this library.
Thanks very much for digging into that.
There are copies of libecore.so and libecore_f
OK, I did a little more looking, and the functions referenced are to be
found in the libecore.so library. So, seems like your libecore_file.so
can't find this library.
So, next step would be to check your /etc/ld.so.conf file (and possibly
/etc/ld.so.conf.d/* files) to see if "/usr/local/lib" i
On 01/09/2017 12:44 AM, Dave wrote:
> In the year 2017, of the month of January, on the 8th day, Peter Flynn wrote:
>>> CCLD src/bin/enlightenment_imc
>>> /usr/local/lib/libecore_file.so: undefined reference to `_efl_add_end'
>>> /usr/local/lib/libecore_file.so: undefined reference to
>>> `
On 01/09/2017 12:44 AM, Dave wrote:
> In the year 2017, of the month of January, on the 8th day, Peter Flynn wrote:
>> Hmm. It's worked 3× for me so far just fine, but now suddenly I get this
>>> CCLD src/bin/enlightenment
>>> CC src/bin/src_bin_enlightenment_imc-e_config_data.o
>>
In the year 2017, of the month of January, on the 8th day, Peter Flynn wrote:
> Hmm. It's worked 3× for me so far just fine, but now suddenly I get this
> > CCLD src/bin/enlightenment
> > CC src/bin/src_bin_enlightenment_imc-e_config_data.o
> > CC src/bin/src_bin_enlightenmen
On 01/05/2017 10:36 PM, Peter Flynn wrote:
> On 11/02/2016 10:01 PM, Peter Flynn wrote:
>> I *know* you're really good...I was letting prior experience cloud my
>> vision. I'm away this weekend but I'll give it a try later.
>
> Hah. It worked. Interesting.
>
> The page at https://www.enlightenmen
On 01/07/2017 03:42 AM, Carsten Haitzler (The Rasterman) wrote:
> On Fri, 6 Jan 2017 22:17:55 + Peter Flynn said:
>> I wouldn't consider my knowledge enough to warrant altering even a wiki.
> well i sure am not updating it ...
I wasn't suggesting that, just excusing my own ignorance.
> well
On Fri, 6 Jan 2017 22:17:55 + Peter Flynn said:
> On 01/06/2017 01:03 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Thu, 5 Jan 2017 22:36:52 + Peter Flynn said:
> >> 2. libxp-dev is dead, and has been replaced by x11proto-print-dev,
> >> so editing that into the list of packages wor
On 01/06/2017 01:03 AM, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 5 Jan 2017 22:36:52 + Peter Flynn said:
>> 2. libxp-dev is dead, and has been replaced by x11proto-print-dev,
>> so editing that into the list of packages works fine.
>
> package names and such change over time for dist
On Thu, 5 Jan 2017 22:36:52 + Peter Flynn said:
> On 11/02/2016 10:01 PM, Peter Flynn wrote:
> > I *know* you're really good...I was letting prior experience cloud my
> > vision. I'm away this weekend but I'll give it a try later.
>
> Hah. It worked. Interesting.
>
> The page at https://www
On 11/02/2016 10:01 PM, Peter Flynn wrote:
> I *know* you're really good...I was letting prior experience cloud my
> vision. I'm away this weekend but I'll give it a try later.
Hah. It worked. Interesting.
The page at https://www.enlightenment.org/distros/debian-start is they key.
1. Apparently
On Wed, 4 Jan 2017 21:04:03 +0100 Mark Dickie said:
> Hi,
>
> On 4 January 2017 at 20:55, Peter Flynn wrote:
>
> > On 01/04/2017 02:00 PM, Mark Dickie wrote:
> > > Hi Peter
> > >
> > > At the bottom are what I use on debian testing should cover all
> > > available options including depende
Hi,
On 4 January 2017 at 20:55, Peter Flynn wrote:
> On 01/04/2017 02:00 PM, Mark Dickie wrote:
> > Hi Peter
> >
> > At the bottom are what I use on debian testing should cover all
> > available options including dependencies for e with wayland:
> >
> > However! some of the package names in
On 01/04/2017 02:00 PM, Mark Dickie wrote:
> Hi Peter
>
> At the bottom are what I use on debian testing should cover all
> available options including dependencies for e with wayland:
>
> However! some of the package names in Ubuntu are slightly different from
> those in Debian
I thought it
Hi Peter
At the bottom are what I use on debian testing should cover all
available options including dependencies for e with wayland:
However! some of the package names in Ubuntu are slightly different from
those in Debian
so for example
apt-cache search libpng dev
in debian shows:
libpn
On 2016-11-29 07:13, Pierre Couderc wrote:
> See too https://www.enlightenment.org/distros/debian-start that was
> tested for debian in Oct 2016.
Thank you for the link.
> On 11/28/2016 04:46 PM, pe...@silmaril.ie wrote:
>> I just installed yakkity so I'm going to try building on that, as the
>>
See too https://www.enlightenment.org/distros/debian-start that was
tested for debian in Oct 2016.
On 11/28/2016 04:46 PM, pe...@silmaril.ie wrote:
> On 2016-11-02 13:37, Mark Dickie wrote:
>> Hi
>> there is also a ppa for e21 at
>> https://launchpad.net/~niko2040/+archive/ubuntu/e19
>>
>> I use
On 2016-11-02 13:37, Mark Dickie wrote:
> Hi
> there is also a ppa for e21 at
> https://launchpad.net/~niko2040/+archive/ubuntu/e19
>
> I use the Debian packages with no problems but there seem to be ones
> for
> xenial too.
I just installed yakkity so I'm going to try building on that, as the
On 11/02/2016 01:27 AM, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 1 Nov 2016 21:00:58 + Peter Flynn said:
>> [...]
>> I've never had any luck building systems that big. [...] Deeply frustrating.
>
> that's not us. i just installed efl+_e on raspbian (i did have to switch to
> testing
Hi
there is also a ppa for e21 at
https://launchpad.net/~niko2040/+archive/ubuntu/e19
I use the Debian packages with no problems but there seem to be ones for
xenial too.
Cheers
On 2 Nov 2016 03:50, "Carsten Haitzler" wrote:
On Tue, 1 Nov 2016 21:00:58 + Peter Flynn said:
> On 11/01/2016
On Tue, 1 Nov 2016 21:00:58 + Peter Flynn said:
> On 11/01/2016 12:10 AM, Simon Lees wrote:
> >
> >
> > On 11/01/2016 08:32 AM, Peter Flynn wrote:
> >> I have been (and still am) running e18 without problems on Xubuntu 15.10
> >> but I just upgraded a system to 16.04 and found that the only
On 11/01/2016 12:10 AM, Simon Lees wrote:
>
>
> On 11/01/2016 08:32 AM, Peter Flynn wrote:
>> I have been (and still am) running e18 without problems on Xubuntu 15.10
>> but I just upgraded a system to 16.04 and found that the only packaged
>> version in the repos was e17!
>>
>> Does anyone know
On 11/01/2016 08:32 AM, Peter Flynn wrote:
> I have been (and still am) running e18 without problems on Xubuntu 15.10
> but I just upgraded a system to 16.04 and found that the only packaged
> version in the repos was e17!
>
> Does anyone know why this has gone backwards?
>
> I know I should be
I have been (and still am) running e18 without problems on Xubuntu 15.10
but I just upgraded a system to 16.04 and found that the only packaged
version in the repos was e17!
Does anyone know why this has gone backwards?
I know I should be using e20, but the PPA doesn't support 16.04 yet.
///Pete
29 matches
Mail list logo
