From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: [PATCH] document getting of ell, point people at useful docs
Date: Fri, 01 Feb 2019 23:25:54 +0100 [thread overview]
Message-ID: <20190201222554.GA22438@amd> (raw)
In-Reply-To: <4ED57398-61D8-4F54-865A-9CCD09E9ED55@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Hi!
> > diff --git a/README b/README
> > index 45bb2e9..04a50a5 100644
> > --- a/README
> > +++ b/README
> > @@ -16,11 +16,14 @@ To configure run:
> > ./configure --prefix=/usr --mandir=/usr/share/man \
> > --sysconfdir=/etc --localstatedir=/var
> >
> > -Configure automatically searches for all required components and packages.
> > +Configure automatically searches for all required components and
> > +packages, except ell, mentioned below.
> >
>
> Nope. Since ELL is actually optional. It is clearly described just a few lines below.
>
Is it optional? This is definitely unclear. Are we looking at same README?
commit 55e5a766f2833d6aaaf98d0f8cc250585717bc07
Author: Nandini Rebello <nandini.rebello@intel.com>
Date: Wed Jan 16 12:15:31 2019 +0530
README says:
Embedded Linux library
======================
In order to compile the daemon and utilities the development version
of Embedded Linux library is required to be present. The development
repositories can be found here:
which sounds like "required" to me. Then there is:
When using --enable-external-ell build option, it is not required that
the Embedded Linux library source code is available in the top level
directory.
But I read it as "can be present somewhere else".
Plus, build actually fails, with pretty cryptic error message:
./bootstrap-configure
./configure
pavel(a)duo:~/g/ofono$ make
make --no-print-directory all-am
make[1]: *** No rule to make target 'ell/util.c', needed by
'ell/util.lo'. Stop.
Makefile:2066: recipe for target 'all' failed
make: *** [all] Error 2
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-02-01 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 9:44 ofono fails to compile on gcc-6.3 Pavel Machek
2018-09-04 11:01 ` Giacinto Cifelli
2018-12-29 9:53 ` Trouble compiling ... " Pavel Machek
2018-12-29 20:20 ` Denis Kenzior
2018-12-29 20:30 ` Pavel Machek
2018-12-29 21:08 ` Denis Kenzior
2019-01-22 17:07 ` Marcel Holtmann
2018-12-29 22:24 ` [PATCH] fix compilation " Pavel Machek
2018-12-29 22:47 ` [PATCH] document getting of ell, point people at useful docs Pavel Machek
2019-01-14 11:17 ` Pavel Machek
2019-01-22 16:50 ` Marcel Holtmann
2019-02-01 22:25 ` Pavel Machek [this message]
2019-02-02 12:18 ` Marcel Holtmann
2019-01-22 17:03 ` [PATCH] fix compilation on gcc-6.3 Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190201222554.GA22438@amd \
--to=pavel@ucw.cz \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.