Re: GWorkSpace-> gnustep-make ERROR

[Nicola Pero]

> I've find the  error, it was in gnustep-make, not in gworkspace.
> 
> In  .../GNUstep/System/Makefile/Instance/Shared/bundle.make all copys are 
> make with:
>                                       cp -r
> This have the problem that it can't copy hardlinks and other type of special 
> files, I replace it with:
>                                       cp -R
> And it works!!!!!

Yes - thanks - but ... I'm still confused about how/why you have been able
to got to the point that you have to copy hardlinks in the first place.
:-)

Can you let me know a bit in detail how/why do you get the error ?  I
wasn't able to reproduce it.


> Making all for app GWorkspace...
>  Copying resources into the app wrapper...
> cp: no se crea el enlace duro 
> `GWorkspace.app/Resources/BrowserViewer.viewer/Contents/Resources' al
> directorio `GWorkspace.app/Resources/BrowserViewer.viewer/Resources'

But how did you generate these hardlinks in the first place ?  These
should be symlinks I think.  Maybe your machine doesn't support symlinks ?

I think you're using a ix86/linux-gnu/gnu-gnu-gnu box, so you should have
symlinks ... Btw - you are talking about a hardlink between directories if
I understand correctly ... I can't even create such hardlinks on my linux
box unless I'm root!

Which suggests me the following questions :-)

 - what operating system, platform, shell etc are you using ?

 - are symlinks working on your machine, and if so, are they detected
correctly ? you may check your /usr/GNUstep/System/Makefiles/config.make -
mine says

LN_S = ln -s 

because I've got symlinks working on my machine.  What does yours say ?  


I'm not sure how portable 'cp -R' is, compared to 'cp -r' (which is
definitely portable), so I'd be curious to know a real example in which it
would be definitely useful to have 'cp -R' rather than 'cp -r'.

We can always define CP_R to be 'cp -r' inside config.make, and then you
could override that with make CP_R='cp -R' if it's a very rare problem.

If you have any more comments or light to shed on this problem, I'd be
happy to read about it.

Thanks! :-)