Can we avoid using symlinks?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Can we avoid using symlinks?

Igor Stasenko
 
Because there is no way to represent them on windows:

tar -xzf cog.tar.gz
tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create
symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file
or directory
tar: Exiting with failure status due to previous errors



--
Best regards,
Igor Stasenko.
Reply | Threaded
Open this post in threaded view
|

Re: Can we avoid using symlinks?

Frank Shearar-3
 
On 9 July 2013 09:55, Igor Stasenko <[hidden email]> wrote:
>
> Because there is no way to represent them on windows:
>
> tar -xzf cog.tar.gz
> tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create
> symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file
> or directory
> tar: Exiting with failure status due to previous errors

Surely you should be using the right tarball for the platform?
cogwin.zip, in this case.

frank

> --
> Best regards,
> Igor Stasenko.
Reply | Threaded
Open this post in threaded view
|

Re: Can we avoid using symlinks?

Igor Stasenko
 
On 9 July 2013 12:39, Frank Shearar <[hidden email]> wrote:

>
> On 9 July 2013 09:55, Igor Stasenko <[hidden email]> wrote:
>>
>> Because there is no way to represent them on windows:
>>
>> tar -xzf cog.tar.gz
>> tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create
>> symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file
>> or directory
>> tar: Exiting with failure status due to previous errors
>
> Surely you should be using the right tarball for the platform?
> cogwin.zip, in this case.
>

That doesn't solves the problem.
The symlink is still there is sources. And that means you cannot
have/use same sources for all platforms.


> frank
>
>> --
>> Best regards,
>> Igor Stasenko.



--
Best regards,
Igor Stasenko.
Reply | Threaded
Open this post in threaded view
|

Re: Can we avoid using symlinks?

EstebanLM

Hi,

AFAIK, we do not use those scripts for build the VM  (ofc, Eliot use them. I mean in the current process with CMakeMaker)
What I'm missing?

Esteban

On Jul 9, 2013, at 1:30 PM, Igor Stasenko <[hidden email]> wrote:

>
> On 9 July 2013 12:39, Frank Shearar <[hidden email]> wrote:
>>
>> On 9 July 2013 09:55, Igor Stasenko <[hidden email]> wrote:
>>>
>>> Because there is no way to represent them on windows:
>>>
>>> tar -xzf cog.tar.gz
>>> tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create
>>> symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file
>>> or directory
>>> tar: Exiting with failure status due to previous errors
>>
>> Surely you should be using the right tarball for the platform?
>> cogwin.zip, in this case.
>>
>
> That doesn't solves the problem.
> The symlink is still there is sources. And that means you cannot
> have/use same sources for all platforms.
>
>
>> frank
>>
>>> --
>>> Best regards,
>>> Igor Stasenko.
>
>
>
> --
> Best regards,
> Igor Stasenko.

Reply | Threaded
Open this post in threaded view
|

Re: Can we avoid using symlinks?

Igor Stasenko
 
On 9 July 2013 23:47, Esteban Lorenzano <[hidden email]> wrote:
>
> Hi,
>
> AFAIK, we do not use those scripts for build the VM  (ofc, Eliot use them. I mean in the current process with CMakeMaker)
> What I'm missing?
>
i don't know, but somehow this symlink got into the sources.


> Esteban
>
> On Jul 9, 2013, at 1:30 PM, Igor Stasenko <[hidden email]> wrote:
>
>>
>> On 9 July 2013 12:39, Frank Shearar <[hidden email]> wrote:
>>>
>>> On 9 July 2013 09:55, Igor Stasenko <[hidden email]> wrote:
>>>>
>>>> Because there is no way to represent them on windows:
>>>>
>>>> tar -xzf cog.tar.gz
>>>> tar: cog/nscogbuild/cygwinbuild/installer/onebuild: Cannot create
>>>> symlink to `/Users/eliot/Newspeak/closurevm/onebuild/': No such file
>>>> or directory
>>>> tar: Exiting with failure status due to previous errors
>>>
>>> Surely you should be using the right tarball for the platform?
>>> cogwin.zip, in this case.
>>>
>>
>> That doesn't solves the problem.
>> The symlink is still there is sources. And that means you cannot
>> have/use same sources for all platforms.
>>
>>
>>> frank
>>>
>>>> --
>>>> Best regards,
>>>> Igor Stasenko.
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>



--
Best regards,
Igor Stasenko.