Support #1028

Trouble with compilation on terminal (with publickey on plugstatic?)

Added by Olivier Baudry over 9 years ago. Updated almost 9 years ago.

Status:ClosedStart date:2011-10-26
Priority:NormalDue date:
Assignee:Tim Place% Done:

0%

Category:-
Target version:-
Branch:

Description

Dear all,

I try to compile jamoma and you can see here the result :
UPDATING: Modules/Test
Already up-to-date.
You need to run this command from the toplevel of the working tree.

ruby: No such file or directory -- update.rb (LoadError)


UPDATING: Modules/Plugtastic
update.rb:69:in `chdir': No such file or directory - /Users/olivierbaudry/Jamoma/Tools/../Modules/Plugtastic (Errno::ENOENT)
from update.rb:69:in `doUpdateSimple'
from update.rb:90:in `doUpdate'
from update.rb:166

I try to that below:
MacBook-Pro-de-Olivier-Baudry:~ olivierbaudry$ cd jamoma
MacBook-Pro-de-Olivier-Baudry:jamoma olivierbaudry$ git submodule init
MacBook-Pro-de-Olivier-Baudry:jamoma olivierbaudry$ git submodule update
Cloning into Modules/Plugtastic...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
Clone of ':jamoma/Plugtastic.git' into submodule path 'Modules/Plugtastic' failed
MacBook-Pro-de-Olivier-Baudry:jamoma olivierbaudry$

How to compile correctly Jamoma for Max6 and Max5?

History

#1 Updated by Trond Lossius almost 9 years ago

  • Status changed from New to Closed

Hi Olivier,

Do you still struggle with updating and compiling Jamoma? If so I suggest that you drop a mail to the jamoma-devel mailing list, and we sort it out there, or eventually that one of us try to help you out in a Skype session.

I'm closing this issue, so that we can have the tracker primarily used for bugs and feature requests.

Cheers,
Trond

Also available in: Atom PDF