Project Home
Project Home		 Source Code
Source Code		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Core Development Tools/Discussion/General/i.MX31 build image won't build after installation of Trinity M4/List of Posts
Forum Topic - i.MX31 build image won't build after installation of Trinity M4: (4 Items)
   
Update
Ken Schumm
03/04/2008 6:37 PM
post5503
i.MX31 build image won't build after installation of Trinity M4   
Win32 host, I installed the latest Trinity build per instructions.

The i.MX31 BSP was rebuilt with minor problems (struct _sync_attr field names changed with addition of leading 
underscores which broke the i.mx31_devn-crys8900 driver, easily fixed).

However, now when trying to build the image an error is generated in the IDE that says "Unable to build path to mkifs.
exe". In the base directory c:\qnx630\host\win32\x86\usr\bin is a shortcut mkifs which seems to properly point to c:\
qnx630\host\win32\x86\usr\bin\mkxfs.exe which is a valid executable.

So, what is this obscure error trying to tell me? The build console output only says this:

Building Image: bsp-freescale_i.mx31
Build Failed.

The error in the Problems tab says this:

Unable to build path to mkifs.exe

The errors are less than helpful.
TIA
Ken Schumm
03/05/2008 11:10 AM
post5526
Re: i.MX31 build image won't build after installation of Trinity M4   
It turns out I'm not sure if this is related to the Trinity M4 build or the 6.7 GDB release, because both of those were 
installed on a previously working development environment, but the problem is apparently with the windows shortcuts that
 were created.

After installing both packages the mkifs.exe file was a shortcut to mkxfs.exe. That shortcut was not resolving. It 
looked correct, but deleting it and creating a new shortcut also failed. Deleting the shortcut and copying mkxfs.exe to 
mkifs.exe fixed the problem.

It appears that the mkefs.exe and mketfs.exe are also shortcuts to mkxfs.exe and those will probably fail too. I'm not 
sure why they fail, the shortcut paths seem to be absolutely correct, but they do.
Aleksandar Ristovski(deleted)
03/05/2008 11:15 AM
post5528
RE: i.MX31 build image won't build after installation of Trinity M4   
 

> -----Original Message-----
> From: Ken Schumm [mailto:kwschumm@qsolv.com] 
> Sent: Wednesday, March 05, 2008 11:11 AM
> To: general-toolchain
> Subject: Re: i.MX31 build image won't build after 
> installation of Trinity M4
> 
> It turns out I'm not sure if this is related to the Trinity 
> M4 build or the 6.7 GDB release, because both of those were 

It is highly unlikely it has to do with gdb 6.7 release, if you look in the
archived file you downloaded, you will see only gdb executables.

> installed on a previously working development environment, 
> but the problem is apparently with the windows shortcuts that 
> were created.
> 
> After installing both packages the mkifs.exe file was a 
> shortcut to mkxfs.exe. That shortcut was not resolving. It 
> looked correct, but deleting it and creating a new shortcut 
> also failed. Deleting the shortcut and copying mkxfs.exe to 
> mkifs.exe fixed the problem.
> 
> It appears that the mkefs.exe and mketfs.exe are also 
> shortcuts to mkxfs.exe and those will probably fail too. I'm 
> not sure why they fail, the shortcut paths seem to be 
> absolutely correct, but they do.
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post5526
>
Ken Schumm
03/05/2008 12:29 PM
post5537
Re: RE: i.MX31 build image won't build after installation of Trinity   
>  
> 
> > -----Original Message-----
> > From: Ken Schumm [mailto:kwschumm@qsolv.com] 
> > Sent: Wednesday, March 05, 2008 11:11 AM
> > To: general-toolchain
> > Subject: Re: i.MX31 build image won't build after 
> > installation of Trinity M4
> > 
> > It turns out I'm not sure if this is related to the Trinity 
> > M4 build or the 6.7 GDB release, because both of those were 
> 
> It is highly unlikely it has to do with gdb 6.7 release, if you look in the
> archived file you downloaded, you will see only gdb executables.

OK, I stand corrected. Both packages were installed without building the image in between so it wasn't clear exactly 
when the problem appeared.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems