On Wed, Aug 17, 2005, Peter S. Mazinger wrote:
> On Wed, 17 Aug 2005, Matthias Kurz wrote:
>
> > My attempt was, to try to disable the usage of libiconv in gcc. There
> > are already provisions (the echo "am_cv_func_iconv=no" etc >config.cache).
> > This config.cache has to be copied into the dir
On Wed, 17 Aug 2005, Matthias Kurz wrote:
> My attempt was, to try to disable the usage of libiconv in gcc. There
> are already provisions (the echo "am_cv_func_iconv=no" etc >config.cache).
> This config.cache has to be copied into the directories of some sub-
> configures to become effective. Bu
On Tue, Aug 16, 2005, Doug Summers wrote:
> Had to jump through a couple of hoops but I finally got it to compile:
>
> 1) Built empty binutils package
Yes, some packages require binutils. And even when they are only
conditionally required, "openpkg build" eventually installs them.
I think the du
Had to jump through a couple of hoops but I finally got it to compile:
1) Built empty binutils package
2) Added '--with-libiconv-prefix=/usr \' to configure section of gcc.spec
3) Built with openpkg rpm -bb gcc.spec --define="with_binutils no"
--define="l_cc gcc"
___
