From: "Jasmin J." <jasmin@anw.at>
To: crossgcc@sourceware.org
Subject: Re: Hard link in CT_GetCustom
Date: Wed, 20 Jan 2016 14:36:00 -0000 [thread overview]
Message-ID: <569F9B66.8020103@anw.at> (raw)
In-Reply-To: <569D08B7.8040806@anw.at>
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
prev parent reply other threads:[~2016-01-20 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 15:46 Jasmin J.
2016-01-20 14:36 ` Jasmin J. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569F9B66.8020103@anw.at \
--to=jasmin@anw.at \
--cc=crossgcc@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).