On Mon, 2015-01-12 at 20:58 +, Joseph Myers wrote:
> On Mon, 12 Jan 2015, Matthew Fortune wrote:
>
> > MIPS does this too for mips64-linux-gnu as it has n32 for the default
> > multilib which gets placed in lib32. I don't honestly know how the multilib
> > spec doesn't end up building 4 multil
On Mon, 12 Jan 2015, Matthew Fortune wrote:
> MIPS does this too for mips64-linux-gnu as it has n32 for the default
> multilib which gets placed in lib32. I don't honestly know how the multilib
> spec doesn't end up building 4 multilibs though. I'm assuming the fact
> that the default ABI is added
> On Mon, 12 Jan 2015, Steve Ellcey wrote:
>
> > MULTILIB_OSDIRNAMES += mips32r2=mipsr2/lib MULTILIB_OSDIRNAMES +=
> > .=mipsr2/lib
> >
> > I don't think the first one would work because -mips32r2 is the
> > default architecture and is not explicitly listed in MULTILIB_OPTIONS
> > and I don't thin
On Mon, 12 Jan 2015, Steve Ellcey wrote:
> MULTILIB_OSDIRNAMES += mips32r2=mipsr2/lib
> MULTILIB_OSDIRNAMES += .=mipsr2/lib
>
> I don't think the first one would work because -mips32r2 is the default
> architecture and is not explicitly listed in MULTILIB_OPTIONS and I
> don't think the second fo
On Thu, 2015-01-08 at 22:12 +, Joseph Myers wrote:
> On Thu, 8 Jan 2015, Steve Ellcey wrote:
>
> > So I set these macros and SPECs:
> > # m32 and be are defaults
> > MULTILIB_OPTIONS = m64 mel # In makefile fragment
> > MULTILIB_DIRNAMES = 64 el #
On Thu, 8 Jan 2015, Steve Ellcey wrote:
> So I set these macros and SPECs:
> # m32 and be are defaults
> MULTILIB_OPTIONS = m64 mel # In makefile fragment
> MULTILIB_DIRNAMES = 64 el # In makefile fragment
> MULTILIB_OSDIRNAMES = m64=../lib
Problem is solved. It was a problem in my configuration of
GCC.
Leif Ekblad
Here is the output from the same compile in the
/usr/src/toolchain/gcc-4.1-20051008/host-i686-pc-linux-gnu/gcc/ directory:
./xgcc -B/usr/src/toolchain/gcc-4.1-20051008/host-i686-pc-linux-gnu/gcc/ -B/
usr/local/rdos/bin/ -B/usr/local/rdos/lib/ -isystem
/usr/local/rdos/include -isystem /usr/local/rd
I rerun the compiler with -v option. This is the output:
./xgcc -B/usr/src/toolchain/gcc-4.2-20060107/host-i686-pc-linux-gnu/gcc/ -B/
usr/local/rdos/bin/ -B/usr/local/rdos/lib/ -isystem
/usr/local/rdos/include -isystem /usr/local/rdos/sys-include -o conftest
conftest.c -v
Reading specs from
/usr/s
On Wed, Jan 11, 2006 at 12:10:32PM +0100, Leif Ekblad wrote:
> In configure script, line 2580, there is a link test which checks if
> an executable can be generated. The config.log file emits the
> following errors:
>
> /usr/local/bin/rdos-ld: unrecognised emulation mode: -o
> Supported emulations
On Apr 4, 2005, at 11:13 AM, François Mainguy wrote:
Bonjour – I own a Mac OS X 10.3.8 loaded with gcc 3.3 on it. I’d like
to add a gcc target so that I can also cross-compile for PowerPC 405
core CPU (as featured in a Xilinx Virtex-2 Pro FPGA). I know I
need to
download something from GCC webs
vivek sukumaran <[EMAIL PROTECTED]> wrote:
Are there any ready to use gcc rpms for,
host:x-86,redhat9.0
target:alpha
The right mailing list to ask is the one at
http://sources.redhat.com/ml/crossgcc/
When you do post there, be sure to mention what OS
the target will be running.
If the target i
12 matches
Mail list logo
