[gccsdk] Symlink: Unknown file type

Ron beeb at woosh.co.nz
Mon Mar 21 18:07:33 PDT 2011


In message <592453b551.beeb at ron1954.woosh.co.nz>
          Ron <beeb at woosh.co.nz> wrote:

> In message <55b44eb551.Jo at hobbes.bass-software.com>
>           John Tytgat <John.Tytgat at aaug.net> wrote:
> 
> > In message <fa9d1eb551.beeb at ron1954.woosh.co.nz>
> >           Ron <beeb at woosh.co.nz> wrote:
> > 
> > > Changing the filetype of the Symlink file to many unheard of
> > > types and tar does not ignore them.
> > > So I think the error is misleading and tar/unixlib knows what
> > > a Symlink file is, and is taking exception to it.
> > 
> > I'm not familiar with the tar format but I guess that fact that an
> > object is a softlink is stored separately (and not part of a RISC OS
> > filetype or "," based filetype extension).
> > 
> > There is support for symbolic links in UnixLib but I don't know how
> > well.  At least point 2 of
> > <URL:http://www.riscos.info/bugzilla/index.cgi/show_bug.cgi?id=162>
> > is still open.
> > 
> > > Now I have to find if Unixlib is saying 'dont do this'
> > > or if Tar is configured to ignore them.
> > 
> > It would be good if you could further nail down what happens.
> >
 
I have found a setting in unixlib/buildoptions.h that alludes to 
toggling symlink actions on or off.
#define __UNIXLIB_SYMLINKS  1
setting this to 0 did not have any effect though.
Just to be clear, the default seems to be to support Symlinks,
and when Tar does a check on the Symlink it errors with 'filetype
unknown'
It's not a showstopper as the tar -h option stops Symlink following

Ron M.   (Cross compiler 4.1.2)




More information about the gcc mailing list