20200117_jeffrey - silenceuncrio/diary GitHub Wiki
0845
review
為了 m350 的工作環境
昨天發生的問題就不去追了
把 m350 整個 source code 砍掉
VMware 關機
Vmware 的 host - window 10 也重開機
藉由觀察 工作管理員 的 磁碟 項目
等著不忙碌的時候再把 VMware 叫起來
先 review 這個禮拜的進度
m330[release/v0.08]
- GRE tunnel keepalive 整合測試
- correct the title of GRE edit web page
- handle keepalive request by ourself when gre interface down
- apply gre while receive event ICOS_WAN_GATEWAY_UPDATE
- refactoring the 'WAN DNS' at status page
- broadcast event when gre interface up/down
- while receive event ICOS_WETH_LINK_UP, apply gre again
- in gre, use event ICOS_WAN_IP_UPDATE to replace ICOS_WAN_GATEWAY_UPDATE and ICOS_WETH_LINK_UP
m350
- prepare the working environment
後續的 task
M300
- 無工作項目
M330
- P1 - GRE Keepalive
- P2 - Web UI; GPS Track drawing(Server)
M350
- GRE
- Web UI
- Firmware Upgrade
- GRE keepalive
M360
- 無工作項目
寫個週報吧
1015
可以把 VMware 叫起來了
重新 checkout m350 source code
切換到 branch develop
再進入為了 build m350 而建立的 container
user@de6137d6ddd7:~$ make
Checking 'uuencode'... ok.
make[1] world
make[2] tools/install
make[3] -C tools/patch compile
make[3] -C tools/patch install
make[3] -C tools/sed compile
make[3] -C tools/sed install
make[3] -C tools/m4 compile
make[3] -C tools/m4 install
make[3] -C tools/autoconf compile
make[3] -C tools/autoconf install
make[3] -C tools/pkg-config compile
make[3] -C tools/pkg-config install
make[3] -C tools/xz compile
make[3] -C tools/xz install
make[3] -C tools/automake compile
make -r world: build failed. Please re-run make with -j1 V=s to see what's going on
/home/user/include/toplevel.mk:186: recipe for target 'world' failed
make: *** [world] Error 1
user@de6137d6ddd7:~$
卡在之前相同的地方
利用 make V=s 看看出了什麼錯
user@de6137d6ddd7:~$ make V=s
make[1]: Entering directory '/home/user'
make[2]: Entering directory '/home/user'
+ mkdir -p /home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi
+ cd /home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi
+ mkdir -p bin lib include stamp
mkdir -p /home/user/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/stamp
touch /home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/.prepared
+ mkdir -p /home/user/staging_dir/host
+ cd /home/user/staging_dir/host
+ mkdir -p bin lib include stamp
mkdir -p /home/user/build_dir/host/stamp /home/user/staging_dir/host/include/sys
install -m0644 /home/user/tools/include/*.h /home/user/staging_dir/host/include/
install -m0644 /home/user/tools/include/sys/*.h /home/user/staging_dir/host/include/sys/
ln -sf lib /home/user/staging_dir/host/lib64
touch /home/user/staging_dir/host/.prepared
make[3]: Entering directory '/home/user/tools/patch'
make[3]: Leaving directory '/home/user/tools/patch'
make[3]: Entering directory '/home/user/tools/patch'
make[3]: Leaving directory '/home/user/tools/patch'
make[3]: Entering directory '/home/user/tools/sed'
make[3]: Leaving directory '/home/user/tools/sed'
make[3]: Entering directory '/home/user/tools/sed'
make[3]: Leaving directory '/home/user/tools/sed'
make[3]: Entering directory '/home/user/tools/m4'
make[3]: Leaving directory '/home/user/tools/m4'
make[3]: Entering directory '/home/user/tools/m4'
make[3]: Leaving directory '/home/user/tools/m4'
make[3]: Entering directory '/home/user/tools/autoconf'
make[3]: Leaving directory '/home/user/tools/autoconf'
make[3]: Entering directory '/home/user/tools/autoconf'
make[3]: Leaving directory '/home/user/tools/autoconf'
make[3]: Entering directory '/home/user/tools/pkg-config'
make[3]: Leaving directory '/home/user/tools/pkg-config'
make[3]: Entering directory '/home/user/tools/pkg-config'
make[3]: Leaving directory '/home/user/tools/pkg-config'
make[3]: Entering directory '/home/user/tools/xz'
make[3]: Leaving directory '/home/user/tools/xz'
make[3]: Entering directory '/home/user/tools/xz'
make[3]: Leaving directory '/home/user/tools/xz'
make[3]: Entering directory '/home/user/tools/automake'
(cd /home/user/build_dir/host/automake-1.15; AUTOM4TE=/home/user/staging_dir/host/bin/autom4te AUTOCONF=/home/user/staging_dir/host/bin/autoconf AUTOMAKE=/home/user/staging_dir/host/bin/automake ACLOCAL=/home/u$er/staging_dir/host/bin/aclocal AUTOHEADER=/home/user/staging_dir/host/bin/autoheader LIBTOOLIZE=/home/user/staging_dir/host/bin/libtoolize LIBTOOL=/home/user/staging_dir/host/bin/libtool M4=/home/user/staging_$ir/host/bin/m4 AUTOPOINT=true STAGING_DIR="" ./bootstrap.sh)
Can't locate loadable object for module threads in @INC (@INC contains: ./automake-1.15 /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /us
r/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at automake-1.15/Automake/ChannelDefs.pm line 23.
Compilation failed in require at automake-1.15/Automake/ChannelDefs.pm line 23.
BEGIN failed--compilation aborted at automake-1.15/Automake/ChannelDefs.pm line 26.
Compilation failed in require at automake-1.15/Automake/Configure_ac.pm line 27.
BEGIN failed--compilation aborted at automake-1.15/Automake/Configure_ac.pm line 27.
Compilation failed in require at ./bin/aclocal.tmp line 41.
BEGIN failed--compilation aborted at ./bin/aclocal.tmp line 41.
Makefile:50: recipe for target '/home/user/build_dir/host/automake-1.15/.configured' failed
make[3]: *** [/home/user/build_dir/host/automake-1.15/.configured] Error 2
make[3]: Leaving directory '/home/user/tools/automake'
tools/Makefile:124: recipe for target 'tools/automake/compile' failed
make[2]: *** [tools/automake/compile] Error 2
make[2]: Leaving directory '/home/user'
tools/Makefile:123: recipe for target '/home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/stamp/.tools_install_yynyynyynynyyyyyyyyynyyyyyyyyynyyyyynnyyyynnyynnnyy' failed
make[1]: *** [/home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/stamp/.tools_install_yynyynyynynyyyyyyyyynyyyyyyyyynyyyyynnyyyynnyynnnyy] Error 2
make[1]: Leaving directory '/home/user'
/home/user/include/toplevel.mk:186: recipe for target 'world' failed
make: *** [world] Error 2
user@de6137d6ddd7:~$
1045
為了 m350 另外再建一個 VMware 吧
不過先用 m330 確認一下到底我的 VMware 還能不能 build
可以
另外建立 VMware 虛擬機之前
先找一下之前安裝 VMware 的紀錄
- 20180604_jeffrey
- 換了一台新的 window 電腦
- 安裝了 VMware Workstation 12 Player
- Ubuntu 16.04 LTS 64 位元版本
1100
重裝 VMware 虛擬機之前再掙扎一下
因為 m350 後續要改用 32 位元的作業系統才能 build uboot
所以要用新的 docker image
簡單紀錄一下
➜ ~ git clone [email protected]:RD/build-m350.git
Cloning into 'build-m350'...
remote: Enumerating objects: 11, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 11 (delta 2), reused 0 (delta 0)
Receiving objects: 100% (11/11), done.
Resolving deltas: 100% (2/2), done.
Checking connectivity... done.
➜ ~ cd build-m350
➜ build-m350 git:(master) git checkout i386
Branch i386 set up to track remote branch i386 from origin.
Switched to a new branch 'i386'
➜ build-m350 git:(i386) docker build -t build-m350 .
...
- checkout build-m350.git
- 切換到 branch i386
- build docker image
1120
build docker image 的時候會發現紅色的訊息
...
debconf: delaying package configuration, since apt-utils is not installed
...
還不止一處
參考 [16.04] debconf: delaying package configuration, since apt-utils is not installed
再重新產生 docker image
出現另外的紅色字樣
...
Get:85 http://archive.ubuntu.com/ubuntu xenial/main i386 libauthen-sasl-perl all 2.1600-1 [48.7 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 41.7 MB in 3min 15s (213 kB/s)
Selecting previously unselected package libatm1:i386.
...
還原 Dockerfile
1135
試著在 docker host 安裝 apt-utils - 也就是 VMware 上的 Ubuntu 16.04
➜ build-m350 git:(i386) sudo apt-get install apt-utils
[sudo] password for jeffrey:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.13.0-36 linux-headers-4.13.0-36-generic linux-headers-4.13.0-43 linux-headers-4.13.0-43-generic linux-headers-4.13.0-45 linux-headers-4.13.0-45-generic linux-headers-4.15.0-24
linux-headers-4.15.0-24-generic linux-headers-4.15.0-29 linux-headers-4.15.0-29-generic linux-headers-4.15.0-30 linux-headers-4.15.0-30-generic linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic
linux-headers-4.15.0-33 linux-headers-4.15.0-33-generic linux-headers-4.15.0-34 linux-headers-4.15.0-34-generic linux-headers-4.15.0-36 linux-headers-4.15.0-36-generic linux-headers-4.15.0-39
linux-headers-4.15.0-39-generic linux-headers-4.15.0-42 linux-headers-4.15.0-42-generic linux-headers-4.15.0-43 linux-headers-4.15.0-43-generic linux-headers-4.15.0-45 linux-headers-4.15.0-45-generic
linux-headers-4.15.0-46 linux-headers-4.15.0-46-generic linux-headers-4.15.0-47 linux-headers-4.15.0-47-generic linux-headers-4.15.0-50 linux-headers-4.15.0-50-generic linux-headers-4.15.0-51
linux-headers-4.15.0-51-generic linux-headers-4.15.0-52 linux-headers-4.15.0-52-generic linux-headers-4.15.0-54 linux-headers-4.15.0-54-generic linux-headers-4.15.0-55 linux-headers-4.15.0-55-generic
linux-headers-4.15.0-58 linux-headers-4.15.0-58-generic linux-headers-4.15.0-60 linux-headers-4.15.0-60-generic linux-headers-4.15.0-62 linux-headers-4.15.0-62-generic linux-headers-4.15.0-64
linux-headers-4.15.0-64-generic linux-headers-4.15.0-65 linux-headers-4.15.0-65-generic linux-headers-4.15.0-66 linux-headers-4.15.0-66-generic linux-headers-4.15.0-70 linux-headers-4.15.0-70-generic
linux-image-4.13.0-36-generic linux-image-4.13.0-43-generic linux-image-4.13.0-45-generic linux-image-4.15.0-24-generic linux-image-4.15.0-29-generic linux-image-4.15.0-30-generic
linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic linux-image-4.15.0-36-generic linux-image-4.15.0-39-generic linux-image-4.15.0-42-generic
linux-image-4.15.0-43-generic linux-image-4.15.0-45-generic linux-image-4.15.0-46-generic linux-image-4.15.0-47-generic linux-image-4.15.0-50-generic linux-image-4.15.0-51-generic
linux-image-4.15.0-52-generic linux-image-4.15.0-54-generic linux-image-4.15.0-55-generic linux-image-4.15.0-58-generic linux-image-4.15.0-60-generic linux-image-4.15.0-62-generic
linux-image-4.15.0-64-generic linux-image-4.15.0-65-generic linux-image-4.15.0-66-generic linux-image-4.15.0-70-generic linux-image-extra-4.13.0-36-generic linux-image-extra-4.13.0-43-generic
linux-image-extra-4.13.0-45-generic linux-modules-4.15.0-24-generic linux-modules-4.15.0-29-generic linux-modules-4.15.0-30-generic linux-modules-4.15.0-32-generic linux-modules-4.15.0-33-generic
linux-modules-4.15.0-34-generic linux-modules-4.15.0-36-generic linux-modules-4.15.0-39-generic linux-modules-4.15.0-42-generic linux-modules-4.15.0-43-generic linux-modules-4.15.0-45-generic
linux-modules-4.15.0-46-generic linux-modules-4.15.0-47-generic linux-modules-4.15.0-50-generic linux-modules-4.15.0-51-generic linux-modules-4.15.0-52-generic linux-modules-4.15.0-54-generic
linux-modules-4.15.0-55-generic linux-modules-4.15.0-58-generic linux-modules-4.15.0-60-generic linux-modules-4.15.0-62-generic linux-modules-4.15.0-64-generic linux-modules-4.15.0-65-generic
linux-modules-4.15.0-66-generic linux-modules-4.15.0-70-generic linux-modules-extra-4.15.0-45-generic linux-modules-extra-4.15.0-46-generic linux-modules-extra-4.15.0-47-generic
linux-modules-extra-4.15.0-50-generic linux-modules-extra-4.15.0-51-generic linux-modules-extra-4.15.0-52-generic linux-modules-extra-4.15.0-54-generic linux-modules-extra-4.15.0-55-generic
linux-modules-extra-4.15.0-58-generic linux-modules-extra-4.15.0-60-generic linux-modules-extra-4.15.0-62-generic linux-modules-extra-4.15.0-64-generic linux-modules-extra-4.15.0-65-generic
linux-modules-extra-4.15.0-66-generic linux-modules-extra-4.15.0-70-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
apt libapt-pkg5.0
Suggested packages:
aptitude | synaptic | wajig apt-doc python-apt
The following packages will be upgraded:
apt apt-utils libapt-pkg5.0
3 upgraded, 0 newly installed, 0 to remove and 190 not upgraded.
Need to get 1996 kB of archives.
After this operation, 152 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://tw.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libapt-pkg5.0 amd64 1.2.32 [713 kB]
Get:2 http://tw.archive.ubuntu.com/ubuntu xenial-updates/main amd64 apt amd64 1.2.32 [1086 kB]
Get:3 http://tw.archive.ubuntu.com/ubuntu xenial-updates/main amd64 apt-utils amd64 1.2.32 [196 kB]
Fetched 1996 kB in 0s (2368 kB/s)
(Reading database ... 1165508 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.2.32_amd64.deb ...
Unpacking libapt-pkg5.0:amd64 (1.2.32) over (1.2.29ubuntu0.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up libapt-pkg5.0:amd64 (1.2.32) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
(Reading database ... 1165508 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.2.32_amd64.deb ...
Unpacking apt (1.2.32) over (1.2.29ubuntu0.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apt (1.2.32) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
(Reading database ... 1165517 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.2.32_amd64.deb ...
Unpacking apt-utils (1.2.32) over (1.2.29ubuntu0.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apt-utils (1.2.32) ...
再次產生 docker image
...
Get:184 http://archive.ubuntu.com/ubuntu xenial/main i386 libauthen-sasl-perl all 2.1600-1 [48.7 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 83.6 MB in 5min 11s (268 kB/s)
Selecting previously unselected package libatm1:i386.
...
Get:39 http://archive.ubuntu.com/ubuntu xenial/main i386 python-yaml i386 3.11-3build1 [105 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 36.5 MB in 2min 31s (241 kB/s)
Selecting previously unselected package libpcrecpp0v5:i386.
...
看來是我誤解了
apt-utils 裝在 docker host 是沒用的
要透過 Docker file 裝在 docker image 裡
1150
安裝其他東西前先安裝 apt-utils
diff --git a/Dockerfile b/Dockerfile
index ad825b2..2e1a151 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,6 +1,8 @@
FROM i386/ubuntu:16.04
-RUN apt-get update && apt-get install -y \
+RUN apt-get update && apt-get install -y apt-utils
+
+RUN apt-get install -y \
gcc \
g++ \
binutils \
(END)
build docker image
1305
出現不同的錯誤
...
Get:184 http://archive.ubuntu.com/ubuntu xenial/main i386 libauthen-sasl-perl all 2.1600-1 [48.7 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/i386-
linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7,
<> line 184.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
...
Get:39 http://archive.ubuntu.com/ubuntu xenial/main i386 python-yaml i386 3.11-3build1 [105 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
...
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 libssl-doc all 1.0.2g-1ubuntu4.15 [1077 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
...
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe i386 gosu i386 1.7-1 [422 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
...
onal disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 u-boot-tools i386 2016.01+dfsg1-2ubuntu5 [107 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 107 kB in 1s (69.7 kB/s)
...
Get:1 http://archive.ubuntu.com/ubuntu xenial/main i386 device-tree-compiler i386 1.4.0+dfsg-2 [361 kB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
...
Step 9/10 : ADD entrypoint.sh /
---> 77d7df73234a
Step 10/10 : ENTRYPOINT ["/entrypoint.sh"]
---> Running in a24dff424ec9
Removing intermediate container a24dff424ec9
---> f9a20e8ce12f
Successfully built f9a20e8ce12f
Successfully tagged build-m350:latest
不過從訊息看來應該只是過程中的 output 出了點狀況
繼續往下走吧
- checkout m350 source code
- checkout develop
- Running the Docker image with volume on m350 source code
- 執行該 container 的 bash
docker exec -it -u user build-m350 bash
- cd 到 volume 所在的 m350 source code
user@06ea8759b639:/$ cd /home/user/ user@06ea8759b639:~$
- 執行
source proenv.sh
user@06ea8759b639:~$ source proenv.sh
- 執行
make
user@06ea8759b639:~$ make Checking 'uuencode'... ok. make[1] world make[2] tools/install make[3] -C tools/patch compile make[3] -C tools/patch install ...
等吧... 希望能順利 build 過啊
1335
偷看到 automake 已經 pass
user@06ea8759b639:~$ make
Checking 'uuencode'... ok.
make[1] world
make[2] tools/install
make[3] -C tools/patch compile
make[3] -C tools/patch install
make[3] -C tools/sed compile
make[3] -C tools/sed install
make[3] -C tools/m4 compile
make[3] -C tools/m4 install
make[3] -C tools/autoconf compile
make[3] -C tools/autoconf install
make[3] -C tools/pkg-config compile
make[3] -C tools/pkg-config install
make[3] -C tools/xz compile
make[3] -C tools/xz install
make[3] -C tools/automake compile
make[3] -C tools/automake install
...
耐心等吧
1350
等待的同時 google 一下以下的錯誤
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
先問第一行就好
debconf: unable to initialize frontend: Dialog
這似乎就是解法了 - 在 Dockerfile 加入以下這一行
ENV DEBIAN_FRONTEND noninteractive
之後有空再試試
1450
今天從家裡出門時忘了把度數較淺一些的眼鏡帶來公司
帶著足夠度數的眼鏡看著電腦螢幕真的覺得很吃力
1540
還再 build... 是好消息
1630
- 執行
make
- 終於成功了
- cd 進入 proscend 目錄
user@06ea8759b639:~$ cd proscend/ user@06ea8759b639:~/proscend$
- make distclean
user@06ea8759b639:~/proscend$ make distclean /bin/bash: line 0: printf: 0x: invalid hex number /bin/bash: line 0: printf: 0x: invalid hex number /bin/bash: line 0: printf: 0x: invalid hex number make -C /home/user/proscend/opensrc distclean ... echo "PROSCEND DISCLEAN" PROSCEND DISCLEAN user@06ea8759b639:~/proscend$
- make menuconfig
- Vendor/Products = GENERIC/0_GENERIC
- make
... make -C iweb make[3]: Entering directory '/home/user/proscend/prosrc/icos/iweb' /home/user/staging_dir/toolchain-arm_cortex-a7_gcc-5.2.0_uClibc-1.0.14_eabi/bin/arm-openwrt-linux-gcc -c -std=c99 -Wall -fPIC -D_XOPEN_SOURCE=600 -D_GNU_SOURCE -fno-stack-protector -I/home/user/proscend/prosrc/icos/include -I/home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/usr/include -I/ home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/usr/include/glib-2.0 -I/home/user/staging_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/usr/include/ libxml2 -I/home/user/staging_dir/host/include -I/home/user/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/linux-4.4.60 -I/home/user/staging_dir/ target-arm_cortex-a7_uClibc-1.0.14_eabi/usr/include/ssdk -DMG_ENABLE_IPV6 -DMG_ENABLE_HTTP_STREAMING_MULTIPART -DMG_ENABLE_SSL -o mongoose.o mongoose.c mongoose.c: In function 'mg_http_serve_file': mongoose.c:7970:19: error: operator '||' has no right operand _XOPEN_SOURCE >= 600 ^ Makefile:29: recipe for target 'mongoose.o' failed make[3]: *** [mongoose.o] Error 1 make[3]: Leaving directory '/home/user/proscend/prosrc/icos/iweb' Makefile:27: recipe for target 'default' failed make[2]: *** [default] Error 2 make[2]: Leaving directory '/home/user/proscend/prosrc/icos' Makefile:25: recipe for target 'icos' failed make[1]: *** [icos] Error 2 make[1]: Leaving directory '/home/user/proscend/prosrc' Makefile:138: recipe for target 'prosrc' failed make: *** [prosrc] Error 2
終於出現我看的懂的錯誤了
1715
終於在 m350 獻出了處女秀
m350[develop] - nomore iweb, so keep the compile flag PROSRC_WEB_CGISESSION unchanged
commit 97f077029a328430508e3d9f333af2e4fa3b4a0f
Refs: [develop], {origin/develop}
Author: jeffrey <[email protected]>
Date: Fri Jan 17 17:14:01 2020 +0800
nomore iweb, so keep the compile flag PROSRC_WEB_CGISESSION unchanged
proscend/mconfig/configs/GENERIC/1_GENERIC_WIFI/defconfig | 2 +-
proscend/prosrc/icos/Makefile | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
image 也 build 出來了
下禮拜再開始玩板子吧