Yagarto tools - Make 64 bit windows - Error

Since make is independent of the code generation tools, you might simply 
replace it with a 64 bit version of make. There is one available here: 
http://www.equation.com/servlet/equation.cmd?fa=make

An alternative but somewhat heavyweight solution may be to run a 32bit 
version of Windows in a virtual machine on your 64bit platform.

Both VMware Server and Virtual PC are free and will allow you to do 
this. One advantage of a VM is that it provides a consistent and 
standardised virtual platform regardless of the physical hardware and 
drivers installed. Because you can have a virtual network between the VM 
and the host (and the rest of your physical network) accessing files in 
either environment can be seamless.

http://www.microsoft.com/downloads/details.aspx?FamilyID=28C97D22-6EB8-4A09-A7F7-F6C7A1F000B5&displaylang=en

http://www.vmware.com/products/server/

If you do not have a spare Windows license to install on the VM, you can 
use one of the IE compatibility test VHDs for Virtual PC, which are in 
fact time-limited full OS installations. 
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=21eabb90-958f-4b64-b5f1-73d0a413c8ef


Clifford
Guest
I got the same error message, but the solution was plain simple:
Don't install the yagarto into a directory containing spaces (like 
"Program Files(x86)")

On my Win7 64bit machine, installing the toolkit in c:\yagarto\ fixed 
the issues...
XploD wrote:
> I got the same error message, but the solution was plain simple:
> Don't install the yagarto into a directory containing spaces (like
> "Program Files(x86)")

Oh yes; never do that with any GNU tools, especially make.  You may be a 
bit late with the suggestion however; thread necromancy is seldom 
useful.
Guest
Thank you very much!

I have searched longer days.
Now I read this post and my problem is solved!

Thanks.

Helge
Guest
Alternatively, edit the PATH environment variable to use the *short 
names* for the directories where Yagarto is intalled, e.g.:
1
PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\yagarto-tools-20100703\bin;C:\Program Files (x86)\yagarto\bin

becomes:
1
PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\PROGRA~2\YAGART~1\bin;C:\PROGRA~2\yagarto\bin

(Use 'dir /x' in the command shell to check the actual short name of 
each directory, and see 
http://geekswithblogs.net/renso/archive/2009/10/21/how-to-set-the-windows-path-in-windows-7.aspx 
for info on editing the PATH)

-Owen

Reply

A question of your own? This thread is over 17 years old. Ask it in a thread of its own – more people read along there, and it gets answered more often and sooner.

Start a new thread

A fix, an addition or feedback on this thread? Then reply here.

Formatting
  • [c]C-Code[/c]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.