# Makefile ends at check\_mounts.sh

**URL:** <https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497>\
**Category:** Support\
**Created:** [July 15, 2020, 2:18pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497 "2020-07-15T14:18:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Reedom](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/reedom/32/966_2.png) [@Reedom](https://discuss.pynq.io/u/Reedom)\
**Post date:** [July 15, 2020, 2:18pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/1 "2020-07-15T14:18:43Z")

</div>

**PYNQ v2.4**  
**Xilinx Tools 2018.3**  
**Ubuntu 16.04 Xenial**

Hi,

I am running the makefile to build my project;however, the build process ends after check\_mounts.sh. I made sure to source my settings for Vivado, SDK and Petalinux before running the make file and turned off petalinux webtalk option.

**This is my output when I run the makefile:**  
vagrant@ubuntu-xenial:/sdbuild/pynq-git/sdbuild$ make BOARDDIR=/sdbuild/pynq-git/sdbuild/boards/ZCU102  
which vivado | fgrep 2018.3  
/sdbuild/Vivado/2018.3/bin/vivado  
which petalinux-config | fgrep 2018.3  
/sdbuild/Petalinux/2018.3/tools/common/petalinux/bin/petalinux-config  
which arm-linux-gnueabihf-gcc  
/sdbuild/Petalinux/2018.3/tools/linux-i386/gcc-arm-linux-gnueabi/bin/arm-linux-gnueabihf-gcc  
which microblaze-xilinx-elf-gcc  
/sdbuild/Petalinux/2018.3/tools/linux-i386/microblaze-xilinx-elf/bin/microblaze-xilinx-elf-gcc  
which ct-ng  
/opt/crosstool-ng/bin/ct-ng  
which python | fgrep /usr/bin/python  
/usr/bin/python  
sudo -n mount \> /dev/null  
bash /sdbuild/pynq-git/sdbuild/scripts/check\_Env.sh  
bash /sdbuild/pynq-git/sdbuild/scripts/check\_mounts.sh

I read into \*\* PeterOgden’s\*\* answer in this thread: [Issues: Quick Porting of PYNQ using Pre-built Images - #3 by AWoLnik](https://discuss.pynq.io/t/issues-quick-porting-of-pynq-using-pre-built-images/1119/3) and tried to debug it .

When I run `mount | grep build` the output I get is:  
vagrant@ubuntu-xenial:/sdbuild/pynq-git/sdbuild$ mount | grep build  
/dev/sdc1 on /sdbuild type xfs (rw,noatime,attr2,nobarrier,inode64,noquota)

I tried to unmount that file & delete the image file according to his instructions, but was unable to. This was my output when I tried to:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/pynq1/original/2X/1/16d7dbc1aaf0338fdac0d7302dca5b2d0597953c.png)

I ran the make command again with the -n and -d option, to get more info on why the makefile wasn’t working.

This is my make output with the -n option:  
vagrant@ubuntu-xenial:/sdbuild/pynq-git/sdbuild$ make -n BOARDDIR=/sdbuild/pynq-git/sdbuild/boards/ZCU102  
which vivado | fgrep 2018.3  
which petalinux-config | fgrep 2018.3  
which arm-linux-gnueabihf-gcc  
which microblaze-xilinx-elf-gcc  
which ct-ng  
which python | fgrep /usr/bin/python  
sudo -n mount \> /dev/null  
bash /sdbuild/pynq-git/sdbuild/scripts/check\_Env.sh  
bash /sdbuild/pynq-git/sdbuild/scripts/check\_mounts.sh

This is my output with the -d option:  
[Make -d option output.txt](https://discuss.pynq.io/uploads/short-url/yCaczPcVFiKQHrmQnROy8zQxgu.txt) (161.7 KB)

^The output of this file was huge, so I put it in a txt file. Let me know if you want it in a different format.  
I would appreciate it if you could tell me why my build is being stopped by the check\_mount.sh script.

---

<div class="post-metadata">

**Author:** ![PeterOgden](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/peterogden/32/55_2.png) [@PeterOgden](https://discuss.pynq.io/u/PeterOgden)\
**Post date:** [July 15, 2020, 4:17pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/2 "2020-07-15T16:17:34Z")

</div>

This looks like our checking script is being a be over-zealous. It checks to see if any sdbuild folder is mounted which in your case is picking up the /sdbuild folder you’re using a work directory. For now you should just be able to comment out the check or change the grep to search for `PYNQ/sdbuild` more specifically

Peter

---

<div class="post-metadata">

**Author:** ![Reedom](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/reedom/32/966_2.png) [@Reedom](https://discuss.pynq.io/u/Reedom)\
**Post date:** [July 15, 2020, 8:13pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/4 "2020-07-15T20:13:39Z")

</div>

Seems like commenting out the check fixed it!  
Thanks!

Quick Question tho: Will commenting out the check\_mount.sh script cause an error when I want to build another new PYNQ image?

---

<div class="post-metadata">

**Author:** ![yss9701](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/yss9701/32/1537_2.png) [@yss9701](https://discuss.pynq.io/u/yss9701)\
**Post date:** [November 17, 2020, 1:22pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/5 "2020-11-17T13:22:25Z")

</div>

Excuse me, how to comment out the check? I do like this, but it has no effect.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/pynq1/original/2X/2/20a98518e98d748439e1ceb6e0fe90472b0378f9.png)  
The output like this, and I run " mount | grep build ", it has no output.  
 ![image](https://us1.discourse-cdn.com/flex019/uploads/pynq1/original/2X/7/7531a35a56f976cfa8fa9b57bb541b00680dbaf2.png)

---

<div class="post-metadata">

**Author:** ![PeterOgden](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/peterogden/32/55_2.png) [@PeterOgden](https://discuss.pynq.io/u/PeterOgden)\
**Post date:** [November 17, 2020, 2:26pm UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/6 "2020-11-17T14:26:47Z")

</div>

The Makefile is ending because it doesn’t think there is anything to do. What’s the structure of your board repository?

Peter

---

<div class="post-metadata">

**Author:** ![yss9701](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/yss9701/32/1537_2.png) [@yss9701](https://discuss.pynq.io/u/yss9701)\
**Post date:** [November 18, 2020, 9:26am UTC](https://discuss.pynq.io/t/makefile-ends-at-check-mounts-sh/1497/7 "2020-11-18T09:26:34Z")

</div>

Thank you very much. I have solve the problem. The problem is that the soft link is not configured well.  
But now I want to update my ultra96v2 board to support dpu-pynq. I have update the image, but when I run “pip3 install pynq-dpu”, the process of install was stuck in one place for more than 30 minutes. Is it normal ?  
 ![image](https://us1.discourse-cdn.com/flex019/uploads/pynq1/original/2X/b/b53b93aa7bc191b1dc60ee08e321e86e5b67367a.png)
