Re: [gentoo-dev] some portage related issues

[Mike Frysinger]

On Tuesday 20 April 2004 01:14 pm, Dan Podeanu wrote:
> 1. Kernel compilation and gcc
>
> The recommended gcc version for kernel compile is gcc 2.95.3. Using emerge
> to get any of the supported kernel packages should have a dependency set on
> 2.95.3 and a message informing the users to use gcc-config to change the
> gcc version while compiling the kernel (great tool gcc-config, btw.)

theres no way this is ever going to happen, end of story.
you want gcc-2.x on your system for some reason, emerge it.

> 2. Compiling gcc 2.95.3 with MAKEOPTS="-j5" (on 4 cpu platforms)
> /etc/make.conf fails. However, without using MAKEOPTS gcc compiles fine. My
> guess is that gcc simply doesn't like -jX where X is greater than 1, and
> should not use it, accordingly.

file a bug

> 3. unixODBC and qt
>
> While bulding a new server from scratch (clean install, from stage1) and
> using USE="odbc X", 'emerge unixODBC' fails to compile qt (its marked as a
> depdendency) as the qt compilation tries to include sql/sqltypes.h that
> will consequently be installed at the end of 'emerge unixODBC' (hence,
> things are circular). To workaround it, USE="-odbc X", compile unixODBC,
> USE="odbc X", recompile qt (that was built part of unixODBC compile).

file a bug

> 4. It would be really nice if we had a tool to automate the detection of
> the build architecture (CHOST, -march & -mcpu) based on the info from
> /proc/cpu to help the newbie with the installation procedure.

considering the *large* number of /proc/cpuinfo and the fact that one set does 
not map properly onto the other set, this is impossible to a degree 
(-march/-mcpu)

in terms of CHOST, simply picking the right stage tarball would be enough ... 
most people shouldnt have to change it
-mike

--
gentoo-dev@g.o mailing list