Hi David

just enable that option in config.full_system:
        http://qi-hw.com/p/openwrt-xburst/68914e0

now I am start a fresh build.

On 01/17/2011 07:46 AM, David Kuehling wrote:
>>>>>> "David" == David Kuehling <[email protected]> writes:
> 
>>>>>> "Wolfgang" == Wolfgang Spraul <[email protected]> writes:
> 
>>> David, I tried to build config.full_system, but ran into this
>>> libgfortran problem:
> 
>>> cp -fpR
>>> /home/wolfgang/fullsys/staging_dir/toolchain-mipsel_gcc-4.3.3+cs_uClibc-0.9.30.1/usr/lib/libgfortran.so.*
>>> /home/wolfgang/fullsys/build_dir/linux-xburst_qi_lb60/base-files/ipkg-xburst/libgfortran/usr/lib/
>>> cp: cannot stat
>>> `/home/wolfgang/fullsys/staging_dir/toolchain-mipsel_gcc-4.3.3+cs_uClibc-0.9.30.1/usr/lib/libgfortran.so.*':
>>> No such file or directory
> 
>> Yeah, I hit that once, too.  For libgfortran to build you need to set
> 
>> CONFIG_INSTALL_GFORTRAN=y
> 
> Had a look at the openwrt-xburst changelog.  This change:
> 
>   
> http://projects.qi-hardware.com/index.php/p/openwrt-xburst/source/commit/ca0b6e7b94a3e47c1652143d1163a481a59fe57d/
> 
> by Xiangfu enabled Octave and libgfortran building without setting the 
> CONFIG_INSTALL_GFORTRAN toolchain option, thereby breaking compilation.
> 
> I would have tried to auto-set the option as a libgfortran dependency,
> but it looks like the openwrt build system is not capable of such a
> thing (i.e. it only handles package<->package dependencies not
> package<->option dependencies).
> 
> cheers,
> 
> David
> 
> 
> 
> _______________________________________________
> Qi Hardware Discussion List
> Mail to list (members only): [email protected]
> Subscribe or Unsubscribe: 
> http://lists.en.qi-hardware.com/mailman/listinfo/discussion


-- 
Best Regards
Xiangfu
-- Qi RSS feed, http://en.qi-hardware.com/feed/rss20.xml --

_______________________________________________
Qi Hardware Discussion List
Mail to list (members only): [email protected]
Subscribe or Unsubscribe: 
http://lists.en.qi-hardware.com/mailman/listinfo/discussion

Reply via email to