Build failed. #2

mullex · 2015-06-12T10:14:42Z

I git cloned the project to local and use make to build it. I then got the error message below. What is the problem?

make[1]: ../juci-build-tpl-cache: Command not found
make[1]: *** [htdocs/js/01-juci-tpl.js] Error 127
make[1]: Leaving directory `/home/alex/Projects/luci-express/juci'
make: *** [juci] Error 2

mkschreder · 2015-06-12T11:06:01Z

It should be there. Works for me.

git clone https://github.com/mkschreder/luci-express.git
cd luci-express
make

You must have probably deleted the file or something.

On Fri, Jun 12, 2015 at 12:14 PM, mullex notifications@github.com wrote:

I git cloned the project to local and use make to build it. I then got the
error message below. What is the problem?

make[1]: ../juci-build-tpl-cache: Command not found
make[1]: *** [htdocs/js/01-juci-tpl.js] Error 127
make[1]: Leaving directory `/home/alex/Projects/luci-express/juci'
make: *** [juci] Error 2

—
Reply to this email directly or view it on GitHub
#2.

mkschreder · 2015-06-12T11:07:01Z

If you are integrating it to openwrt build process then make sure you copy
the whole juci folder to builddir and then execute make in the correct
directory.

On Fri, Jun 12, 2015 at 1:05 PM, Martin Schroeder <
mkschreder.uk@googlemail.com> wrote:

It should be there. Works for me.

git clone https://github.com/mkschreder/luci-express.git
cd luci-express
make

You must have probably deleted the file or something.

On Fri, Jun 12, 2015 at 12:14 PM, mullex notifications@github.com wrote:

I git cloned the project to local and use make to build it. I then got
the error message below. What is the problem?

make[1]: ../juci-build-tpl-cache: Command not found
make[1]: *** [htdocs/js/01-juci-tpl.js] Error 127
make[1]: Leaving directory `/home/alex/Projects/luci-express/juci'
make: *** [juci] Error 2

—
Reply to this email directly or view it on GitHub
#2.

mullex · 2015-06-13T02:31:32Z

Many thanks. I placed the whole folder inside builddir and then It compiles fine. But i didn't find it in make menuconfig.How can i install it to openwrt.

mkschreder · 2015-06-13T09:33:28Z

There is an openwrt package for juci in iopsys sdk under
package/inteno/webgui/juci. In juci readme are instructions on how to
checkout iopsys sdk through git. So actually you should let the wrt
makefile checkout juci and build it. Then it will also build all
dependencies and create an ipk.
On 13 Jun 2015 04:31, "mullex" notifications@github.com wrote:

Many thanks. I placed the whole folder inside builddir and then It
compiles fine. But i didn't find it in make menuconfig.How can i install it
to openwrt.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-14T05:46:32Z

I followed the instructions. But when i run "make" inside the iop folder, I always got the error message below.

Checking out files from the git repository...
Cloning into 'mtd-utils-1.4.5'...
ssh_exchange_identification: read: Connection reset by peer
fatal: Could not read from remote repository.

mullex · 2015-06-15T06:53:11Z

I used your mirror of iop on github. The issue above was gone but i got the following errors. Does this work for u?

echo "Checking out files from the git repository..."; mkdir -p /home/mullex/Projects/iop/tmp/dl && cd /home/mullex/Projects/iop/tmp/dl && rm -rf ice-client-3.1.0 && [ ! -d ice-client-3.1.0 ] && git clone ssh://git@iopsys.inteno.se/ice-client.git ice-client-3.1.0 && (cd ice-client-3.1.0 && git checkout 249d6033274f93da343b7fb5879dae0edc5f9682) && echo "Packing checkout..." && /usr/bin/gtar cfz /home/mullex/Projects/iop/tmp/dl/ice-client-3.1.0-RC4.tar.gz ice-client-3.1.0 && mv /home/mullex/Projects/iop/tmp/dl/ice-client-3.1.0-RC4.tar.gz /home/mullex/Projects/iop/dl/ && rm -rf ice-client-3.1.0;
Checking out files from the git repository...
Cloning into 'ice-client-3.1.0'...
ssh_exchange_identification: read: Connection reset by peer

mkschreder · 2015-06-15T07:26:20Z

Thats ok. ice client is inteno specific utility so you will not be able to
build it anyway. The same goes for the broadcom wifi stuff that is closed
source from broadcom. But you will not need that one either unless you
build for an inteno target. Iopsys public sdk will be updated in due time
to include working alternatives for these things. But for now you can just
disable the packages that you can't compile.

Since you have gotten this far, what you can do is actually just build juci
and it's dependencies by doing "make package/inteno/webgui/juci/compile".

Also note that the github mirror you checked out was not the
latest-latest.. so you may wanna do a pull on that one.
On 15 Jun 2015 08:53, "mullex" notifications@github.com wrote:

I used your mirror of iop on github. The issue above was gone but i got
the following errors. Does this work for u?

echo "Checking out files from the git repository..."; mkdir -p
/home/mullex/Projects/iop/tmp/dl && cd /home/mullex/Projects/iop/tmp/dl &&
rm -rf ice-client-3.1.0 && [ ! -d ice-client-3.1.0 ] && git clone ssh://
git@iopsys.inteno.se/ice-client.git ice-client-3.1.0 && (cd
ice-client-3.1.0 && git checkout 249d6033274f93da343b7fb5879dae0edc5f9682)
&& echo "Packing checkout..." && /usr/bin/gtar cfz
/home/mullex/Projects/iop/tmp/dl/ice-client-3.1.0-RC4.tar.gz
ice-client-3.1.0 && mv
/home/mullex/Projects/iop/tmp/dl/ice-client-3.1.0-RC4.tar.gz
/home/mullex/Projects/iop/dl/ && rm -rf ice-client-3.1.0;
Checking out files from the git repository...
Cloning into 'ice-client-3.1.0'...
ssh_exchange_identification: read: Connection reset by peer

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-15T10:32:46Z

Sorry for keep asking questions as this is the first time i build iop though i have a couple years of experience with openwrt.

I executed the following steps:
1.git clone http://ihgsp.inteno.se/git/iopsysAA.git iop
2.cd iop
3.git checkout BB
4./iop_get_feeds.sh
5.make package/inteno/webgui/juci/compile
I got the following error:
make[1]: Entering directory /home/alex/Projects/iop' make[1]: *** No rule to make targetpackage/inteno/webgui/juci/compile'. Stop.
make[1]: Leaving directory `/home/alex/Projects/iop'
make: *** [package/inteno/webgui/juci/compile] Error 2

When i execute the make package/inteno/webgui/juci/juci-compile, i got the following error
make: `package/inteno/webgui/juci/juci-compile' is up to date.

mkschreder · 2015-06-15T10:44:30Z

Try checkout BB-martin
On 15 Jun 2015 12:32, "mullex" notifications@github.com wrote:

Sorry for keep asking questions as this is the first time i build iop
though i have a couple years of experience with openwrt.

I executed the following steps:
1.git clone http://ihgsp.inteno.se/git/iopsysAA.git iop
2.cd iop
3.git checkout BB
4./iop_get_feeds.sh
5.make package/inteno/webgui/juci/compile
I got the following error:
make[1]: Entering directory /home/alex/Projects/iop'
make[1]: *** No rule to make targetpackage/inteno/webgui/juci/compile'.
Stop.
make[1]: Leaving directory `/home/alex/Projects/iop'
make: *** [package/inteno/webgui/juci/compile] Error 2

When i execute the make package/inteno/webgui/juci/juci-compile, i got the
following error
make: `package/inteno/webgui/juci/juci-compile' is up to date.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mkschreder · 2015-06-15T10:46:58Z

A huge merge is coming soon on master. Then hopefully things will work much
better.
On 15 Jun 2015 12:44, "Martin Schroeder" mkschreder.uk@googlemail.com
wrote:

Try checkout BB-martin
On 15 Jun 2015 12:32, "mullex" notifications@github.com wrote:

Sorry for keep asking questions as this is the first time i build iop
though i have a couple years of experience with openwrt.

I executed the following steps:
1.git clone http://ihgsp.inteno.se/git/iopsysAA.git iop
2.cd iop
3.git checkout BB
4./iop_get_feeds.sh
5.make package/inteno/webgui/juci/compile
I got the following error:
make[1]: Entering directory /home/alex/Projects/iop'
make[1]: *** No rule to make targetpackage/inteno/webgui/juci/compile'.
Stop.
make[1]: Leaving directory `/home/alex/Projects/iop'
make: *** [package/inteno/webgui/juci/compile] Error 2

When i execute the make package/inteno/webgui/juci/juci-compile, i got
the following error
make: `package/inteno/webgui/juci/juci-compile' is up to date.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-15T11:01:44Z

I hope that can come soon. I really like your project:)

1.I tried to execute git checkout BB-martin
2.I still got errors.

make package/inteno/webgui/juci/compile V=s
Collecting package info: done
package/Makefile:105: warning: overriding recipe for target package/cg300/clean' package/Makefile:105: warning: ignoring old recipe for targetpackage/cg300/clean'
make[1]: *** No rule to make target package/inteno/webgui/juci/compile'. Stop. make[1]: Leaving directory/home/alex/Projects/iop'
make: *** [package/inteno/webgui/juci/compile] Error 2

mkschreder · 2015-06-15T11:09:04Z

I just realized that you will not be able to build it either because it
needs to pull configs from a repo you don't have access to. I will need to
add default configs. It is actually on my todo list..

There is a script called genconfig. It takes hardware and profile as first
and second argument. It then sets top level targe package and then the rest
is handled by defconfig to select all other packages based on dependencies.
It needs to be run first before make. This actually allows one to have many
different customer profiles with different packages for each target.

What hardware are you using?
On 15 Jun 2015 13:01, "mullex" notifications@github.com wrote:

I hope that can come soon. I really like your project:)

1.I tried to execute git checkout BB-martin
2.I still got errors.

make package/inteno/webgui/juci/compile V=s
Collecting package info: done
package/Makefile:105: warning: overriding recipe for target
package/cg300/clean'
package/Makefile:105: warning: ignoring old recipe for target
package/cg300/clean'
make[1]: *** No rule to make target package/inteno/webgui/juci/compile'.
Stop.
make[1]: Leaving directory/home/alex/Projects/iop'
make: *** [package/inteno/webgui/juci/compile] Error 2

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-15T11:25:25Z

I am using CentOS(x86_64) 7 with VMWARE as the build machine. It has 4-Core CPU,4G RAM,100G SCSI HDD.

mkschreder · 2015-06-15T11:32:35Z

But what is your build target?
On 15 Jun 2015 13:25, "mullex" notifications@github.com wrote:

I am using CentOS(x86_64) 7 with VMWARE as the build machine. It has
4-Core CPU,4G RAM,100G SCSI HDD.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-15T11:37:12Z

my build target is for X86_64.

mullex · 2015-06-18T09:42:50Z

Is there any progress on this?

mkschreder · 2015-06-18T17:46:23Z

There is always progress. :-) but we focus mainly on developing for inteno
hardware. Everything else is secondary.
On 18 Jun 2015 11:42, "mullex" notifications@github.com wrote:

Is there any progress on this?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-06-19T11:02:46Z

Do you mean that juci will support Inteno devices for the time being? Does it support any other openwrt devices as i really like juci and want to use it in our project.

mkschreder · 2015-06-20T11:12:44Z

It is mostly the backend that is the issue. Juci will work on any device
and if you write your own modules for your device then you're fine. It's
just that currently the backend is actually scattered around several
daemons with functions that are tied into broadcom specifics.

It would be good to break up these daemons into clean ubus modules that can
be tied with corresponding juci app, but the daemons have been around for
way longer than juci so they are used in other places as well. The daemons
have been originally created only with broadcom in mind. And then I have
just built juci on top of the existing ubus api that was already in place.

For an idea of what is needed, here is a repo that will build a juci setup
with uhttpd and all the daemons locally:

git clone https://github.com/mkschreder/juci-feed.git

Do a make then make install then sudo bash server start and go to port 8080
locally. Of course this will be missing a lot of things if you just run it
locally on a pc rather than on a real device, but it is still a fully
standalone setup that is not even dependent on openwrt to run.

So as long as the juci modules can be tailored to work on a desktop pc then
this setup will work just as well as on an inteno router. This repo is just
a proof of concept of how to make it work. I'm not responsible for any
crashes or bugs you're going to get with this setup ;-) use at your own
risk.

Do you mean that juci will support Inteno devices for the time being? Does
it support any other openwrt devices as i really like juci and want to use
it in our project.

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-07-08T10:55:44Z

git clone https://github.com/mkschreder/juci-feed.git
make

I got the following error so i still couldn't get it compiled and running

..............
Compiling CSS bin/www/css/01-juci.css..
YUICompressor Version: 2.4.8

Usage: java -jar yuicompressor-2.4.8.jar [options] [input file]

Global Options
-V, --version Print version information
-h, --help Displays this information
--type <js|css> Specifies the type of the input file
--charset Read the input file using
--line-break Insert a line break after the specified column number
-v, --verbose Display informational messages and warnings
-o Place the output into . Defaults to stdout.
Multiple files can be processed using the following syntax:
java -jar yuicompressor.jar -o '.css$:-min.css' *.css
java -jar yuicompressor.jar -o '.js$:-min.js' *.js

JavaScript Options
--nomunge Minify only, do not obfuscate
--preserve-semi Preserve all semicolons
--disable-optimizations Disable all micro optimizations

If no input file is specified, it defaults to stdin. In this case, the 'type'
option is required. Otherwise, the 'type' option is required only if the input
file extension is neither 'js' nor 'css'.
make: *** [all] Error 1

mkschreder · 2015-07-09T08:09:21Z

Can you debug a bit more? Try a clean build from clean checkout. Make sure
you are using bash as your shell.

Check that you can run the yui compressor command manually:

yui-compressor

If nothing works then you can just comment out the line using yui
compressor. It just makes the css file smaller but it is not strictly
mandatory.

git clone https://github.com/mkschreder/juci-feed.git
make

I got the following error so i still couldn't get it compiled and running

..............
Compiling CSS bin/www/css/01-juci.css..
YUICompressor Version: 2.4.8

Usage: java -jar yuicompressor-2.4.8.jar [options] [input file]

Global Options
-V, --version Print version information
-h, --help Displays this information
--type Specifies the type of the input file
--charset Read the input file using
--line-break Insert a line break after the specified column number
-v, --verbose Display informational messages and warnings
-o Place the output into . Defaults to stdout.
Multiple files can be processed using the following syntax:
java -jar yuicompressor.jar -o '.css$:-min.css' *.css
java -jar yuicompressor.jar -o '.js$:-min.js' *.js

JavaScript Options
--nomunge Minify only, do not obfuscate
--preserve-semi Preserve all semicolons
--disable-optimizations Disable all micro optimizations

If no input file is specified, it defaults to stdin. In this case, the
'type'
option is required. Otherwise, the 'type' option is required only if the
input
file extension is neither 'js' nor 'css'.
make: *** [all] Error 1

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-07-09T10:20:31Z

I can always debug it as long as you are available on this:)))

I commented out the following lines in juci-compile(i had to comment out mv statement there is an error complaining about a mssing .out file).
for file in find bin/www/css/ -name "*.css"; do
echo "Compiling CSS ${file}.."
#yui-compressor ${file} > ${file}.out
#mv ${file}.out ${file}
done

Then make and make install worked!

But when i run sudo bash server start, got the following error:
[root@localhost juci-feed]# sudo bash server start
PATH:/home/alex/Projects/juci/juci-feed/build/bin:/sbin:/bin:/usr/sbin:/usr/bin
UBUS
RPCD
rpcd: connected to ubus
rpcd: session init
rpcd: uci init
rpcd: plugin init
rpcd: loading /usr/lib/rpcd/juci-ubus-core.so
rpcd: purge savedirs
rpcd: started
QUEST
NETIF
UHTTPD
connected as 502c3854
[root@localhost juci-feed]# chdir(main path): No such file or directory
chdir(main path): No such file or directory
Failed to load network config

mkschreder · 2015-07-09T10:49:20Z

That is actually netifd that is giving that error and it's ok. The local
uhttpd should run in the background anyway. For development it is usually
better to use juci-local-server and connect to a real box running uhttpd
over ubus.
On 9 Jul 2015 12:20, "mullex" notifications@github.com wrote:

I can always debug it as long as you are available on this:)))

I commented out the following lines in juci-compile(i had to comment out
mv statement there is an error complaining about a mssing .out file).
for file in find bin/www/css/ -name "*.css"; do
echo "Compiling CSS ${file}.."
#yui-compressor ${file} > ${file}.out
#mv ${file}.out ${file}
done

Then make and make install worked!

But when i run sudo bash server start, got the following error:
[root@localhost juci-feed]# sudo bash server start

PATH:/home/alex/Projects/juci/juci-feed/build/bin:/sbin:/bin:/usr/sbin:/usr/bin
UBUS
RPCD
rpcd: connected to ubus
rpcd: session init
rpcd: uci init
rpcd: plugin init
rpcd: loading /usr/lib/rpcd/juci-ubus-core.so
rpcd: purge savedirs
rpcd: started
QUEST
NETIF
UHTTPD
connected as 502c3854
[root@localhost juci-feed]# chdir(main path): No such file or directory
chdir(main path): No such file or directory
Failed to load network config

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

mullex · 2015-07-09T16:17:19Z

It finally works fine and i can open 127.0.0.1:8080

What is the default password for admin?

mkschreder · 2015-07-09T17:02:28Z

The same as for linux user admin.
On 9 Jul 2015 18:17, "mullex" notifications@github.com wrote:

It finally works fine and i can open 127.0.0.1:8080

What is the default password for admin?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

Issue #2: Universalize nodejs script shebang.

…ile. !! important #2: all menu items are now decoupled from filenames of the pages. Instead, there is now a single menu.json file in the theme that governs the menu. This makes customization simpler and allows to customize menus specifically for each deployment profile. nr. 2 allows now to completely decouple menu structure from the names of the files. You still should call your files same as html tag names and urls, but menu items themselves should now contain "page" parameter that specifes filename of the page. Old way is currently supported also, but not for long. All future developmet will use the new way of structuring menus.

max-b added a commit to max-b/luci-express that referenced this issue Jul 30, 2015

Issue mkschreder#2: Universalize nodejs script shebang.

e0abd1f

max-b added a commit to max-b/luci-express that referenced this issue Jul 30, 2015

Issue mkschreder#2: Universalize nodejs script shebang.

4f40e1d

max-b added a commit to max-b/luci-express that referenced this issue Jul 30, 2015

Issue mkschreder#2: Universalize nodejs script shebang.

47aef17

mkschreder added a commit that referenced this issue Jul 30, 2015

Merge pull request #4 from max-b/issue-2

f722808

Issue #2: Universalize nodejs script shebang.

mkschreder closed this as completed Oct 28, 2015

whales-lee mentioned this issue Nov 14, 2021

firefox visit openwrt juci got a running cycle. F12 network print these messages: #92

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Build failed. #2

Build failed. #2

mullex commented Jun 12, 2015

mkschreder commented Jun 12, 2015

mkschreder commented Jun 12, 2015

mullex commented Jun 13, 2015

mkschreder commented Jun 13, 2015

mullex commented Jun 14, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mullex commented Jun 18, 2015

mkschreder commented Jun 18, 2015

mullex commented Jun 19, 2015

mkschreder commented Jun 20, 2015

mullex commented Jul 8, 2015

mkschreder commented Jul 9, 2015

mullex commented Jul 9, 2015

mkschreder commented Jul 9, 2015

mullex commented Jul 9, 2015

mkschreder commented Jul 9, 2015

Build failed. #2

Build failed. #2

Comments

mullex commented Jun 12, 2015

mkschreder commented Jun 12, 2015

mkschreder commented Jun 12, 2015

mullex commented Jun 13, 2015

mkschreder commented Jun 13, 2015

mullex commented Jun 14, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mkschreder commented Jun 15, 2015

mullex commented Jun 15, 2015

mullex commented Jun 18, 2015

mkschreder commented Jun 18, 2015

mullex commented Jun 19, 2015

mkschreder commented Jun 20, 2015

mullex commented Jul 8, 2015

mkschreder commented Jul 9, 2015

mullex commented Jul 9, 2015

mkschreder commented Jul 9, 2015

mullex commented Jul 9, 2015

mkschreder commented Jul 9, 2015