How to cross compile 32bit packages on Arch64 via distcc?

Is there a way to cross compile 32 bit packages on Arch64 via distcc?
Use 32bit chroot on Arch64, maybe?
If anyone has done such things, please tell me how.
Thank you very much!

Themaister wrote:http://wiki.archlinux.org/index.php/Arc … bit_system <--- good place to start
That's exactly what I followed to make a 32bit chroot on a 64bit machine. Then just use pacman inside the chroot to install the base-devel group, and you can start compiling packages from AUR, exactly the same way as you usually do. That's what I do (I have eee laptop on which it's pain to compile, so I use my 64bit machine for compiling). Then just transfer the newly created packages to the 32bit machine and install...
I don't use distcc for that, so can't help you with this, sorry.

Similar Messages

How to cross compile CDC CVM on Redhat6.2 for stong ARM??

Dear all:
Can you tell me how to cross compile CDC CVM on Redhat6.2 for stong ARM??I failed to find any
infomation on this problem.If you know ,please tell me.
Thanks

Hi:
Thank you for your advice. I'll give your advice to my boss.But is it possible to cross-compile CVM? If the answer is positive,how?
Thank you
Best RGDS

Howto build 32bit package on Arch64?

hello,
yesterday i installed 64bit arch. I need to build 32bit and 64bit packages for my repo. I don't know how to build 32bit packages on my machine. I read http://wiki.archlinux.org/index.php/Arc … _Arch64.3F but I do something wrong. I installed gcc-multilib and tried to build mc-new (linux32 yaourt -S mc-new). I got 64bit package. Although 'linux32 uname -a' says I have i686 machine.
What did I do wrong?
Thanks (I don't want i686 chroot)

I installed i686 system to /opt/arch32. Then I did 'sudo linux32 chroot /opt/arch32'. Now I can build 32bit packages running on i686? Am I right?
Is this ok? /opt/arch32/etc/makepkg.conf:
CARCH="i686"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=native -mtune=generic -O2 -pipe"
CXXFLAGS="-march=native -mtune=generic -O2 -pipe"

How do I compile a package?

JAVA QUESTION: When I compile a package do I execute this with javac (the name of the package).java or what?

Greetings,
I have a question that relates here... I have been trying to compile a program that uses several packages I have created in an IDE by hand. In the IDE they compile fine, or if I leave out the package name/imports and have all the files in the same dir, but if I try it by hand with all the files in their dirs javac complains it can't find them.
I have the files in individual folders by package, which works with the ide. Dir structure/package names are roughly as so:
MyProj (package MyProj)
-gui (package MyProj.gui)
--blue (package MyProj.gui.blue)
--green (package MyProj.gui.green)
-units (package MyProj.units)
--foot (package MyProj.units.foot)
etc.
I have appropriate import's for each package file, and I am trying to compile from the MyProj folder, where the main file is located.
My guess is that I need to have all the folders of the various packages in the classpath, or they all need to be sent to javac, which seems really clumsy to me, not to mention wrong - see the quote from the Tut below...
My path and classpath seem to be all right - I can happily compile stuff, just not when they are in packages :( Actually, come to think, I have the classpath listed with '.\' at the end, which I thought would've been sufficient for javac to workout where the other dirs are.
From Java tut:Managing Source and Class files: "From the top- level directory, the compiler and the interpreter can construct the rest of the path, based on the package and the class name for the class"
What am I doing wrong, or is my guess correct? Is there any easier way of compiling packages by hand or do I really need an IDE? Having twenty or thirty sources and classes in one dir doesn't really appeal...
And does anyone know of a good ide in Linux (which more or less sparked this issue), which I am just learning to love...
Any help is appreciated.
Cheers

How to make use of 32bit packages on Arch64

Hello everyone, I recently installed arch 64bit which was not yet fully tweaked to suit my needs.
My 32bit version has some nice apps and I would like to know how to make use of them or even reuse them so that I won't download things anymore because I have a slow internet connection...:)
Arch x86_64 / XFCE4
Thanks in advance
Last edited by kaola_linux (2008-12-09 15:24:36)

kaola_linux wrote:
Hello everyone, I recently installed arch 64bit which was not yet fully tweaked to suit my needs.
My 32bit version has some nice apps and I would like to know how to make use of them or even reuse them so that I won't download things anymore because I have a slow internet connection...:)
Arch x86_64 / XFCE4
Thanks in advance
You can reuse the packages in /var/cache/pacman/pkg/ on your Arch32.
You can use these saved packages in a 32bit chroot ENV on your Arch64. Just pacman -U all of them.

Using makepkg to cross-compile (for sparc64)

I recently acquired a Sun Ultra 5 system with a TI UltraSparc IIi CPU (sparc64). I am in the middle of doing some compiling on it using Debian as the host system while dabbling into cross-compiling for it. It would be superb to have a sparc64 toolchain installed and in the $PATH on a modern x86_64 system while using makepkg to cross-compile sparc64 packages. I would copy /etc/makepkg.conf to a working directory, make the necessary changes, and run makepkg --config /working/dir/makepkg.conf. makepkg would then (theoretically) pick up that I'm cross compiling, see the proper toolchain in the path, and cross compile.
Is this possible? If not, what kind of work/patching would be necessary to make it happen?

cedeel wrote:A Sparc64 chroot isn't possible. The closest thing would be to run a chroot-like environment in QEMU.
A cross toolchain should be preferred, although I have no idea on how to set it up.
Yeah. I'm building a toolchain atm. As long as the PKGBUILDs know that I'm cross compiling, I should be okay. There will be a bit of hand-cranking needed since not all sources use autotools. Not really looking forward to cross-compiling openssl, and the kernel will take a bit of screwing around to work right, but, meh, that's part of the fun, right? There's only 100-ish packages for a base install, so just getting to a functional system won't be too bad.
I'm going to experiment with an auto-build system when I have the system running. I'm very comfortable with bash scripting and am learning c++, so I have some good ideas. I work as a sysadmin too, so I could even give some of the meatier servers at work an extra job to do. That is, if all goes well
Last edited by synthead (2012-01-02 20:18:18)

Compiling two packages referenced to each other

I've got two Packages named PackageA and PackageB from other developer
PackageB imports a class from PackageA as
import PackageA.class1;
PackageA imports all classes from PackageB as
import PackageB.*;
My questions are:
1. Is it allowed in Java?
2. How do I compile these packages? Here is what I tried. I wrote a Ant Script to compile I couldn't compile succefully. Then I tried to compile manually by compiling first Class1 from PackageA, followed by PackageB and then came back to compile remaining classes in PackageA. The compilation was successful. But what I don't understand is how it compiled successfully in the command prompt.
Any help would be appreciated
thanks

Probably the classpath setting wasn't correct, so the "other" class couldn't be found. See How Classes are Found, http://java.sun.com/j2se/1.4.1/docs/tooldocs/findingclasses.html

How can I compile an entire package ??

Hi
I've downloaded about 20 .java files (these files build a package) and I want to compile them now with javac. Compiling the files one after the other produces unfortunately many errors. The owner of the code told me I've to "compile the entire package" and I should use Borland's JBuilder for that. Installing JBuilder makes trouble so I want to compile the code with javac.
Do you know how I can compile an entire package with javac ?
javac *.java doesn't work (produces lots of errors).
Thanks in advance,
Marcel

Hi
I've downloaded about 20 .java files (these files
build a package) and I want to compile them now with
javac. Compiling the files one after the other
produces unfortunately many errors. The owner of the
code told me I've to "compile the entire package" and
I should use Borland's JBuilder for that. Installing
JBuilder makes trouble so I want to compile the code
with javac.
Do you know how I can compile an entire package with
javac ?
javac *.java doesn't work (produces lots of errors).
I doubt it.
"javac *.java" will compile any dependent class files in the same package.
There are several possibilities.
1. There is more than one package.
2. The class path is wrong. (The class path must have the root of the directory and obviously the java files must exist in a directory tree that mirrors the package.)
3. Something is wrong with the java files. Or perhaps something is missing.

How to compile all package body using sqlplus ?

hi all,
How to compile all package body using sqlplus ?
Please help.
Amy

dbms_utility.compile_schema will compile all the invalid objects in a schema, including the invalid package bodies. If you only want to compile the invalid package bodies, you could write your own dynamic SQL stored procedure to do that using the user_source view, but that's a lot more effort for a very minimal benefit.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

New programmer- how do i compile package members?

im learning java using sams teach yourself java in 21 days. its really good compared to other ive tried but i was having a problem on day 6. i couldnt compile package members successfully. i didnt undestand the book instruction so instead of compiling this way:
C:\noam\java> c:\java\jdk1.5.0_06\bin\javac classname.java
i did it this way:
C:\java\noam\org\cadenhead\ecommerce> c:\java\jdk1.5.0_06\bin\javac classname.java
this worked but other classes inside the package could not recognize this class, though classes outside the package could.
how do i compile package members?
thnx!

I solved the problem...! I have no idea how but it worked this time!
thnx anyway for everybody who tried to help!

How to compile and package my EJB application

Hi,
I just ran the sample programs from the Sun J2EE tutorial. Seems to work fine. I used the ant utility to compile all the programs and the J2EE Deployment Wizard to package and deploy everything. Now how do I compile and deploy a sample EJB program that I have written ?
I am using the following platforms:
1: JBuilder 3.0 : IDE (for writing the source code)
2: JDK 1.4.0_01
3: J2SDK EE 1.3.1 (EJB/Appln server)
How do I make ant recognize my program and compile it... i guess the deployment procedure would still be the same.
Can somebody please help me out on this ??
Thanks
prasanna

Hi,
Thanks for your prompt reply. I tried that out.. I have a directory called "customer" under which I have my interfaces,bean implementation class and the J2EE application client.
ANT_HOME is set to : the directory where ant is installed
JAVA_HOME is set to : the directory where JDK is installed
J2EE_HOME is set to : the directory where J2EE server is installed
and PATH : includes the bin directories of JDK, ant and J2SDK EE
These are the paths I had to set when I ran the J2EE tutorial programs. It worked fine.
Now when I say : ant myprogram I get an error saying:
BUILD FAILED
Target "myprogram" does not exist in this project
How do I add my program also to the project so that ant can recognize it ?
Also if there is any other way you can suggest to compile and package my application it would be great...
Thanks
prasanna

How to get return code of compiling a package

Hi,
i want to compile a package and if it was not succesfull to write the error_message from "show errors" into a file.
thx
Wolle

the problem with compiling individual packages is that you might inadvertently invalidate others. you should also programmatically check package dependencies too so you dont break any accidentally.
if you're only compiling package bodies, this shouldn't be an issue, but if youre also compiling specs, this is something you should keep an eye on.
i wrote an application that uploads new packages i commit in cvs to our database and then recompiles them. it then reports whether or not compilation was successful. this helps eliminate alot of user error when people manually recompile packages in HA environments. however, i recompile the entire schema when i do this (this is not something run very often). i can get away with this at my shop because the schema is very small, but this might not be a practical solution for everyone.
this is how i check for dependencies:
FROM public_dependency pd, user_objects uo
WHERE referenced_object_id IN (select object_id from user_objects where object_name= UPPER(?))
AND uo.object_id = pd.object_id
this is useful for saving a snapshot of current package (in case of reversion):
SELECT TEXT FROM USER_SOURCE WHERE NAME = ?
this is how you can recompile the schema:
DBMS_UTILITY.COMPILE_SCHEMA(?, TRUE, TRUE);
i do a check for invalid objects in the schema before i even start (And exit with error if any are found) :
SELECT OBJECT_NAME, STATUS
FROM USER_OBJECTS
WHERE (OBJECT_TYPE='PACKAGE' OR OBJECT_TYPE='PACKAGE BODY')
AND STATUS <> 'VALID'
Hope this info helps.
Edited by: user577162 on Aug 25, 2008 2:21 PM

How to compile a package with classess

Hi,
Can any one tell me , how to compile a package ?
Actually, i have three classes under the package named as linklist.
i am unable to compile the classes under this package ? its always raising errors. saying that the package does not exist.
Can any one tell me, why it is like this ?
thanks in advance

Hi,
Can any one tell me , how to compile a package ?I'll try.
Actually, i have three classes under the package named
as linklist. Okay, so you have the package statement at the top of each class, right?
And the 3 classes reside in a folder named linklist?
Okay, if you do, while in the folder above linklist, do:
javac linklist/*.java (using the appropriate slash)
Did it work?

Error when re-compiling a package

I get the following error when I re-compile my package.
Yesterday someone has compiled this package and changes are reflected.
How to get this package unlocked???.
ERROR at line 1:
ORA-04021: timeout occurred while waiting to lock object
SCH_LOAD.DNS_LOAD_BASE_TABLES_CRDM
ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring
Cause: While waiting to lock a library object, a timeout is occurred.
Action: Retry the operation later.

Thanks Rob,
Usually this package takes few minutes to re-compile and we have already crossed 2 to 3 hours.
Could you please let me know what might be the probable reasons for this abnormal behaviour.
we are able to find required changes using user_source view.
Could you please let me know on how to kill the process and unlock the package.
thanks in advance.

[SOLVED] cross compiling libopenfst makepkg error

Hello there,
I am trying to cross compile openfst on my 64 bit arch setup since it is taking too long on my raspberry pi (which also happily runs arch). I thought I would be ok with the following makepkg to get me a binary package which I could transfer to my pi and then install with pacman-U:
# Maintainer: Christoph Drexler <chrdr at gmx dot at>
pkgname=openfst
pkgver=1.4.1
pkgrel=1
pkgdesc="Library for constructing, combining, optimizing, and searching weighted finite-state transducers (FSTs)"
arch=('i686' 'x86_64' 'armv6h')
url="http://www.openfst.org/"
license=('APACHE')
depends=('gcc-libs' 'glibc')
options=(!libtool)
source=("http://openfst.cs.nyu.edu/twiki/pub/FST/FstDownload/${pkgname}-${pkgver}.tar.gz")
md5sums=('ca8f1730b9b9b281e515611fa9ae23c0')
build() {
cd ${srcdir}/${pkgname}-${pkgver}
#export CXX=arm-linux-gnueabi-g++
#export CC=arm-linux-gnueabi-gcc
# Options according to http://openfst.cs.nyu.edu/twiki/bin/view/FST/ReadMe
OPTIONS="--prefix=/usr --disable-dependency-tracking"
OPTIONS+=" --enable-bin" # Enable fst::script and command-line binaries; Default: yes
OPTIONS+=" --enable-compact-fsts" # Enable all CompactFst classes; Default: no
OPTIONS+=" --enable-const-fsts" # Enable all ConstFst classes; Default: no
OPTIONS+=" --enable-far" # Enable FAR (FST Archive) extension; Default: no
OPTIONS+=" --enable-linear-fsts" # Enable Linear{Tagger,Classifier}Fst extensions; Default: no
OPTIONS+=" --enable-lookahead-fsts" # Enable LookAheadFst classes; Default: no
OPTIONS+=" --enable-pdt" # Experimental push-down transducer extensions; Default: no
OPTIONS+=" --host=arm-linux-gnueabi" # Experimental push-down transducer extensions; Default: no
OPTIONS+=" --build=x86_64" # Experimental push-down transducer extensions; Default: no
LIBS="-ldl" ./configure $OPTIONS
make
package() {
cd ${srcdir}/${pkgname}-${pkgver}
make DESTDIR=${pkgdir} install
(basically adding the host and build option)
However, I get an error in the output:
==> Making package: openfst 1.4.1-1 (Sun Jan 11 16:13:22 CET 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found openfst-1.4.1.tar.gz
==> Validating source files with md5sums...
openfst-1.4.1.tar.gz ... Passed
==> Extracting sources...
-> Extracting openfst-1.4.1.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-linux-gnueabi-strip... arm-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-linux-gnueabi-g++... arm-linux-gnueabi-g++
checking whether the C++ compiler works... no
configure: error: in `/home/tom/openfst-1.4.1/src/openfst-1.4.1':
configure: error: C++ compiler cannot create executables
See `config.log' for more details
==> ERROR: A failure occurred in build().
Aborting...
the error being that the C++ compiler cannot create excecutables makes sense since they are not meant to be excecuted on x86_64 but for armv6h (cross compilation). I have checked with arm-linux-gnueabi-g++ and its excecutables I can run on my pi so this should be ok. I am guessing that I am either missing an option to disable the compiler check, or I should change the configure script and remove this check, but I cannot figure out how to do either...
//edit: I'm not sure this topic is in the right place btw, maybe it should be in scripting...
Last edited by tomzooi (2015-01-11 18:23:35)

that seems to do the trick, I'm not gonna test it since my pi just finished compiling it locally (which took 12+hours or so), but the compile seems to work since they are not excecutable on 64 bit, so pkgbuild for raspi cross compilation using makepkg -s:
# Maintainer: Christoph Drexler <chrdr at gmx dot at>
pkgname=openfst
pkgver=1.4.1
pkgrel=1
pkgdesc="Library for constructing, combining, optimizing, and searching weighted finite-state transducers (FSTs)"
arch=('i686' 'x86_64' 'armv6h')
url="http://www.openfst.org/"
license=('APACHE')
depends=('gcc-libs' 'glibc')
options=(!libtool !buildflags)
source=("http://openfst.cs.nyu.edu/twiki/pub/FST/FstDownload/${pkgname}-${pkgver}.tar.gz")
md5sums=('ca8f1730b9b9b281e515611fa9ae23c0')
build() {
cd ${srcdir}/${pkgname}-${pkgver}
# Options according to http://openfst.cs.nyu.edu/twiki/bin/view/FST/ReadMe
OPTIONS="--prefix=/usr --disable-dependency-tracking"
OPTIONS+=" --enable-bin" # Enable fst::script and command-line binaries; Default: yes
OPTIONS+=" --enable-compact-fsts" # Enable all CompactFst classes; Default: no
OPTIONS+=" --enable-const-fsts" # Enable all ConstFst classes; Default: no
OPTIONS+=" --enable-far" # Enable FAR (FST Archive) extension; Default: no
OPTIONS+=" --enable-linear-fsts" # Enable Linear{Tagger,Classifier}Fst extensions; Default: no
OPTIONS+=" --enable-lookahead-fsts" # Enable LookAheadFst classes; Default: no
OPTIONS+=" --enable-pdt" # Experimental push-down transducer extensions; Default: no
OPTIONS+=" --host=arm-linux-gnueabi" # Experimental push-down transducer extensions; Default: no
OPTIONS+=" --build=x86_64" # Experimental push-down transducer extensions; Default: no
LIBS="-ldl" ./configure $OPTIONS
make
package() {
cd ${srcdir}/${pkgname}-${pkgver}
make DESTDIR=${pkgdir} install
to get some stuff which I think I can ignore:
strip: Unable to recognise the format of the input file `./usr/bin/fstprint'
strip: Unable to recognise the format of the input file `./usr/bin/farprintstrings'
strip: Unable to recognise the format of the input file `./usr/bin/fstmap'
strip: Unable to recognise the format of the input file `./usr/bin/fstsynchronize'
strip: Unable to recognise the format of the input file `./usr/bin/fstdraw'
strip: Unable to recognise the format of the input file `./usr/bin/fstepsnormalize'
strip: Unable to recognise the format of the input file `./usr/bin/fstdisambiguate'
strip: Unable to recognise the format of the input file `./usr/bin/fstunion'
strip: Unable to recognise the format of the input file `./usr/bin/pdtexpand'
strip: Unable to recognise the format of the input file `./usr/bin/fstminimize'
strip: Unable to recognise the format of the input file `./usr/bin/fsttopsort'
strip: Unable to recognise the format of the input file `./usr/bin/pdtreplace'
strip: Unable to recognise the format of the input file `./usr/bin/fstreverse'
strip: Unable to recognise the format of the input file `./usr/bin/fstsymbols'
strip: Unable to recognise the format of the input file `./usr/bin/farequal'
strip: Unable to recognise the format of the input file `./usr/bin/fstequal'
strip: Unable to recognise the format of the input file `./usr/bin/fstcompile'
strip: Unable to recognise the format of the input file `./usr/bin/fstshortestpath'
strip: Unable to recognise the format of the input file `./usr/bin/farinfo'
strip: Unable to recognise the format of the input file `./usr/bin/fstrandgen'
strip: Unable to recognise the format of the input file `./usr/bin/fstshortestdistance'
strip: Unable to recognise the format of the input file `./usr/bin/fstarcsort'
strip: Unable to recognise the format of the input file `./usr/bin/fstrmepsilon'
strip: Unable to recognise the format of the input file `./usr/bin/fstconvert'
strip: Unable to recognise the format of the input file `./usr/bin/fstreplace'
strip: Unable to recognise the format of the input file `./usr/bin/farcompilestrings'
strip: Unable to recognise the format of the input file `./usr/bin/fstencode'
strip: Unable to recognise the format of the input file `./usr/bin/fstpush'
strip: Unable to recognise the format of the input file `./usr/bin/pdtshortestpath'
strip: Unable to recognise the format of the input file `./usr/bin/fstinfo'
strip: Unable to recognise the format of the input file `./usr/bin/fstrelabel'
strip: Unable to recognise the format of the input file `./usr/bin/fstinvert'
strip: Unable to recognise the format of the input file `./usr/bin/fstconcat'
strip: Unable to recognise the format of the input file `./usr/bin/fstintersect'
strip: Unable to recognise the format of the input file `./usr/bin/pdtreverse'
strip: Unable to recognise the format of the input file `./usr/bin/fstclosure'
strip: Unable to recognise the format of the input file `./usr/bin/fstdeterminize'
strip: Unable to recognise the format of the input file `./usr/bin/fstcompose'
strip: Unable to recognise the format of the input file `./usr/bin/fstlinear'
strip: Unable to recognise the format of the input file `./usr/bin/pdtcompose'
strip: Unable to recognise the format of the input file `./usr/bin/farcreate'
strip: Unable to recognise the format of the input file `./usr/bin/fstdifference'
strip: Unable to recognise the format of the input file `./usr/bin/fstloglinearapply'
strip: Unable to recognise the format of the input file `./usr/bin/fstprune'
strip: Unable to recognise the format of the input file `./usr/bin/pdtinfo'
strip: Unable to recognise the format of the input file `./usr/bin/fstproject'
strip: Unable to recognise the format of the input file `./usr/bin/farextract'
strip: Unable to recognise the format of the input file `./usr/bin/fstequivalent'
strip: Unable to recognise the format of the input file `./usr/bin/fstconnect'
strip: Unable to recognise the format of the input file `./usr/bin/fstreweight'
strip: Unable to recognise the format of the input file `./usr/lib/libfst.so.3.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact8_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact8_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstfar.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/const16-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact8_weighted_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/arc_lookahead-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/const64-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstlinearscript.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact16_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact16_unweighted-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstlookahead.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/linear_classifier-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/linear_tagger-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact16_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstcompact.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/olabel_lookahead-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/const8-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact16_weighted_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact16_unweighted_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact64_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstconst.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/ilabel_lookahead-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact64_unweighted-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact64_weighted_string-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstfarscript.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact8_unweighted_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/libfstpdtscript.so.1.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact8_unweighted-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact64_unweighted_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/fst/compact64_acceptor-fst.so.0.0.0'
strip: Unable to recognise the format of the input file `./usr/lib/libfstscript.so.1.0.0'
I will check soon I hope , for now will mark it as solved.

How to cross compile 32bit packages on Arch64 via distcc?

Similar Messages

Maybe you are looking for