Hard link in CT_GetCustom

Jasmin J. jasmin@anw.at
Wed Jan 20 14:36:00 GMT 2016


Ping

On 18/01/16 23:45, Jasmin J. wrote:
> Hi!
> 
> I am currently using a Laptop with a small SSD, so I ran CT-NG on a USB 3.0
> HDD. To be more precise, I am using SymLinks for some directories.
> I discovered a problem in CT_GetCustom() for my custom source directories.
> There is this line:
>   CT_DoExecLog DEBUG cp -al "${component_location}" \
>             "${CT_SRC_DIR}/${component_name}-${component_version}"
> It does not work in my setup, because the src and build directories are on
> different drives. Is there any good reason why a hard link (-al) is used?
> I changed it to a sym-link (-as) and this works also.
> If it is OK to use the sym-link, I will provide a patch.
> 
> BR
>    Jasmin
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq



More information about the crossgcc mailing list