|
|
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » remote build
remote build [message #19366] |
Fri, 28 November 2008 23:58  |
cocob
Messages: 156 Registered: January 2008
|
Experienced Member |
|
|
I have tried TheIDE remote build functionnality. It's seems to be very nice but on a linux remote host i get these errors.
g++: error trying to exec 'as': execvp: No such file or directory
But as command is on /usr/bin.
Can you help me ?
cocob
|
|
|
|
Re: remote build [message #19412 is a reply to message #19366] |
Mon, 01 December 2008 18:47   |
cocob
Messages: 156 Registered: January 2008
|
Experienced Member |
|
|
Nobody can help me with this ?
g++: error trying to exec 'as': execvp: No such file or directory
For information i'm on Windows VISTA and remote host is debian.
But when i build from an ubuntu OS with the same remote host it works perfectly
[Updated on: Mon, 01 December 2008 18:53] Report message to a moderator
|
|
|
|
Re: remote build [message #19768 is a reply to message #19366] |
Thu, 15 January 2009 22:41   |
cocob
Messages: 156 Registered: January 2008
|
Experienced Member |
|
|
I think the problem come from StartProcess (on TServ package) wich does not use environnement pointer. On this host gcc will not work if environnement variables (LD_LIBRARY_PATH for example) are not defined correctly.
Please help me to modify the call to StartProcess() to transfert environnement variables.
Thanks for your help
[Updated on: Thu, 15 January 2009 22:59] Report message to a moderator
|
|
|
|
Re: remote build [message #21943 is a reply to message #21890] |
Thu, 11 June 2009 22:44  |
rylek
Messages: 79 Registered: November 2005
|
Member |
|
|
Hi there!
Thanks for locating and fixing the problem with assembler invocation. As concerns -L, I'm not sure I understand your meaning. Is the problem caused by the remote build omitting the library path specifications, or by the physical library files residing on the local host instead of the remote host? It should be possible to fix the omitted library paths but it doesn't seem to me a very good idea to transfer physical library files between the hosts during the build process. The libraries being built on-the-fly during the build appear and remain on the remote host and I see no reason to install third-party libraries on the local host at all (as they belong to the remote host environment). I still have a feeling I'm missing something there, could you please explain the last problem to me in greater detail?
Regards
Tomas
|
|
|
Goto Forum:
Current Time: Mon Apr 28 00:57:40 CEST 2025
Total time taken to generate the page: 0.00795 seconds
|
|
|