Strange XMake Error

Technical questions regarding the XTC tools and programming with XMOS.
Post Reply
User avatar
GeorgeIoak
Active Member
Posts: 56
Joined: Wed May 19, 2010 9:42 pm

Strange XMake Error

Post by GeorgeIoak »

I'm running:
XDE Version: 11.11.0 (build 2237)

On a Mac OS X v10.7.4

I haven't had this problem before but I recently got some projects mixed up and had to copy some directories so perhaps that has something to do with it.

When I go to build my project I get the following message in the console:

**** Build of configuration XMOS Compiler Collection (xcc) for project app_usb_aud_l1 ****

xmake all
xmake: *** ../module_usb_shared: Is a directory. Stop.

The directory structure looks the same as other projects (different versions of modified USB Audio L1 Projects) so I'm not sure what is causing this error.

Any help would be greatly appreciated!!


User avatar
segher
XCore Expert
Posts: 844
Joined: Sun Jul 11, 2010 1:31 am
Contact:

Post by segher »

Do you perhaps have spaces (or similar nasty characters) in the full
path your source tree is in?
User avatar
GeorgeIoak
Active Member
Posts: 56
Joined: Wed May 19, 2010 9:42 pm

Post by GeorgeIoak »

No, I checked that, it's:

Users\george\workspace\USB_Audio_Int_3.31-iHope

I just looked into the log files and I see the following:

7/4/12 2:33:22.955 PM [0x0-0x37037].org.eclipse.eclipse: Unable to find full path for "g++"

I re-downloaded the XDE but I still see this error and I'm not sure if it's related or something that has always been lurking in the background.
Last edited by GeorgeIoak on Thu Jul 05, 2012 12:23 am, edited 1 time in total.
User avatar
segher
XCore Expert
Posts: 844
Joined: Sun Jul 11, 2010 1:31 am
Contact:

Post by segher »

GeorgeIoak wrote:No, I checked that, it's:

Users\george\workspace\BDG_USB_Audio_Int_3.31-iHope
But forward slashes I hope, right?
I just looked into the log files and I see the following:

7/4/12 2:33:22.955 PM [0x0-0x37037].org.eclipse.eclipse: Unable to find full path for "g++"
I think that is harmless and has nothing to do with your problem.

You could try

Code: Select all

xmake VERBOSE=1
to perhaps get more useful error messages.
User avatar
GeorgeIoak
Active Member
Posts: 56
Joined: Wed May 19, 2010 9:42 pm

Post by GeorgeIoak »

yeah, sorry forward slashes. no luck with the VERBOSE

Code: Select all

bash-3.2$ cd workspace/USB_Audio_Int_3.31-iHope/app_usb_aud_l1/
bash-3.2$ xmake VERBOSE=1
xmake: *** ../module_usb_shared: Is a directory.  Stop.
bash-3.2$ 
Last edited by GeorgeIoak on Thu Jul 05, 2012 12:23 am, edited 1 time in total.
User avatar
segher
XCore Expert
Posts: 844
Joined: Sun Jul 11, 2010 1:31 am
Contact:

Post by segher »

Ah, it seems many XMOS Makefiles override the VERBOSE setting; look
in "app_usb_aud_l1/Makefile", if it sets VERBOSE=0 change it to
VERBOSE=1?

If that doesn't help, I only know of big hammers to debug things
like this (e.g., the "make -n" option), which however aren't easy
to use, certainly not long-distance like this. *Lots* of output, etc.
I'm sure someone else will then show up who knows these Makefiles
better though :-)
User avatar
GeorgeIoak
Active Member
Posts: 56
Joined: Wed May 19, 2010 9:42 pm

Post by GeorgeIoak »

no, unfortunately no verbose setting in the app makefile and make -n just gives the same and only message :(
User avatar
GeorgeIoak
Active Member
Posts: 56
Joined: Wed May 19, 2010 9:42 pm

Post by GeorgeIoak »

Problem Solved!

Dumb error on my part. Seems that when I copied directories I ended up with my edited project as well as the original XMOS project in the same directory.

Kind of a strange error to throw and not much help but at least I'm able to compile again.
User avatar
segher
XCore Expert
Posts: 844
Joined: Sun Jul 11, 2010 1:31 am
Contact:

Post by segher »

Glad you solved it!

Some background on the error... The error comes from your OS,
it's EISDIR, which means you tried to write to a directory as if it was
a file. The error message shows it was make itself that tried to do
that; why, we don't know. It probably ended up with that directory
as a Make target, but how, who knows... If you are very, very brave
you can take a look at Makefile.common and friends. Make sure
you have someone standing by to offer emotional support though! ;-)
Post Reply