yes i know i can call it gcc34 but the real problem is that the toolchain has
some scripts to automate the building and it uses some paths to pick up the
appropriate tools and when i run the scripts gcc42 is used. I figure out
that the path that gcc42 is located is the same as gcc34
On Thu, 28 Jan 2010 00:14:14 -0800 (PST) at
gfot giorgo...@yahoo.gr wrote:
yes i know i can call it gcc34 but the real problem is that the toolchain has
some scripts to automate the building and it uses some paths to pick up the
appropriate tools and when i run the scripts gcc42 is used. I
gfot wrote:
...
yes i know i can call it gcc34 but the real problem is that the toolchain has
some scripts to automate the building and it uses some paths to pick up the
appropriate tools and when i run the scripts gcc42 is used. I figure out
that the path that gcc42 is located is the same as
Hi i'm trying to compile a toochain for mips and i'm having some problems
with gcc 4.2.1 that my Freebsd 8.0 (64-bit) system came with. So i decided
(it was proposed by the README of the toolchain) to use gcc 3.4 but i
installed gcc 3.4 from ports but i still use the 4.2 when i type gcc. How
can
On Wed, 27 Jan 2010 16:35:02 -0800 (PST)
gfot giorgo...@yahoo.gr wrote:
Hi i'm trying to compile a toochain for mips and i'm having some
problems with gcc 4.2.1 that my Freebsd 8.0 (64-bit) system came
with. So i decided (it was proposed by the README of the toolchain)
to use gcc 3.4 but i
