Peter Bex peter@xs4all.nl writes:
Thanks guys, for making and testing the patch!
Here's a proper git patch w/ changelog.
Thanks from me, too. Signed off and pushed!
Moritz
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
On Sun, Nov 24, 2013 at 03:46:38PM -0500, John J Foerch wrote:
DG Ward david.w...@zerospace.co.nz writes:
D'Oh! Let's try this again!
Your patch fixed the problem for me.
Thanks guys, for making and testing the patch!
Here's a proper git patch w/ changelog.
Cheers,
Peter
--
DG Ward david.w...@zerospace.co.nz writes:
On 2013-11-23 07:07, Peter Bex wrote:
On Sat, Nov 23, 2013 at 05:39:51AM +1300, DG Ward wrote:
Anyway! I've got a new patch for you to play with. All it does in
comparison to the original defaults.make is that it uses install to
create a directory
* DG Ward david.w...@zerospace.co.nz [131122 07:03]:
Hey guys,
I've been working away on fixing the problem described here:
http://bugs.call-cc.org/ticket/942
The problem only manifests itself when you install via. sudo.
The reason that the issue arose is that no owner was specified for
I agree that setting the user-id explicitly isn't the right way to do
things, so, I spent some more time playing about.
I've found that the problem seemed to be more about the permissions
being set on the directories created during installation rather than the
files that're being installed
On Sat, Nov 23, 2013 at 05:39:51AM +1300, DG Ward wrote:
Anyway! I've got a new patch for you to play with. All it does in
comparison to the original defaults.make is that it uses install to
create a directory and specifies only the permissions to use for that
new directory - 755.
I think
On 2013-11-23 07:07, Peter Bex wrote:
On Sat, Nov 23, 2013 at 05:39:51AM +1300, DG Ward wrote:
Anyway! I've got a new patch for you to play with. All it does in
comparison to the original defaults.make is that it uses install to
create a directory and specifies only the permissions to use for
Hey guys,
I've been working away on fixing the problem described here:
http://bugs.call-cc.org/ticket/942
The problem only manifests itself when you install via. sudo.
The reason that the issue arose is that no owner was specified for the
files being installed. This meant that the owner
