18 Jul
2016
18 Jul
'16
4:15 p.m.
2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net>et>:
From the README: Or to use your own LiMe packages git
repository and/or
OpenWRT/LEDE (must be executed the first time make is invoked or after
clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx P=generic
OWRT_GIT="http://foo.git" <http://foo.git>
I tried to compile LiMe on LEDE using lime-build develop, I simply issued:
make T=ar71xx P=generic OWRT_GIT="
https://git.lede-project.org/source.git"
but I noticed that there are lines in the feeds.conf file [1] included in
lime-build which are pointing to our static OpenWrt repos.
So, what is a good procedure to build LiMe on LEDE using lime-build?
Is it enough to remove those lines in the feeds.conf file and specify the
OWRT_GIT parameter pointing to LEDE source?
Thanks,
Ilario
[1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf
6 Sep
6 Sep
1:17 a.m.
Trying to get caught up after some time away and having trouble
building. This was with a fresh git clone running Ubuntu 16.04 x64. I
didn't try running again with `-j1 V=s` yet.
http://pastebin.com/k4cU8Uyj
Also, if I understand the recent threads, downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
On 07/18/2016 11:15 AM, Ilario wrote:
2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net
<mailto:pau@dabax.net>>:
From the README: Or to use your own LiMe packages git repository
and/or OpenWRT/LEDE (must be executed the first time make is
invoked or after clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx
P=generic OWRT_GIT="http://foo.git" <http://foo.git>
I tried to compile LiMe on LEDE using lime-build develop, I simply issued:
make T=ar71xx P=generic
OWRT_GIT="https://git.lede-project.org/source.git"
but I noticed that there are lines in the feeds.conf file [1] included
in lime-build which are pointing to our static OpenWrt repos.
So, what is a good procedure to build LiMe on LEDE using lime-build?
Is it enough to remove those lines in the feeds.conf file and specify
the OWRT_GIT parameter pointing to LEDE source?
Thanks,
Ilario
[1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
10:37 a.m.
Hi Marvin.
We cannot help you if you do not post the result of "-j1 V=s". You can
execute:
make T=ar71xx P=generic J=1 V=s
Probably there is some missing dependency on your Ubuntu system required
for building OpenWRT. On the README you can find a list of packages
which you might install before compiling [1].
The binaries of http://builds.libre-mesh.org for release 16.07 should
work fine.
Cheers.
[1] https://github.com/libre-mesh/lime-build/blob/develop/README.md
On 06/09/16 03:17, Marvin Arnold wrote:
Trying to get caught up after some time away and
having trouble
building. This was with a fresh git clone running Ubuntu 16.04 x64. I
didn't try running again with `-j1 V=s` yet.
http://pastebin.com/k4cU8Uyj
Also, if I understand the recent threads, downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
On 07/18/2016 11:15 AM, Ilario wrote:
--
./p4u
2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net
<mailto:pau@dabax.net>>:
From the README: Or to use your own LiMe packages git repository
and/or OpenWRT/LEDE (must be executed the first time make is
invoked or after clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx
P=generic OWRT_GIT="http://foo.git" <http://foo.git>
I tried to compile LiMe on LEDE using lime-build develop, I simply issued:
make T=ar71xx P=generic
OWRT_GIT="https://git.lede-project.org/source.git"
but I noticed that there are lines in the feeds.conf file [1] included
in lime-build which are pointing to our static OpenWrt repos.
So, what is a good procedure to build LiMe on LEDE using lime-build?
Is it enough to remove those lines in the feeds.conf file and specify
the OWRT_GIT parameter pointing to LEDE source?
Thanks,
Ilario
[1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
7 Sep
7 Sep
12:55 a.m.
Thank Pau,
Just reran with -j1 V=s and it compiled fine. I think this might be a
similar issue I experienced before where trying to compile with J > 1
doesn't work. I guess I'll just always use 1 for now.
By the way I had installed all the packages from README before compiling
the first time.
On 09/06/2016 05:37 AM, Pau wrote:
Hi Marvin.
We cannot help you if you do not post the result of "-j1 V=s". You can
execute:
make T=ar71xx P=generic J=1 V=s
Probably there is some missing dependency on your Ubuntu system required
for building OpenWRT. On the README you can find a list of packages
which you might install before compiling [1].
The binaries of http://builds.libre-mesh.org for release 16.07 should
work fine.
Cheers.
[1] https://github.com/libre-mesh/lime-build/blob/develop/README.md
On 06/09/16 03:17, Marvin Arnold wrote:
Trying to get caught up after some time away and
having trouble
building. This was with a fresh git clone running Ubuntu 16.04 x64. I
didn't try running again with `-j1 V=s` yet.
http://pastebin.com/k4cU8Uyj
Also, if I understand the recent threads, downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
On 07/18/2016 11:15 AM, Ilario wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev 2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net
<mailto:pau@dabax.net>>:
From the README: Or to use your own LiMe packages git repository
and/or OpenWRT/LEDE (must be executed the first time make is
invoked or after clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx
P=generic OWRT_GIT="http://foo.git" <http://foo.git>
I tried to compile LiMe on LEDE using lime-build develop, I simply issued:
make T=ar71xx P=generic
OWRT_GIT="https://git.lede-project.org/source.git"
but I noticed that there are lines in the feeds.conf file [1] included
in lime-build which are pointing to our static OpenWrt repos.
So, what is a good procedure to build LiMe on LEDE using lime-build?
Is it enough to remove those lines in the feeds.conf file and specify
the OWRT_GIT parameter pointing to LEDE source?
Thanks,
Ilario
[1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
8 Sep
8 Sep
1:38 p.m.
I've compiled many times with J>1 and it worked fine most of the times
(just to let you know and save you some compilation time). Take into
account that if there is some Internet cut (or the destination server is
down at that moment), compilation might fail when trying to download
some packet source. So this might be one explanation for a "random" crash.
Anyway, congratulations for the success :)
On 07/09/16 02:55, Marvin Arnold wrote:
Thank Pau,
Just reran with -j1 V=s and it compiled fine. I think this might be a
similar issue I experienced before where trying to compile with J > 1
doesn't work. I guess I'll just always use 1 for now.
By the way I had installed all the packages from README before compiling
the first time.
On 09/06/2016 05:37 AM, Pau wrote:
--
./p4u
Hi Marvin.
We cannot help you if you do not post the result of "-j1 V=s". You can
execute:
make T=ar71xx P=generic J=1 V=s
Probably there is some missing dependency on your Ubuntu system required
for building OpenWRT. On the README you can find a list of packages
which you might install before compiling [1].
The binaries of http://builds.libre-mesh.org for release 16.07 should
work fine.
Cheers.
[1] https://github.com/libre-mesh/lime-build/blob/develop/README.md
On 06/09/16 03:17, Marvin Arnold wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
Trying to get caught up after some time away and
having trouble
building. This was with a fresh git clone running Ubuntu 16.04 x64. I
didn't try running again with `-j1 V=s` yet.
http://pastebin.com/k4cU8Uyj
Also, if I understand the recent threads, downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
On 07/18/2016 11:15 AM, Ilario wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev 2016-07-11 20:49 GMT+02:00 p4u <pau(a)dabax.net
<mailto:pau@dabax.net>>:
From the README: Or to use your own LiMe packages git repository
and/or OpenWRT/LEDE (must be executed the first time make is
invoked or after clean).
make LIME_GIT="http://foo.git" <http://foo.git> T=ar71xx
P=generic OWRT_GIT="http://foo.git" <http://foo.git>
I tried to compile LiMe on LEDE using lime-build develop, I simply issued:
make T=ar71xx P=generic
OWRT_GIT="https://git.lede-project.org/source.git"
but I noticed that there are lines in the feeds.conf file [1] included
in lime-build which are pointing to our static OpenWrt repos.
So, what is a good procedure to build LiMe on LEDE using lime-build?
Is it enough to remove those lines in the feeds.conf file and specify
the OWRT_GIT parameter pointing to LEDE source?
Thanks,
Ilario
[1] https://github.com/libre-mesh/lime-build/blob/develop/feeds.conf
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
2:13 p.m.
2016-09-08 15:38 GMT+02:00 Pau <pau(a)dabax.net>et>:
Take into
account that if there is some Internet cut (or the destination server is
down at that moment), compilation might fail when trying to download
some packet source. So this might be one explanation for a "random" crash.
Yep, also in my experience the build sometime fails for some network
problem, simply issuing again the same command (or with J=1) usually
solves.
Anyway this issue is not Libre-Mesh related, it happens also compiling
plain OpenWrt :)
On 09/06/2016 03:17 AM, Marvin Arnold wrote:
if I understand the recent threads,
downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
At this very moment both subdomains points to the same content :)
2:16 p.m.
Thanks both. I'll make a pull request to update the build instructions
with a small note.
On 09/08/2016 09:13 AM, Ilario wrote:
2016-09-08 15:38 GMT+02:00 Pau <pau(a)dabax.net>et>:
Take into
account that if there is some Internet cut (or the destination server is
down at that moment), compilation might fail when trying to download
some packet source. So this might be one explanation for a "random" crash.
Yep, also in my experience the build sometime fails for some network
problem, simply issuing again the same command (or with J=1) usually
solves.
Anyway this issue is not Libre-Mesh related, it happens also compiling
plain OpenWrt :)
On 09/06/2016 03:17 AM, Marvin Arnold wrote:
if I understand the recent threads,
downloads.libre-mesh should be
ignored until it gets pointed to builds.libre-mesh?
At this very moment both
subdomains points to the same content :)
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
3026
days inactive
3078
days old
6 comments
3 participants
participants (3)
-
Ilario -
Marvin Arnold -
Pau