Troy via Gcc kirjoitti 29.9.2024 klo 6.15:
I've created a Unix-like system, and although it's not very complete
yet, I want to make a cross-compilation chain for it so that I can use
some open source c libraries.
More important would be to see the -v output when you ran the compiler
and got the
Christophe Lyon via Gcc kirjoitti 27.3.2024 klo 10.52:
On 3/26/24 22:52, Joel Sherrill via Gcc wrote:
I am trying --disable-multlibs on the gcc configure and adding
CFLAGS_FOR_TARGET to make.
I would configure GCC with --disable-multilibs --with-cpu=XXX
--with-mode=XXX --with-float=XXX [maybe
Kai Ruottu kirjoitti 1.12.2017 klo 12:02:
Marek kirjoitti 1.12.2017 klo 10:51:
It seems the last error preceeding the "suffix" error is "no include
path in which to search for stdc-predef.h"
I wonder where to find stdc-predef.h or whether it's generated by gcc
during
Marek kirjoitti 1.12.2017 klo 10:51:
It seems the last error preceeding the "suffix" error is "no include
path in which to search for stdc-predef.h"
I wonder where to find stdc-predef.h or whether it's generated by gcc
during compile time.
This file comes with newer glibc versions. For instance
Vitalijus Jefišovas kirjoitti 16.11.2017 klo 18:54:
On Cortex-M mcu’s, when interrupt happens, NVIC copies r0-r3 and couple
other registers onto the psp stack, and then jumps to interrupt routine,
when it finishes, NVIC restores these registers, and jumps back to user’s
function.
What is happenin
R0b0t1 kirjoitti 18.8.2017 klo 19:17:
On Fri, Aug 18, 2017 at 1:09 AM, Freddie Chopin wrote:
On Thu, 2017-08-17 at 22:27 -0500, R0b0t1 wrote:
On Thu, Aug 17, 2017 at 4:44 PM, R0b0t1 wrote:
When compiling libssp, ssp.c, function __guard_setup:
O_RDONLY is undeclared (ssp.c:93:34),
ssize_t is
30.3.2012 19:03, Mao Ito kirjoitti:
I got stuck on a problem.
Actually, I could install "arm-eabi" cross-compiler for c, c++.
The problem is about "arm-eabi-gcj" (i.e. for Java). "arm-elf" version
> cross-compiler was successfully installed for c, c++, Java. But,
> after that, I realized that m
Paul Koning writes:
I'm trying to do a cross-build of gcc 4.5.1.
It's configured --target=mips64el-netbsdelf --enable-languages=c,c++, on an
i686-pc-linux-gnu host.
Can you try sysroot with full mips64el-netbsdelf C library and header
files?
The NetBSD archive maybe haven't them... The st
16.10.2010 14:58, Uros Bizjak kirjoitti:
Trying to use --with-build-sysroot configure option, the build failed
with "error: no include path in which to search for ..." error.
This problem come down to the fact, that -isysroot is ignored when
crosscompiling:
Crosscompiler does not handle -isysr
14.9.2010 11:29, Dennis, CHENG Renquan kirjoitti:
For anyone could succeed compiling gcc-4.6, could you paste a correct
ggc_alloc_cleared_lang_type macro ?
just run this grep command under your build directory,
gcc-4.6-build$ grep -RsInw ggc_alloc_cleared_lang_type gcc/
gcc/gtype-desc.h:2451:#
13.9.2010 10:39, Dennis, CHENG Renquan kirjoitti:
So maybe the Gentoo distro has some problem...
No, I've tried compiling gcc-4.6-20100911 on ubuntu 10.04, the same
problem also happened;
and I also found that macro was defined in a generated header file, in
the gcc build directory;
renq...@
6.9.2010 6:17, Dennis kirjoitti:
I'm using gentoo distribution (including gmp/mpfr/mpc) that could compile
gcc-4.5.0, 4.5.1, and many snapshots correctly, including the recent one
gcc-4.5-20100902,
but when I tried to compile gcc-4.6, any snapshot version, even recent
gcc-4.6-20100904,
it a
22.4.2010 1:35, Andreas Schwab kirjoitti:
Paolo Bonzini writes:
I'm not sure if "nm -g" would work under Linux, since
$ nm -g /usr/lib64/libsqlite3.so
nm: /usr/lib64/libsqlite3.so: no symbols
$ objdump -T /usr/lib64/libsqlite3.so|head -5
The equivalent of "objdump -T" is "nm -D".
Whatev
Jie Zhang wrote:
On 12/28/2009 12:59 PM, Pardis Beikzadeh wrote:
Hi,
Also 'make bootstrap' doesn't work without running configure, so I'm
not sure what the "recommended way" mentioned in the email below
means.
The bootstrap in Jim's reply means, I think, building a minimal (only
C front-end)
徐持恒 wrote:
> These days, I’m trying to build gcc-4.4.2 + binutils-2.20 + gmp + mpfr in
> Msys+MinGW and Cygwin environment.
>
> The builds on both environments are OK, but I cannot run "make check", or
> "make check-gcc".
>
> Finally, I found, that, to run test, you must first install guile, autoge
Dave Korn wrote:
Danny Backx wrote:
On Thu, 2009-07-23 at 10:07 +0100, Dave Korn wrote:
Kai Ruottu wrote :
Comparing the output from some earlier working GCC with the gcc-4.4.0
output would reveal if something was wrong in preparing inputs for
the soft-float routines... Or maybe something
Kai Ruottu wrote:
Rainer Emrich wrote:
I try to build a cross compiler host x86_64-unknown-linux-gnu -> target
hppa64-hp-hpux11.00 using gcc trunk.
I run into the next issue.
/usr/lib/pa20_64/milli.a is tried to be linked directly instead be
searched in the sysroot.
- --with-sysroot=/
Rainer Emrich wrote:
I try to build a cross compiler host x86_64-unknown-linux-gnu -> target
hppa64-hp-hpux11.00 using gcc trunk.
I run into the next issue.
/usr/lib/pa20_64/milli.a is tried to be linked directly instead be searched in
the sysroot.
- --with-sysroot=/opt/tec/setup/sys-root/HP
Paul Koning wrote:
I was looking for GCC 3.3.3 just now, and noticed that it doesn't
exist on the generic GNU FTP server or its mirrors
(ftp://ftp.gnu.org/gnu/gcc for example). 3.3.2 and 3.3.4 are there,
as well as lots of other releases, but 3.3.3 is mysteriously missing.
I looked too and wa
Segher Boessenkool wrote:
The manual explicitly says you need to have target headers. With
all those --disable-XXX and especially --enable-sjlj-exceptions it
all works fine without, though.
If one tries to produce everything in the 'gcc' subdirectory, including
'libgcc',
then headers may be nee
Claudio Scordino wrote:
Kai Ruottu wrote:
Claudio Scordino wrote:
I'm looking for a toolchain capable of compiling floating point
operations for the Maverick Crunch Math engine of Cirrus EP93xx
processors.
Cirrus provides some scripts to build a gcc-3.4 toolchain with such
support
Paul Brook wrote:
How can I get the build scripts to use the precompiled gcc throughout
the build process ?
Short answer is you can't. The newly build gcc is always used to build the
target libraries.
Nice statement but what does this really mean?
Does this for instance mean that: "T
Ian Lance Taylor wrote :
Kai Ruottu <[EMAIL PROTECTED]> writes:
Ok, the traditional "evolutionary" method is to not reinvent the wheel
with the already tested target components but let then be as they are
and produce only the stuff required for the new $host, the GNU
binu
Ferad Zyulkyarov wrote :
To build a GCC corss compiler it would be good to use a specail tool
that is called "crosstool". You may look at the following links:
1. http://kegel.com/crosstool/
2. http://kegel.com/crosstool/current/doc/crosstool-howto.html
Everyone always building the target Linux
Jack Twilley wrote:
When I try to build C++ for xscale-elf, I get this as the last message:
configure: WARNING: No native atomic operations are provided for this
platform.
configure: WARNING: They cannot be faked when thread support is disabled.
configure: WARNING: Thread-safety of certain cla
Rohit Arul Raj wrote:
I am upgrading a cross-compiler from gcc3.4.6 to gcc 4.1.1. i am
getting some errors while trying to build the compiler.
The way in which i am building the compiler is :
$configure --target= --prefix=/usr/crossgcc/ --with-newlib
--disable-libssp
"--target=" "Let's
David Daney kirjoitti:
kernel coder wrote:
hi,
I'm trying to cross compile gcc-4.1.0 for mipsel
platform.Following is the sequence of commands which i'm using
../gcc-4.1.0/configure --target=mipsel --without-headres
--prefix=/home/shahzad/install/ --with-newlib --enable-languages=c
Perhap
Eric Fisher wrote:
/src/gcc-3.2.1/configure --target=mipsel-elf \
--prefix=/gnutools --enable-languages=c,c++ \
--with-gnu-as --with-gnu-ld --with-newlib \
--without-headers --disable-shared --disable-threads
Build and install GCC
make
Wrong command, use 'make all-gcc ; make install-gcc', th
Ranjit Mathew kirjoitti:
If I understand you correctly, you're saying that the
target runtime libraries are already created by the
cross-compiler in Phase 1, so I don't need to rebuild
them again in Phase 2 along with the crossed-native
compiler - I can get by by just building the compiler.
Y
Ranjit Mathew wrote :
It seems that toolchain relocation, especially for
crossed-native builds, seems to be broken in mainline
while it used to work for earlier releases. The situation
seems particularly bad for Windows (MinGW).
In this issue was something I didn't understand Let's ass
Niklaus kirjoitti:
Hi,
Until now i have only build cross toolchains for linux systems.
I guess "for totally self-built Linux-from-scratch" systems, not cross
toolchains for usual Linuces like
RedHats, SuSEs, Fedoras, Ubuntus etc.
Usually i build crossgcc in 2 parts, one is before glibc i
Richard Earnshaw wrote:
Next, I suggest you add --with-cpu=xscale when configuring GCC. You can
then drop the -mcpu=xscale when compiling (this should also give you
better libraries for your system). However, beware that you libraries
will now only run on ARMv5 or later processors.
IMHO usi
Rafael Ávila de Espíndola wrote:
I noticed that in the config.h generated for libiberty has HAVE_DECL_ASPRINTF
defined as 0. This hapens because _GNU_SOURCE is not used when running the
test programs.
Another long-staying bug in the libiberty configure system is that it
claims newlib missing
Jeff Stevens wrote:
I am creating the target tree on my host, so that I
can later transfer it to a USB storage device. I was
going to manually move everything, but only saw one
binary, xgcc. Is that all, or aren't there some other
utilities that go along with it?
The 'cpp', 'cc1*', 'collect2
Jeff Stevens wrote:
.../gcc-3.4.4/configure
--build=`../gcc-3.4.4/config.guess`
--target=powerpc-linux --host=powerpc-linux
--prefix=${PREFIX} --enable-languages=c
and then a make all. The make went fine, and
completed without any errors. However, when I ran
'make install' I got the following
Kai Ruottu wrote:
How one gets the first toolchain made shouldn't have the importance
many people think it has... My opinion (clashing badly with Dan's) is
that the first build has no importance at all, if one knows the basics
for Linux, for compiling and for other newbie-level t
David Daney wrote:
Ian Lance Taylor writes:
> Jonathan Day <[EMAIL PROTECTED]> writes:
> > > My question is simple enough - has anyone built a
> > toolchain for a MIPS64-Linux-GNU target?
> > Yes, I did, last year.
> > But I did it through a tedious iterative process--build the
binutils
Mike Stump wrote:
On Friday, August 26, 2005, at 12:59 AM, Kai Ruottu wrote:
Is there any sane reasons for this on systems which never have had that
non-GNU native 'cc' ?
Consistency. This is only bad if one abhors consistency and
predicability. No?
I understand people c
Dave Korn wrote:
What becomes to Cygwin and MinGW, the same attitude as followed with
Linux, that "producing any apps for Windoze should happen only on
Windoze, or that when one does it on some other host, it still should
happen just like on Windoze!", is totally weird to me.
It seems weir
Mike Stump wrote:
configure --with-headers=/cygwin/usr/include --with-libs=/cygwin/usr/
lib target=i386-pc-cygwin && make && make install
would be an example of how I used to build one up, see the gcc
documentation for details. --with-sysroot or some such might be
another way to to do it
Haren Visavadia wrote:
You missed "The GCC team has been urged to drop
support for SCO Unix from GCC, as a protest against
SCO's irresponsible aggression against free software".
When starting my Unix learnings with SCO Xenix/286,
SCO Xenix/386 and SCO Unix (all some kind of trademarks),
I hav
Kai Ruottu kirjoitti:
Mark Cuss kirjoitti:
So - the question is: How do I do this? Even though LD_LIBRARY_PATH
points to ./ as it's first entry, ldd still looks in /lib first for
ld-linux.so.2. I've tried the rpath option to ld at link time, but
that doesn't work either.
Mark Cuss kirjoitti:
Hello all
I apologize if this is off topic for this list - I wasn't sure exactly
where to ask but I thought this would be a good place to start:
Something for newbies like gcc-help?
I'm trying to get myself a group of libraries that I can distribute with
my program so
zouqiong kirjoitti:
.../../gcc-2.95.3/configure --prefix=/opt/gcc --target=mipsel-linux
--enable-languages=c --disable-checking -enable-shared -v;
This is not true at all
-B=/opt/gcc-2.95//mipsel-linux/bin/
-I=/opt/gcc-2.95//mipsel-linux/include
Because these rows tell that a '--pre
Steven J. Hill kirjoitti:
zouqiong wrote in 15.4.2005 10:16:
> i download the release version of gcc-2.95.3, and binutils 2.15,
> then i did the following things:
> 1. mkdir binutils-build;
> .../../binutils-2.15/configure --prefix=/opt/gcc
> --target=mipsel-linux -v;
> make;make install;
>
>
Jonathan Wilson kirjoitti:
> Neither does Linux - by linking against a recent library you are
> *asking* for a binary that requires that library. If you understand
> that you might understand why everyone is saying you should build on
the
> lowest common denominator of the systems you're targ
Amir Fuhrmann kirjoitti:
1. If I am ONLY interested in the compiler, and do NOT want to build
libraries, what would be the process ??
Be happy with what you already have?
Ok
- 'make all-gcc' builds ONLY GCC
- 'make install-gcc' installs ONLY GCC
The "ONLY GCC" of course means the stuff
James E Wilson kirjoitti:
Amir Fuhrmann wrote:
checking whether byte ordering is bigendian... cross-compiling...
unknown
checking to probe for byte ordering...
/usr/local/powerpc-eabi/bin/ld: warning: cannot find entry symbol
_start; defaulting to 01800074
Looking at libiberty configure, I see i
E. Weddington kirjoitti:
I don't know if the specific combination will work, but one could
always try. At least it's sometimes a better starting point for
building a lot of cross-toolchains.
If building more than 1000 cross-GCCs is already "a lot of", then the
experience got from that says it
is
On 15 Apr 2005 at 14:56, zouq wrote:
> first i download the release the version of gcc-2.95.3, binutils 2.15,
This message should go to the crossgcc list... But it is nowadays
filled with bolsheviks demanding everyone to start from absolute
scratch, so wacky advices expected there :-(
So maybe
In the crossgcc list was a problem with gcc-3.4 generating the opcode
'mfcr' with '-mcpu=power' for the second created multilib, when the
GCC target is 'rs6000-ibm-aix4.3'. The other multilibs produced as
default are for '-pthread', '-mcpu=powerpc' and '-maix64'... The AIX
users could judge if all
51 matches
Mail list logo
