From: Andreas Radke <andyrtr@mailbox.org>
To: Denis Kenzior <denkenz@gmail.com>
Cc: ell@lists.linux.dev
Subject: Re: missing header files
Date: Mon, 26 Aug 2024 18:39:26 +0200 [thread overview]
Message-ID: <20240826183926.6cd4fd33@workstation64.local> (raw)
In-Reply-To: <14a637ae-0f31-4429-963a-5f5012841ee0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Am Mon, 26 Aug 2024 10:38:37 -0500
schrieb Denis Kenzior <denkenz@gmail.com>:
> Hi Andreas,
>
> On 8/26/24 7:38 AM, Andreas Radke wrote:
> [...]
>
> ell/useful.h and ell/asn1-private.h are special. They're copied from
> the ell tree when iwd is built. Even if using shared ell, you need
> to setup ell as described in the README
>
> [...]
>
> These files are included in the distribution package.
> [denkenz@archdev iwd]$ tar -Jtvf iwd-2.19.tar.xz | grep useful
> -rw-r--r-- denkenz/denkenz 1979 2024-08-16 10:31
> iwd-2.19/ell/useful.h [denkenz@archdev iwd]$ tar -Jtvf
> iwd-2.19.tar.xz | grep asn1 -rw-r--r-- denkenz/denkenz 4406
> 2024-08-16 10:31 iwd-2.19/ell/asn1-private.h
>
> [...]
>
> None of these files are to be installed by ell, they're not part of
> the public API.
>
> Regards,
> -Denis
>
Compiling is broken here when using --enable-external-ell with iwd git
master no matter if I put ell source along iwd as described in README
but succeeds with --disable-external-ell.
The README ist somewhat misleading here. When building from git and
placing ell into toplevel dir it's failing. A cp ell/ell into iwd/ is
required when building from git.
-Andy
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-08-26 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:38 missing header files Andreas Radke
2024-08-26 15:38 ` Denis Kenzior
2024-08-26 16:39 ` Andreas Radke [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 16:38 Missing " Harald von Fellenberg - Sun Switzerland Zurich - Technology Strategy Office
2001-01-04 17:08 ` Stephen Smalley
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=20240826183926.6cd4fd33@workstation64.local \
--to=andyrtr@mailbox.org \
--cc=denkenz@gmail.com \
--cc=ell@lists.linux.dev \
/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.