Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Release Notes for CDT 1.2


Yes, I'm using hostname1 for testing where the mount points include /net/hostname2/home on hostname2:/home

And yes, if I create my own symbolic link, the same thing happens.



"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

10/07/2003 04:55 PM
Please respond to cdt-dev

       
        To:        cdt-dev@xxxxxxxxxxx
        cc:        
        Subject:        Re: [cdt-dev] Release Notes for CDT 1.2



>
> This is a multipart message in MIME format.
> --=_alternative 006D9A0285256DB8_=
> Content-Type: text/plain; charset="us-ascii"
>
> Bug 43372 can be reproduced with eclipse 2.1.1 if you call eclipse with a
> -data option having a workspace path with a soft link. The workaround
> would be to specify the workspace as a relative path (which doesn't
> involve a link) or the full path of the actual location.
>
> Eg.    call eclipse as:
> ./eclipse -data /net/medusa/home/twolff/cdt/workspaces/ws1
> instead of
> ./eclipse -data /home/twolff/cdt/workspaces/ws1
>
>

Interesting, are you using automount points(auto_fs) ?

If the automounter when resolving the path is returning
/net/hostname/home/... instead of /home/...

I'm wondering if in automount point,

                IResouce.getLocation().toOSString();

is returning a different value.

Is this visible via the CDT/Debug only ?

So for example if you do

# /tmp/myworkspace
# cd /home/twolff; ln -s /tmp/myworkspace workspace
# eclipse -data /home/twollf/workspace

You may have the same problem,(depending on the OS behaviour
for symbolic links)

>

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev



Back to the top