Problems cross-compiling imagemagick with mingw32

I am trying to cross-compile imagemagick dlls for Windows with mingw32.
I installed the mingw32 package and ran
./configure --host=i486-mingw32 --with-perl=no --enable-static=no
The output shows something like this:
JPEG v1 --with-jpeg=yes no (failed tests)
JPEG-2000 --with-jp2=yes no (failed tests)
LCMS v1 --with-lcms=yes no (failed tests)
LCMS v2 --with-lcms2=yes no
LQR --with-lqr=yes no
Magick++ --with-magick-plus-plus=yes yes
OpenEXR --with-openexr=yes no
PERL --with-perl=no no
PNG --with-png=yes no (failed tests)
RSVG --with-rsvg=yes yes
TIFF --with-tiff=yes no (failed tests)
In config.log the test failures are shown as follows:
configure:27841: checking for jpeg_read_header in -ljpeg
configure:27866: i486-mingw32-gcc -std=gnu99 -std=gnu99 -o conftest.exe -g -O2 -Wall -I/usr/include/freetype2 -D_DLL -D_MT -I/usr/include -L/usr/lib conftest.c -ljpeg -lX11 -lm >&5
/usr/lib/gcc/i486-mingw32/4.5.0/../../../../i486-mingw32/bin/ld: cannot find -lX11
collect2: ld returned 1 exit status
The compiler/linker configuration looks correct to me:
X11 Configuration:
X_CFLAGS = -I/usr/include
X_PRE_LIBS =
X_LIBS = -L/usr/lib
X_EXTRA_LIBS =
Options used to compile and link:
PREFIX = /usr/local
EXEC-PREFIX = /usr/local
VERSION = 6.6.4
CC = i486-mingw32-gcc -std=gnu99 -std=gnu99
CFLAGS = -g -O2 -Wall
CPPFLAGS = -I/usr/local/include/ImageMagick -D_DLL -D_MT
PCFLAGS = -D_DLL -D_MT
DEFS = -DHAVE_CONFIG_H
LDFLAGS = -L/usr/lib
MAGICK_LDFLAGS = -L/usr/local/lib -L/usr/lib
LIBS = -lMagickCore -lfontconfig -lX11 -pthread -lrsvg-2 -lm -lgdk_pixbuf-2.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lgdi32 -lm
CXX = i486-mingw32-g++
CXXFLAGS = -g -O2
FEATURES =
Why can't it find the X11 library?

Similar Messages

Problem cross compiling from x86_64 to i386

Please read from the fourth message.
OLD MESSAGE:
Today I needed to cross compile and ld could not get libc.co.6 because it looks it with the absolute path /usr/lib/libc.so.6 ignoring -L options,
I tried fixing using --sysroot, but ld was not compiled with its support.
So I was wondering, it should not be better to compile with --with-sysroot ?
Last edited by ezzetabi (2010-01-08 10:11:51)

I am trying to compile the doom3 SDK: so it is a cross compiling from x86_64 to i386.
After downloading the SDK and unpacking it with --tar xf, since the package uses scons I had to modify the file SConstruct line BASELINKFLAGS: I put BASELINKFLAGS = [ "-m32", "-L/opt/lib32/lib", "-L/opt/lib32/usr/lib", ]
but the linking fails with
`/usr/bin/ld: skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6'
On the other hand if I use
BASELINKFLAGS = [ "-m32", "--sysroot=/opt/lib32", ]
ld fails anyway with... :S
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.2/../../../crti.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.2/crtbeginS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.2/crtendS.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.2/../../../crtn.o' is incompatible with i386 output
It is not really important, but I find annoying that I cannot compile it :S
Last edited by ezzetabi (2010-01-08 09:48:59)

Compiler configure problems (cross compiling?)

When attempting to compile packages, I am receiving these errors:
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/tmp/yaourt-tmp-procyon/abs-htop/src/htop-1.0.3':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build htop.
I have not changed any cflags or other build variables. Why these errors?

I should add, this occurred after I restored my system from a backup.

Problems cross compiling for Foxboard (cris-gcc)

I am trying to compile the Berkeley DB for applications on a Foxboard from ACME and I am running into some problems that I cannot solve. Perhaps someone can help me.
First problem is the configure. I use the following to configure:
cd build_unix
export prefix=/home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu
export SYSTYPE=FOXBOARD
export CCFLAGS="-isystem $prefix/include -isystem $prefix/usr/include"
export CPPFLAGS="-isystem $prefix/include -isystem $prefix/usr/include"
export RANLIB=ranlib
export STRCASE="strcasecmp.o"
export LDFLAGS="-Wl,-rpath-link,$prefix/lib,-rpath-link,$prefix/usr/lib"
export SYSLIBS="-Wl,-rpath-link,$prefix/lib,-rpath-link,$prefix/usr/lib"
export AUXLIBS=$AUXLIBS
export AR=ar-cris
export ARFL=$ARFL
export RANLIB=$RANLIB
export SYSLIBS="$AUXLIBS $SYSLIBS"
export CC=gcc_cris $CCARGS
export OPT=$OPT
export DEBUG=$DEBUG
export AWK=awk
../dist/configure          \
     --disable-largefile     \
     --disable-static     \
     --enable-smallbuild     \
     --host=i386-pc-linux-gnu \
     --target=cris-linux     \
     --enable-uimutexes     \
     --prefix $prefix/mnt/1
This works, but it produces the following messages:
configure: WARNING: sys/time.h: present but cannot be compiled
configure: WARNING: sys/time.h: check for missing prerequisite headers?
configure: WARNING: sys/time.h: see the Autoconf documentation
configure: WARNING: sys/time.h: section "Present But Cannot Be Compiled"
configure: WARNING: sys/time.h: proceeding with the preprocessor's result
configure: WARNING: sys/time.h: in the future, the compiler will take precedence
configure: WARNING: ## ---------------------------------------------------------- ##
configure: WARNING: ## Report this to Oracle Technology Network Berkeley DB forum ##
configure: WARNING: ## ---------------------------------------------------------- ##
checking for sys/time.h... yes
checking sys/fcntl.h usability... no
checking sys/fcntl.h presence... yes
configure: WARNING: sys/fcntl.h: present but cannot be compiled
configure: WARNING: sys/fcntl.h: check for missing prerequisite headers?
configure: WARNING: sys/fcntl.h: see the Autoconf documentation
configure: WARNING: sys/fcntl.h: section "Present But Cannot Be Compiled"
configure: WARNING: sys/fcntl.h: proceeding with the preprocessor's result
configure: WARNING: sys/fcntl.h: in the future, the compiler will take precedence
configure: WARNING: ## ---------------------------------------------------------- ##
configure: WARNING: ## Report this to Oracle Technology Network Berkeley DB forum ##
configure: WARNING: ## ---------------------------------------------------------- ##
Because I assume this is the forum they are talking about, I decided to obey the suggestion and report it here.
Do I need to be worried?
Laurent-jan

The problems are in the configure-step. So here is from config.log:
<pre>
configure:23212: checking sys/time.h usability
configure:23229: gcc_cris -c -Os -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include -isystem /home/foxboard/devboa
rd-R2_10/target/cris-axis-linux-gnu/usr/include -D_GNU_SOURCE -D_REENTRANT conftest.c >&5
In file included from /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/sys/time.h:4,
from conftest.c:44:
/home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/linux/types.h:59: conflicting types for `clock_t'
/usr/local/cris/cris-axis-elf/include/time.h:36: previous declaration of `clock_t'
configure:23235: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "Berkeley DB"
| #define PACKAGE_TARNAME "db-4.5.20"
| #define PACKAGE_VERSION "4.5.20"
| #define PACKAGE_STRING "Berkeley DB 4.5.20"
| #define PACKAGE_BUGREPORT "Oracle Technology Network Berkeley DB forum"
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| /* end confdefs.h. */
| #include <stdio.h>
| #if HAVE_SYS_TYPES_H
| # include <sys/types.h>
| #endif
| #if HAVE_SYS_STAT_H
| # include <sys/stat.h>
| #endif
| #if STDC_HEADERS
| # include <stdlib.h>
| # include <stddef.h>
| #else
| # if HAVE_STDLIB_H
| # include <stdlib.h>
| # endif
| #endif
| #if HAVE_STRING_H
| # if !STDC_HEADERS && HAVE_MEMORY_H
| # include <memory.h>
| # endif
| # include <string.h>
| #endif
| #if HAVE_STRINGS_H
| # include <strings.h>
| #endif
| #if HAVE_INTTYPES_H
| # include <inttypes.h>
| #endif
| #if HAVE_STDINT_H
| # include <stdint.h>
| #endif
| #if HAVE_UNISTD_H
| # include <unistd.h>
| #endif
| #include <sys/time.h>
configure:23266: result: no
configure:23270: checking sys/time.h presence
configure:23285: gcc_cris -E -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/usr/include -D_GNU_SOURCE -D_REENTRANT conftest.c
configure:23291: $? = 0
configure:23312: result: yes
configure:23325: WARNING: sys/time.h: present but cannot be compiled
configure:23327: WARNING: sys/time.h: check for missing prerequisite headers?
configure:23329: WARNING: sys/time.h: see the Autoconf documentation
configure:23331: WARNING: sys/time.h: section "Present But Cannot Be Compiled"
configure:23333: WARNING: sys/time.h: proceeding with the preprocessor's result
configure:23335: WARNING: sys/time.h: in the future, the compiler will take precedence
configure:23345: checking for sys/time.h
configure:23353: result: yes
configure:23212: checking sys/fcntl.h usability
configure:23229: gcc_cris -c -Os -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/usr/include -D_GNU_SOURCE -D_REENTRANT conftest.c >&5
In file included from /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/asm-generic/fcntl.h:4,
from /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/asm/fcntl.h:1,
from /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/sys/fcntl.h:4,
from conftest.c:45:
/home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include/linux/types.h:59: conflicting types for `clock_t'
/usr/local/cris/cris-axis-elf/include/time.h:36: previous declaration of `clock_t'
configure:23235: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "Berkeley DB"
| #define PACKAGE_TARNAME "db-4.5.20"
| #define PACKAGE_VERSION "4.5.20"
| #define PACKAGE_STRING "Berkeley DB 4.5.20"
| #define PACKAGE_BUGREPORT "Oracle Technology Network Berkeley DB forum"
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_SYS_TIME_H 1
| /* end confdefs.h. */
| #include <stdio.h>
| #if HAVE_SYS_TYPES_H
| # include <sys/types.h>
| #endif
| #if HAVE_SYS_STAT_H
| # include <sys/stat.h>
| #endif
| #if STDC_HEADERS
| # include <stdlib.h>
| # include <stddef.h>
| #else
| # if HAVE_STDLIB_H
| # include <stdlib.h>
| # endif
| #endif
| #if HAVE_STRING_H
| # if !STDC_HEADERS && HAVE_MEMORY_H
| # include <memory.h>
| # endif
| # include <string.h>
| #endif
| #if HAVE_STRINGS_H
| # include <strings.h>
| #endif
| #if HAVE_INTTYPES_H
| # include <inttypes.h>
| #endif
| #if HAVE_STDINT_H
| # include <stdint.h>
| #endif
| #if HAVE_UNISTD_H
| # include <unistd.h>
| #endif
| #include <sys/fcntl.h>
configure:23266: result: no
configure:23270: checking sys/fcntl.h presence
configure:23285: gcc_cris -E -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/include -isystem /home/foxboard/devboard-R2_10/target/cris-axis-linux-gnu/usr/include -D_GNU_SOURCE -D_REENTRANT conftest.c
configure:23291: $? = 0
configure:23312: result: yes
configure:23325: WARNING: sys/fcntl.h: present but cannot be compiled
configure:23327: WARNING: sys/fcntl.h: check for missing prerequisite headers?
configure:23329: WARNING: sys/fcntl.h: see the Autoconf documentation
configure:23331: WARNING: sys/fcntl.h: section "Present But Cannot Be Compiled"
configure:23333: WARNING: sys/fcntl.h: proceeding with the preprocessor's result
configure:23335: WARNING: sys/fcntl.h: in the future, the compiler will take precedence
configure:23345: checking for sys/fcntl.h
configure:23353: result: yes
</pre>
Running the configure again results in the same messages (which is logical) but now fails with:
<pre>
checking for unistd.h... (cached) yes
checking for off_t... no
configure: error: No off_t type.
</pre>
Crosscompiling is not as easy as it looks. Thanks for looking into this.
Laurent-jan

[SOLVED] mingw32 cross compile won't link with static libraries

Hi all,
I'm trying to cross compile an app I have written to i486-mingw32. I'm running Arch 64-bit (under which it compiles fine natively), and I have installed the mingw32 binaries along with mingw32-boost-static from AUR.
All seems well, but unfortunately when I cross compile my code libtool refuses to link to the static Boost libraries:
*** Warning: Trying to link with static lib archive /usr/i486-mingw32/lib/libboost_filesystem-mt-s.a.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because the file extensions .a of this argument makes me believe
*** that it is just a static archive that I should not use here.
This then leads to undefined references as the library is not linked in. But as I *want* the static version of the library, does anyone know how to tell libtool to accept the .a file and link it?
Last edited by Malvineous (2011-05-02 02:44:48)

Just to follow up on this, I discovered the problem. It turns out libtool was doing the correct thing, and refusing to link the static library in with the shared one (otherwise later this could result in something being defined multiple times.) The undefined references were unrelated to the error above, and the code that was causing them (in a different Boost header file) could be easily #defined out.
When the time came to link the actual executables, libtool did include all the necessary libraries and everything worked as it should!

Cross Compiling with distcc

I have a 64-bit server and a 32-bit desktop. I would like to run a distcc server on the 64-bit machine to cross-compile 32-bit software so my 32-bit machine can step up its guns. I noticed that there are cross32-binutils and cross32-gcc packages in the AUR, so I assume that I can use them with distcc, but can I and how? I want to avoid running a 32-bit chroot as much as possible (I think it's silly).

Okay, I got it up and running ... I have two problems though, one I posted here (not trying to double-post).
I am having the same issue. I want to start distccd, but when I run schroot /etc/rc.d/distccd start, it says [DONE] as usual, but the daemon doesn't come up in ps -A. if I manually chroot into /opt/arch32, I can issue the same command and it'll stay running. I'm assuming that schroot sandboxes the environment, and when the command releases the terminal, it kills all the processes associated to it.
How can I keep daemons running when they are started by schroot?
My other issue is that dictccd only uses one core. I have a hyperthreaded dual-core system on my server that constitutes as four cores, and when I'm in the 32-bit chroot, htop does in fact see four cores and appears to be using them. The client machine is set to -j7 also, so it should be utilizing the 2+4(+1) cpus, but it isn't and I'm not sure why.

Compile issues with cross-mipsel-linux-gnu-gcc

I'm trying to set up some sort of cross-compilation environment in order to compile software for a MIPS device.
I installed cross-mipsel-linux-gnu-gcc (4.7.2-1) along with cross-mipsel-linux-gnu-binutils (2.22-1). Then I tried to compile a simple Hello World, and the result was as follows:
[mcmlxxxvi@deepspace1 hello-world]$ cat hello.c
#include <stdio.h>
int main()
printf("Hello World!\n");
return 0;
[mcmlxxxvi@deepspace1 hello-world]$ mipsel-linux-gnu-gcc hello.c
hello.c:1:19: fatal error: stdio.h: No such file or directory
compilation terminated.
[mcmlxxxvi@deepspace1 hello-world]$ mipsel-linux-gnu-gcc hello.c -I/usr/include
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find crtbegin.o: No such file or directory
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find -lgcc
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find -lc
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find -lgcc
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find crtend.o: No such file or directory
/usr/lib/cross-mipsel-linux-gnu/lib/gcc/mipsel-linux-gnu/4.7.2/../../../../mipsel-linux-gnu/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
I know I generally need a compatible glibc build, but a) there isn't a package pre-built for MIPS as the compiler, and b) there is no mention of glibc in either gcc or binutils' AUR pages. So I thought that these two packages were somehow supposed to be sufficient - and they aren't.
I found a tutorial on setting up cross-compilation for MIPS and I tried to build libc, but as I used the gcc and bunutils AUR pacakges instead of going straight for the source, and, probably, as the tutorial is geared towards slightly older versions, I did not succeed. configure produced only a config.log and I wasn't able to make.
So, how are cross-mipsel-linux-gnu-gcc and cross-mipsel-linux-gnu-binutils supposed to be used? How do I need to set up my environment in order to be able to invoke the MIPS gcc the same way as my regular gcc?
Thanks in advance.

The problem is gone after going to Kernel 39 in testing.

Can anyone help me with a problem i am having with my music on my iPhone 4S. I have put alot of Compilation CDs in my library on iTunes. I download these tracks onto my phone, everything is ok so far. Now, this is what is niggling me and I don.t know how

Can anyone help me with a problem i am having with my music on my iPhone 4S. I have put alot of Compilation CDs in my library on iTunes. I download these tracks onto my phone, everything is ok so far. Now, this is what is niggling me and I don.t know how to resolve it. This is my problem:
Have downloaded for example: Queen – Bohemium Rhapsody from a compilation album as well as a few complete Queen Album CDs into the iTunes library and then put them into playlists,
When I go onto my phone and select Queen on the MUSIC app using Songs tab at the bottom of the screen it will display all Queen songs and their resective Alum pics, that is all those not in a complilation album, .
If I know the song title I can select the songs tab and find the song that way,
I’ve tried fiddling with the settings in the iTunes app by going to ‘get info’ tab and trying to sort the problem out that way but am not having much luck.What I want the phone to do is show, for example all Queens songs including those in compilation albums. Can this be done, would be grateful for any ideas on how it can be done, that is if ic can be done, any ideas
Thanks for your help

Try assigning Queen as the Album Artist on the compilations in iTunes on your computer.

Seperate include directory for i486-mingw32 cross-compiler toolchain

I've installed the mingw32 cross-compiler. I noticed that when using this compiler, a seperate, non-standard include directory is used. So instead of copying all of the dependencies headers to compile the software, is there an easier way of including both directories?
Thanks.

I've installed the mingw32 cross-compiler. I noticed that when using this compiler, a seperate, non-standard include directory is used. So instead of copying all of the dependencies headers to compile the software, is there an easier way of including both directories?
Thanks.

Problem in GCCFSS cross compiler

I have followed the instructions of using gccfss as a cross compiler. But when I compile my HelloWorld.c I encountered the following error:
ld fatal: file /usr/lib/libc.so: wrong ELF machine type: EM_386
Can anyone help me?

All
I have gccfss installed along with target (sparc) machine's /usr/include and /usr/lib directory contents.
I'm trying a simple "Hello" {color:#0000ff}cross-compile{color} exercise below and getting linking {color:#ff0000}error(s){color:#000000}.
Any ideas/suggestions?
Thank you in advance, Attila.
NB: I tried setting/defining LD_LIBRARY_PATH environment variable to point to copy of target system's library directories but get "wrong ELF machine type" errors because gccfss is referencing /usr/lib directory instead.
{color}{color}{color:#ff0000}{color:#0000ff}
$ /opt/gccfss/gcc/bin/gcc -L/opt/sparc/usr/lib -L/opt/sparc/usr/lib/mdb/proc -L/opt/sparc/usr/lib/mdb/proc/sparcv9 hello.c{color}
Undefined first referenced
symbol in file
exit /opt/gccfss/gcc/bin/../lib/gcc/sparc-sun-solaris2.10/4.2.0/crt1.o
puts /tmp/ccobWhgs.o
_exit /opt/gccfss/gcc/bin/../lib/gcc/sparc-sun-solaris2.10/4.2.0/crt1.o
bzero /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_snprintf /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_printf /opt/sparc/usr/lib/mdb/proc/libc.so
atexit /opt/gccfss/gcc/bin/../lib/gcc/sparc-sun-solaris2.10/4.2.0/crt1.o
mdb_lookup_by_obj /opt/sparc/usr/lib/mdb/proc/libc.so
strcat /opt/sparc/usr/lib/mdb/proc/libc.so
strcpy /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_alloc /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_vread /opt/sparc/usr/lib/mdb/proc/libc.so
sig2str /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_free /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_warn /opt/sparc/usr/lib/mdb/proc/libc.so
strerror /opt/sparc/usr/lib/mdb/proc/libc.so
mdb_get_xdata /opt/sparc/usr/lib/mdb/proc/libc.so
_environ /opt/gccfss/gcc/bin/../lib/gcc/sparc-sun-solaris2.10/4.2.0/crt1.o
ld: fatal: Symbol referencing errors. No output written to a.out
collect2: ld returned 1 exit status{color}

Cross compiling with crosstool-ng-hg

Is anyone successfully using crossng-hg to cross compile x86 on x86_64? I know the most popular solution is to simply use linux32 chroot /path/to/target but I'm interested in learning what other options are out there.

karol wrote:Did looking at 'Known issues.txt' or build.log gave any clues?
Nope. Shall I post my build.log?

Debugging mingw cross-compiled JNI code with drmingw

Hi there... I've been googling up a storm but so far no luck so I thought I'd throw the question out and hope for some answers. I have a chunk of native code in linux and now cross-compiled to win32 using mingw. When there is an exception in the native code, the VM exits. I'm getting java dumping its stack traces (eg. hs_err_pidXXXXX.log files), but those only have hex addresses for the native DLL because the mingw symbols aren't understood.
Example:
C [lhext.dll+0x47dcc]
C [lhext.dll+0x37408]
j some.jni.method.call.i.cant.easily.cut.and.paste
I tried to load the drmingw exchndl.dll in my native code, which I thought should dump stack traces to a file when the exception occurs, but it seems like java is controlling the exception handling and bypassing the exchndl.dll library, so the net result is no useful stack trace output.
Does anyone have a good method to do this (aside from attaching gdb in windows, which is inconvenient if this happens in the field)? Or a method to extract a call stack using the hex dll addresses from a mingw cross-compiled dll?

Hi there... I've been googling up a storm but so far no luck so I thought I'd throw the question out and hope for some answers. I have a chunk of native code in linux and now cross-compiled to win32 using mingw. When there is an exception in the native code, the VM exits. I'm getting java dumping its stack traces (eg. hs_err_pidXXXXX.log files), but those only have hex addresses for the native DLL because the mingw symbols aren't understood.
Example:
C [lhext.dll+0x47dcc]
C [lhext.dll+0x37408]
j some.jni.method.call.i.cant.easily.cut.and.paste
I tried to load the drmingw exchndl.dll in my native code, which I thought should dump stack traces to a file when the exception occurs, but it seems like java is controlling the exception handling and bypassing the exchndl.dll library, so the net result is no useful stack trace output.
Does anyone have a good method to do this (aside from attaching gdb in windows, which is inconvenient if this happens in the field)? Or a method to extract a call stack using the hex dll addresses from a mingw cross-compiled dll?

Cross compiling apps on solaris 8 for solaris 10 x86 and x64

Hi All,
We have a few applications built on Solaris 8. and we want to build the same apps on Solaris 10 x86 and x64 but the problem is clearcase does not support Solaris 10 yet.
Can we cross compile the apps on Solaris 8 for Solaris 10 x86 and x64 ? and how ?
waiting for any info on this.
TIA,
warm regards,
Girish

FYI, I noticed the reply on Sun Studio General Forum:
If you build an app on one version of Solaris, the app will run on later Solaris versions. So in particular, you can build an x86 application on Solaris 8 and run it on Solaris 9 and 10.
Unfortunately, an x64 application must be built on a Solaris x64 system, which first became available with Solaris 10.

Good instructions for making a GCC cross compiler?

Hi
I think this might be the best place to ask this since people probably have been making cross compilers. I am interested in trying to make a cross compiler of GCC targetting Plan9/i386. There is an old 3.0 version of GCC (http://cm.bell-labs.com/sources/extra/gcc/) ported to Plan9.
The thing that confuses me a bit about cross compilers is the use of binutils for the target architecture. How does that actually work? The host OS/architecture would not be able to execute those binaries. It feels a bit like a chicken-and-egg issure and I am not really sure how to get started. I have been trying to read up a bit on the PKGBUILDs for cross-arm but the whole theoretical issue of how to actually get the thing working in the first place is still a bit unclear to me.
Some good instructions/links/help would be appreciated
I could post my temporary PKGBUILD here if people want to help out with the actual build...

A small update to my attempts:
This is my binutils package, it has failed at multiple levels during my attempts. The binutils ported to Plan9 are relatively old so some stuff needs to be patched up to build. Now it fails on not being able to recognize arlex.o . This seems a bit odd I think.
# Adapted from cross-arm-elf, cross-i686-pc-gnu and cross-i686-pc-mingw32
pkgname=cross-i386-plan9-binutils
pkgver=2.11.2
pkgrel=1
pkgdesc="The GNU Compiler Collection - Cross compiler for Plan9 i386 target"
arch=('i686' 'x86_64')
license=('GPL')
url="http://plan9.bell-labs.com/wiki/plan9/porting_alien_software_to_plan_9/index.html"
depends=('glibc' 'zlib')
options=('!libtool' '!distcc' '!ccache')
source=('http://plan9.bell-labs.com/sources/extra/gcc/gnusrc.tgz' \
'bucommh.patch')
md5sums=('39d23b7223b68de4cf333205257112ce' \
'2945c4e40dbcd966217ed1349195e312')
_target=i386-lucent-plan9
_sysroot=/usr/lib/cross-${_target}
build() {
rm -rf ${srcdir}/build
mkdir ${srcdir}/build #starting fresh
msg "building and packaging binutils"
cp -ar ${srcdir}/binutils-2.11.2/* ${srcdir}/build/
cd ${srcdir}/build
msg "cheating broken references to Plan9-ported GNU binutils"
ln -s /usr/bin/ar "${_target}-ar"
ln -s /usr/bin/as "${_target}-as"
ln -s /usr/bin/ld "${_target}-ld"
ln -s /usr/bin/ranlib "${_target}-ranlib"
PATH=${srcdir}/build:$PATH
CFLAGS='-O2 -static'
msg "patching up stuff"
cd ${srcdir}/build/binutils
patch bucomm.h -i $srcdir/bucommh.patch
msg "going back to build directory and start configure"
cd ${srcdir}/build
./configure --prefix=${_sysroot} --bindir=/usr/bin \
--with-sysroot=${_sysroot} \
--build=$CHOST --host=$CHOST --target=${_target} \
--with-gcc --with-gnu-as --with-gnu-ld \
--enable-shared --without-included-gettext \
--disable-nls --disable-debug
msg "fixing some corrupt libraries"
cp /usr/lib/libiberty.a ${srcdir}/build/libiberty/
msg "finally making the actual binutils"
cd ${srcdir}/build
make
make DESTDIR=$pkgdir/ install
# clean-up cross compiler root
rm -r ${pkgdir}/${_sysroot}/share/{info,man}
# needed for gcc build
install -dm755 ${pkgdir}/${_sysroot}/include
this is the bucommh.patch:
81c81
< extern char *sbrk ();
> extern void *sbrk ();
Last edited by W.F.Cody (2011-09-13 18:57:17)

Cross compiling : CARCH flag

Hi all ! I just have a question about cross compiling. No real problem in fact
So, on the "Safe Cflags" wiki page (and on other Web pages, too), one can see lots of optimizations for various processors. But for each one, only CHOST and CFLAGS change. I don't understand what CARCH is used for, then...
"Specifies your computer architecture; possible values include "i686" or "x86_64". This should be automatically set on installation."
I think that if it never changes, this CARCH value only concern the computer which is compiling.
So, if I compile something, say, for an Athlon 64 from an Intel chip, my flags would be :
CARCH="i686"
CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
And if I compile frequently for other architectures, I would have a couple of CHOST/CFLAGS for each foreign architecture, and only one CARCH, corresponding to my computer.
Am I right ?

You should check out the Android NDK documentation. The NDK comes with a cross compiler specifically for android, with the correct versions of libraries, etc. It comes with some examples showing how to build stuff for it.
EDIT: There is also an AUR package for it.
Last edited by tom5760 (2011-04-04 15:56:25)

Problems cross-compiling imagemagick with mingw32

Similar Messages

Maybe you are looking for