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
(Reposting from gcc-help since I didn't get any replies there.)
I have a question about SYSROOT_SUFFIX_SPEC, MULTILIB_OSDIRNAMES, and
multilib cross compilers. I was experimenting with a multilib cross compiler
and was using SYSROOT_SUFFIX_SPEC to specify different sysroots for different
multilib
On 05/04/2010 16:10, Nathan Froyd wrote:
>
> Have you tried configuring with --enable-languages=c? Doing so should
> ensure that libstdc++ is not configured for your target.
I've found it possible to build a c++ compiler with no libstdc (as per other
post). Bare-metal COFF target, no libc; I
On 05/04/2010 15:59, Kofi Doku Atuah wrote:
> Hello, and a pleasant good day to everyone. With no further ado:
:) Actually, that's a fair amount of ado simply to say:
> There's no *need* for a libstdc++ on a vanilla or 'bare metal' build.
This is my idea of "no further ado":
/path/to/gcc/c
On Mon, Apr 05, 2010 at 10:29:07AM -0430, Kofi Doku Atuah wrote:
> The process of building a simply, plain vanilla cross compiler for
> arch-fmt-no_os is really probably overdone. To build, for example, a
> GCC cross compiler for an i586-elf target, the build process requires
> you to have a libc f
Hello, and a pleasant good day to everyone. With no further ado:
The process of building a simply, plain vanilla cross compiler for
arch-fmt-no_os is really probably overdone. To build, for example, a
GCC cross compiler for an i586-elf target, the build process requires
you to have a libc for the
On Thu, Mar 19, 2009 at 8:25 PM, Kai Tietz wrote:
> 2009/3/19 Ozkan Sezer :
>> On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote:
>>> On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote:
I'm a bit amazed that the prototype for VirtualProtect() is known to the
compiler but the definit
2009/3/19 Ozkan Sezer :
> On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote:
>> On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote:
>>> I'm a bit amazed that the prototype for VirtualProtect() is known to the
>>> compiler but the definition of DWORD is not.. In any case, it should be
>>> fixed
Ozkan Sezer wrote:
> On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote:
>> However you are wrong about DWORD definition it has always be defined
>> like this :
>>
>> typedef unsigned long DWORD, *PDWORD, *LPDWORD;
>>
>> at least windows.
>>
>
> A DWORD on windows is an unsigned 32 bit integer, t
On Thu, Mar 19, 2009 at 8:04 PM, Vincent R. wrote:
> On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote:
>> I'm a bit amazed that the prototype for VirtualProtect() is known to the
>> compiler but the definition of DWORD is not.. In any case, it should be
>> fixed easily by changing DWORD into
On Thu, 19 Mar 2009 19:58:13 +0200, Ozkan Sezer wrote:
> I'm a bit amazed that the prototype for VirtualProtect() is known to the
> compiler but the definition of DWORD is not.. In any case, it should be
> fixed easily by changing DWORD into unsigned int which is what a
> DWORD is always defined a
I'm a bit amazed that the prototype for VirtualProtect() is known to the
compiler but the definition of DWORD is not.. In any case, it should be
fixed easily by changing DWORD into unsigned int which is what a
DWORD is always defined as. And PR 39063 is still open anyway.
--
Ozkan
On Thu, Mar 19, 2009 at 7:49 AM, Vincent R. wrote:
> Hi,
>
> I tried to generate a cross-compiler from trunk a few hours ago and I have
> noticed that
> libgcc2.c doesn't compile anymore because of the following function :
It is caused by:
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00822.html
Hi,
I tried to generate a cross-compiler from trunk a few hours ago and I have
noticed that
libgcc2.c doesn't compile anymore because of the following function :
int
mprotect (char *addr, int len, int prot)
{
DWORD np, op;
if (prot == 7)
np = 0x40;
else if (prot == 5)
np = 0x20;
On Tue, 2008-09-02 at 18:29 -0600, Jacob Oursland wrote:
> This seems to be a problem that should be resolvable by getting the
> variables straightened out. Unfortunately, I don't know which variables
> are wrong and what they are set to. Grep isn't really helping me
> either.
It seems you're us
Hello!
I'm trying to get a native Ada compiler working on ARM, but have ran
into a few (primarily Makefile) problems.
Before the problem, a little background: I successfully built a cross
compiler to build Ada programs from my laptop (x86_64) to the target
system (Debian ARMEL). My process was
Hello,
I'm trying to cross compile gcc-4.3 for emdebian.org and i have got
some compilers for some arches but i'm struggling with some other
arches (like powerpc, mips(el), sparc and s390).
Those architectures have separated ABIs for (n)32, 64. The problem i
have is that ../lib64 and ../lib32 are
On Thu, Jan 31, 2008 at 12:46:41PM +, Martin Guy wrote:
> 2008/1/31, Manuel López-Ibáñez <[EMAIL PROTECTED]>:
> > Nonetheless, if someone decided to go through the hassle of collecting
> > tutorials and hints for various cross-compiling configurations in the
> > wi
2008/1/31, Manuel López-Ibáñez <[EMAIL PROTECTED]>:
> Nonetheless, if someone decided to go through the hassle of collecting
> tutorials and hints for various cross-compiling configurations in the
> wiki, I think many users will appreciate it. It is still considered by
> many
er, I am not familiar with
> the GCC internals. Do you have any suggestions on a project related to
> cross-compiling that I could start with? Perhaps cross-compiling for the
> XScale/ARM target?
You can help with the MinGW port to Win64!
https://sourceforge.net/projects/mingw-w64/
Not that
Manuel López-Ibáñez wrote:
On 31/01/2008, Ben Elliston <[EMAIL PROTECTED]> wrote:
Once you get into GCC in enough detail, you'll come to appreciate that
cross-compiling is not particularly special. It's just the compiler
running on a different system type to the code being gene
On 31/01/2008, Ben Elliston <[EMAIL PROTECTED]> wrote:
> Once you get into GCC in enough detail, you'll come to appreciate that
> cross-compiling is not particularly special. It's just the compiler
> running on a different system type to the code being generated. Ther
> It seems like the best place to start for someone new to GCC would be the
> beginners projects off from the GCC Projects webpage
> (http://gcc.gnu.org/projects/beginner.html). I think I will start from there
> and then try to move to the cross-compiling area.
Once you get into G
Thanks for your suggestions.
It seems like the best place to start for someone new to GCC would be the
beginners projects off from the GCC Projects webpage
(http://gcc.gnu.org/projects/beginner.html). I think I will start from there
and then try to move to the cross-compiling area.
Thanks again
t familiar with
> the GCC internals. Do you have any suggestions on a project related to
> cross-compiling that I could start with? Perhaps cross-compiling for the
> XScale/ARM target?
Thanks for your interest.
There are a number of general projects for gcc. Google's Summer of
Code is n
related to
cross-compiling that I could start with? Perhaps cross-compiling for the
XScale/ARM target?
Thank you,
Rodrigo
Hi,
I'd like to use gprmake to cross-compile a mixed language project, but
I don't know how to pass the RTS directory (--RTS=abc) to gprmake.
BTW, where can I find the documentation for gprmake?
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail ha
Don't build *in* the source directory. Use two separate build
directories, one for each target.
At this point, you should run "make distclean" to clean up the source
tree before doing anything else.
On Apr 18, 2006, at 3:13 PM, Ashit Kumar wrote:
Hi,
I tried to cross compile the GCC.I first configured,make and make
install
the binutils and newlibc respectively.Then i compiled the GCC for
sparc-linux machine.It worked fine.
Then i am trying to cross-compile for the arm-none-eabi but i am
Hi,
I tried to cross compile the GCC.I first configured,make and make install
the binutils and newlibc respectively.Then i compiled the GCC for
sparc-linux machine.It worked fine.
Then i am trying to cross-compile for the arm-none-eabi but i am getting
the following error
Configuring in ./libibert
Been so far unsuccessful in doing this, was hoping someone could help.
I tried to emulate our current cross compile method (C to NLM) for Ada
but something doesn't seem to be working. Currently, we cross compile
our C programs using gcc and link everything into an elf32-i386 object
file. Then, we
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
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: elf_i386
collect2: ld returned status 1 exit status.
This error later
On Thu, Jul 28, 2005 at 12:31:05PM -0700, James E Wilson wrote:
> Mark Cuss wrote:
> >[EMAIL PROTECTED] helloworldsun]$ g++ -b sparc-sun-solaris2.9 hello.cxx
> >/cdl/apps/.software/linux/gcc-3.4.4-x86-sparc/lib/gcc/sparc-sun-solaris2.9/3.4.4/../../../../sparc-sun-solaris2.9/bin/ld:
> >
> >values-X
Mark Cuss wrote:
[EMAIL PROTECTED] helloworldsun]$ g++ -b sparc-sun-solaris2.9 hello.cxx
/cdl/apps/.software/linux/gcc-3.4.4-x86-sparc/lib/gcc/sparc-sun-solaris2.9/3.4.4/../../../../sparc-sun-solaris2.9/bin/ld:
values-Xa.o: No such file: No such file or directory
collect2: ld returned 1 exit st
" <[EMAIL PROTECTED]>
To:
Sent: Monday, July 25, 2005 1:04 PM
Subject: Can't find values-Xa.o when cross compiling
Hello All
I've built gcc-3.4.4 as a linux to Solaris (on SPARC) cross compiler. If
I
change my path to include my new compiler executables, I can com
Hello All
I've built gcc-3.4.4 as a linux to Solaris (on SPARC) cross compiler. If I
change my path to include my new compiler executables, I can compile and
link a simple "hello world" program.
However, I want to be able to specify the target architecture and compiler
version number with gcc's
Steven J. Hill wrote:
While I am getting closer to full toolchain build, GCC-4.1.0 is still
not behaving the way it should. Below is the output that I am running
up against. I attempted to define a stack variable to hold the value
of zero and tried using that instead of the actual value, but nothin
> the patch just for the sake of discussion. Does anyone have some
> insight on this? I am using binutils-2.15, glibc-2.3.4, 2.6.12-rc2
> kernel headers and gcc-4.1.0-20050418. Thanks.
>
I'd use 2.16 binutils, especially if using mainline gcc, but that's not
as relevant here...
> /home/sjhill/m
Greetings.
While I am getting closer to full toolchain build, GCC-4.1.0 is still
not behaving the way it should. Below is the output that I am running
up against. I attempted to define a stack variable to hold the value
of zero and tried using that instead of the actual value, but nothing
worked. I
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
Bonjour I own a Mac OS X 10.3.8 loaded with gcc 3.3 on it. Id 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 website and build gcc on Darwin 7.8 with
some options for t
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
Are there any ready to use gcc rpms for,
host:x-86,redhat9.0
target:alpha
thanking you
vivek
__
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
52 matches
Mail list logo
