# Tar: cannot hard link to 'crosstool-ng-1.24.0.tar.bz2'

**URL:** <https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385>\
**Category:** Support\
**Created:** [June 26, 2022, 9:48am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385 "2022-06-26T09:48:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![saeed123](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/saeed123/32/5837_2.png) [@saeed123](https://discuss.pynq.io/u/saeed123)\
**Post date:** [June 26, 2022, 9:48am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/1 "2022-06-26T09:48:59Z")

</div>

![Capture](https://us1.discourse-cdn.com/flex019/uploads/pynq1/original/2X/0/066d94c955ffc59b407e620d34fc261ddf33e126.png)  
Hi dear friends, I installed UBUNTU v 2018 with vagrant file , when I run setup\_host.sh, process is encounterd with error. How can I fix this problem

---

<div class="post-metadata">

**Author:** ![atopet](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@atopet](https://discuss.pynq.io/u/atopet)\
**Post date:** [June 27, 2022, 7:27pm UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/2 "2022-06-27T19:27:42Z")

</div>

Hi,

Set up passwordless permission on your ubuntu for the period of this installation

---

<div class="post-metadata">

**Author:** ![rpp](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/rpp/32/4457_2.png) [@rpp](https://discuss.pynq.io/u/rpp)\
**Post date:** [March 29, 2023, 5:42pm UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/3 "2023-03-29T17:42:27Z")

</div>

I ran into same situation. How to setup passwordless permission.

---

<div class="post-metadata">

**Author:** ![briansune](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/briansune/32/3087_2.png) [@briansune](https://discuss.pynq.io/u/briansune)\
**Post date:** [March 30, 2023, 6:59am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/4 "2023-03-30T06:59:35Z")

</div>

@rpp

Before running setup script, change PYNQ GIT repository to all right

> chmod 777 -R ./PYNQ/\*  
> There is a setup script in the PYNQ, use that to setup environment.

Step 13 should help you out quick =]

Reference:

> [@Stuck at extract yocoto](https://discuss.pynq.io/t/stuck-at-extract-yocoto/4134/8):
>
> Unless people having hard time on setting up the environment: Vagrant is not a good method to setup the SD build environment. I have not investigate to the bottom but what previous engineer shows there might Virtual R/W issue during such setup. STEPS: I will suggest download 18.04.06 LTS Ubuntu from official website Create a virtual disk size about 200GB or more, set the CPU \>#4, RAM \>#8192 Update Ubuntu packages before setting up the PYNQ 3b) Git clone the PYNQ to /home//PYNQ 3c) sudo ch…

ENJOY~

---

<div class="post-metadata">

**Author:** ![Reza\_Mashayekhi](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/reza_mashayekhi/32/5664_2.png) [@Reza\_Mashayekhi](https://discuss.pynq.io/u/Reza_Mashayekhi)\
**Post date:** [March 3, 2024, 6:16am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/5 "2024-03-03T06:16:13Z")

</div>

Didn’t work for me.  
After using this script:

```auto
chmod 777 -R ./PYNQ/*

```

I get this errors:

```auto
chmod: changing permissions of './pynq/lib/_pynq/_video/bsp/gpio': No such file or directory
chmod: changing permissions of './pynq/lib/_pynq/_video/bsp/vtc': No such file or directory

```

and this error still remains:

```auto
Tar: cannot hard link to ‘crosstool-ng-1.24.0.tar.bz2’

```

---

<div class="post-metadata">

**Author:** ![briansune](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/briansune/32/3087_2.png) [@briansune](https://discuss.pynq.io/u/briansune)\
**Post date:** [April 3, 2024, 4:24am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/6 "2024-04-03T04:24:33Z")

</div>

@Reza_Mashayekhi

BTW did you use “sudo” when changing the right?

I will suggest check alignment between the Vivado and the Ubuntu and the toolchain version. Too little info

---

<div class="post-metadata">

**Author:** ![Reza\_Mashayekhi](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/reza_mashayekhi/32/5664_2.png) [@Reza\_Mashayekhi](https://discuss.pynq.io/u/Reza_Mashayekhi)\
**Post date:** [April 3, 2024, 1:55pm UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/7 "2024-04-03T13:55:54Z")

</div>

My problem was solved by changing PYNQ directory.  
I was using virtual machine to run Ubuntu.  
PYNQ folder was inside `/mnt` which was sharing with Window.  
By changing PYNQ directory to `/home`, problem was solved.

---

<div class="post-metadata">

**Author:** ![briansune](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/briansune/32/3087_2.png) [@briansune](https://discuss.pynq.io/u/briansune)\
**Post date:** [April 14, 2024, 1:01am UTC](https://discuss.pynq.io/t/tar-cannot-hard-link-to-crosstool-ng-1-24-0-tar-bz2/4385/8 "2024-04-14T01:01:39Z")

</div>

@Reza_Mashayekhi

I guess you did not read the previous reference:

> [@Stuck at extract yocoto](https://discuss.pynq.io/t/stuck-at-extract-yocoto/4134/8):
>
> Unless people having hard time on setting up the environment: Vagrant is not a good method to setup the SD build environment. I have not investigate to the bottom but what previous engineer shows there might Virtual R/W issue during such setup. STEPS: I will suggest download 18.04.06 LTS Ubuntu from official website Create a virtual disk size about 200GB or more, set the CPU \>#4, RAM \>#8192 Update Ubuntu packages before setting up the PYNQ 3b) Git clone the PYNQ to /home//PYNQ 3c) sudo ch…

The setup guide is very clear and mentioned @ 3A step  
STEPS:

1. I will suggest download 18.04.06 LTS Ubuntu from official website
2. Create a virtual disk size about 200GB or more, set the CPU \>#4, RAM \>#8192
3. Update Ubuntu packages before setting up the PYNQ  
3b) Git clone the PYNQ to /home//PYNQ \<------  
3c) sudo chmod -R 777 ./PYNQ/\*

So i guess the issue had resolved.

ENJOY~
