From: KeithG <ys3al35l@gmail.com>
To: connman@lists.linux.dev
Subject: Re: cannot build release 1.42 on RPiOS
Date: Fri, 22 Dec 2023 14:13:15 -0600 [thread overview]
Message-ID: <CAG17S_MLsYxcvFpf3v4t578a6=0MuTUiNYj8SinzA5-DQr6jWw@mail.gmail.com> (raw)
In-Reply-To: <CAG17S_PAwPF6BaL6SqLcZi7HxgGjho2oUOT1vHqbiqyA8LfJtg@mail.gmail.com>
On Fri, Dec 22, 2023 at 7:49 AM KeithG <ys3al35l@gmail.com> wrote:
>
> In the past,I have successfully built connman versions 1.38-41 from
> source on numerous RPi based systems runnign arch and rpios. I tried
> to build the latest, 1.42, and cannot get past this error:
>
> scripts/libppp-plugin.c:37:10: fatal error: libppp-compat.h: No such
> file or directory
> 37 | #include "libppp-compat.h"
> | ^~~~~~~~~~~~~~~~~
> compilation terminated.
>
> A search for a debian package with this file reveals nothing. What am
> I missing here?
>
> I have used this 'config' for a while w/o issue (I borrowed it from Arch Linux):
>
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
> --runstatedir='/run' \
> --enable-iwd \
> --enable-l2tp \
> --enable-openconnect \
> --enable-openvpn \
> --enable-pie \
> --enable-polkit \
> --enable-pptp \
> --enable-selinux \
> --enable-threads \
> --with-openconnect=/usr/sbin/openconnect \
> --with-openvpn=/usr/sbin/openvpn \
> --with-systemdunitdir=/lib/systemd/system \
> --with-tmpfilesdir=/usr/lib/tmpfiles.d
>
> Any help appreciated.
>
> Keith
Problem solved. Someone noted this previously that it was in the wrong
place in the tar file. I am guessing that between 1.42 and Head there
is a patch to fix it b/c I was able to build connman-git to the
current Head with the config as above. I tested it and it seems to run
w/o issue on arm64 on a RPi.
Keith
prev parent reply other threads:[~2023-12-22 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 13:49 cannot build release 1.42 on RPiOS KeithG
2023-12-22 20:13 ` KeithG [this message]
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='CAG17S_MLsYxcvFpf3v4t578a6=0MuTUiNYj8SinzA5-DQr6jWw@mail.gmail.com' \
--to=ys3al35l@gmail.com \
--cc=connman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).