[Solved] Programs segfaults when compiled by makepkg

Hi!
I changed my computer recently and now makepkg is giving me segfaults. When I try to build mplayer from aur I get segfaults when ./configure is run.
The strange thing it that mplayer unset CFLAGS... makepkg change something else in the enviroment? I'm getting segfaults on building asymptote too. Outside of makepkg, compiling mplayer manually works.
I have a Intel Core2 Duo CPU and my makepkg.conf have the following
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"
#-- Exclusive: will only run on -march=x86-64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=nocona -mtune=generic -O2 -pipe"
CXXFLAGS="-march=nocona -mtune=generic -O2 -pipe"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j3"
Thanks.
Last edited by kazuo (2009-04-15 17:05:12)

you have nvidia-utils installed? Is a know issue [#1]
if true use this workaround:
LD_PRELOAD=/xyz/usr/lib/libGL/libGL.so.1.2 makepkg
Where "xyz" is the path to a extracted libgl package from Arch Linux for example /home/kazuo/libgl
[#1] http://bugs.archlinux.org/task/13375#comment39966

Similar Messages

Severe chromium lag when compiling via makepkg

I am noticing a pretty severe lag when scrolling or opening a new tab, general usage of chromium when my machine is running makepkg to compile something. I'd like to get someone to confirm that it's not something odd unique to my system. Can someone please confirm this? I recommend building a package that takes some time to compile like a kernel. Just start makepkg -s in a kernel package and once your cpu(s) get throttled up, try using chromium to browse the forums or whatever. Any odd effects there as I am describing?
Quad core x3360 w/ 8 GB of RAM running x86_64 and nvidia driver.

@karol - firefox is just fine. it happens under bfs and am testing cfq now (building pkg).
Last edited by graysky (2012-01-13 21:11:54)

Can any solve this exception when compiling the source code

when i compile the source code . i am getting the following exceptions
1.java.lang.classnotfoundException and javax.jnlp.UnavailableServiceException
BadFieldException[ The field <jnlp>codebase has an invalid value: $$context/adempiereHome,$$context/adempiereHome]
 at com.sun.javaws.jnl.XMLUtils.getAttributeURL(Unknown Source)
 at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
 at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
 at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
 at com.sun.javaws.Main.launchApp(Unknown Source)
 at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
 at com.sun.javaws.Main$1.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

looks like you're using java web start to run app. am i right? personally i don't have much expertise in this area but i've had to deal with it before, essentially what your problem looks to me is that the codebase in your jnlp file is set up wrong
under my definition (vague) the codebase points to where java should look at to find your files and run them
do a search and read more about running apps. through web start if that's your case

[Solved] X segfaults when playing video files, not web video (fglrx)

When I try to play a video file with either VLC or mplayer, X segfaults with the following error:
[ 47876.400] (EE)
[ 47876.400] (EE) Backtrace:
[ 47876.400] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x584ae8]
[ 47876.400] (EE) 1: /usr/bin/X (0x400000+0x1887c9) [0x5887c9]
[ 47876.400] (EE) 2: /usr/lib/libpthread.so.0 (0x7f2634b4c000+0xf880) [0x7f2634b5b880]
[ 47876.400] (EE) 3: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxPixmapIsTypeOf+0x25) [0x7f26318d7af5]
[ 47876.401] (EE) 4: /usr/lib/xorg/modules/drivers/fglrx_drv.so (atiddxPixmapIsTypeOf+0xd) [0x7f26316f146d]
[ 47876.401] (EE) 5: /usr/lib/xorg/modules/amdxmm.so (X740XvPutImage+0x197) [0x7f262e7f3957]
[ 47876.401] (EE) 6: /usr/bin/X (0x400000+0x8b9c2) [0x48b9c2]
[ 47876.401] (EE) 7: /usr/bin/X (0x400000+0xd31c2) [0x4d31c2]
[ 47876.401] (EE) 8: /usr/bin/X (0x400000+0x35d1e) [0x435d1e]
[ 47876.401] (EE) 9: /usr/bin/X (0x400000+0x39b2a) [0x439b2a]
[ 47876.401] (EE) 10: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f26337c3b05]
[ 47876.401] (EE) 11: /usr/bin/X (0x400000+0x250ce) [0x4250ce]
[ 47876.401] (EE)
[ 47876.401] (EE) Segmentation fault at address 0x47
[ 47876.401] (EE)
Fatal server error:
[ 47876.401] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 47876.401] (EE)
[ 47876.401] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 47876.401] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 47876.401] (EE)
[ 47876.401] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 47876.402] (II) fglrx(0): Backup framebuffer data.
[ 47876.426] (II) fglrx(0): Backup complete.
[ 47876.640] (EE) Server terminated with error (1). Closing log file.
I think those are the only relevant things in the log file, everything before that is at an older time and I think is a log from when I ran "startx". I think this is the first time I've run video since updating catalyst-utils. Web video (eg YouTube) plays fine and doesn't cause any problems. I've tried reinstalling catalyst-utils and still have the same problems. The version is 14.1-1.
Any ideas on what I should try? Also, is there an easy way to switch to the open source driver, and then back to catalyst if that doesn't work? I tried using the open source one for a while but had issues so started using catalyst, but it's possible the issues I had with the foss one are now fixed.
Edit: I managed to install the FOSS drivers and all problems I formerly had with my 6970 are now fixed. This is a better solution than I could have hoped for, since I had been having a few problems with catalyst before the segfaulting started, and I'm having none of them with xf68-video-ati. And, full resolution from before I start X!
Last edited by davidjosepha (2014-02-13 19:59:55)

shak wrote:Also is there an easier way for mplayer to play my files , with default settings , so that i don't have to type a big command each time i want to play a video ?
Yes. You can put all of your personal default settings in the file ~/.mplayer/config. If it doesn't already exist, just create it. On my VDPAU enabled system it looks like this:
[default]
vo=vdpau,xv,
deint=4
hqscaling=9
vc=ffh264vdpau,ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,
channels=2
As far as subtitles go, I never use them so I have no idea.

Segfault when handling __m128i

Hi,
the below code segfaults when compiled with -m32, but runs fine when built with -m64 or when built with gcc regardless of the 32/64 bits.
A slight shift of the cast makes the segfault go away (below).
Is it a bug in CC or is there something else in it?
(this is with 12.3beta and 12.1)
TIA for any hints
failing code:
<pre>
#include <cstdlib>
#ifdef __SUNPRO_CC
#include <sys/emmintrin.h>
#else
#include <xmmintrin.h>
#endif
int main(int argc, char** argv) {
const unsigned char s1[16] = {0U,1U,2U,3U,4U,5U,6U,7U,8U,9U,10U,11U,12U,13U,14U,15U};
const unsigned char *s2 = s1;
int x = 0;
__m128i top = mmloadu_si128((__m128i*)((const unsigned int *)(s2)+x));
return 0;
</pre>
non-failing code:
<pre>
#include <cstdlib>
#ifdef __SUNPRO_CC
#include <sys/emmintrin.h>
#else
#include <xmmintrin.h>
#endif
int main(int argc, char** argv) {
const unsigned char s1[16] = {0U,1U,2U,3U,4U,5U,6U,7U,8U,9U,10U,11U,12U,13U,14U,15U};
const unsigned char *s2 = s1;
int x = 0;
__m128i* qqq = (__m128i*)((const unsigned int *)(s2)+x);
__m128i top = mmloadu_si128(qqq);
return 0;
</pre>

Take a look at the bug I have filed in the middle of Nov 2011. Under some conditions the Oracle C++ compilers won't even compile SSE2 code.
*2011-11-14 15:42:54.85 EMAIL SENT BY* ****
From: *** ****
Subject: Re: (Incident Review ID: 2127676) C++ compiler crash when compiling SSE2 code.
Hi Konstantin, we have verified this bug against our latest build and it is no longer reproducible.
Report

 category : compiler
subcategory : ube
 release : spica
 type : bug
 synopsis : C++ compiler crash when compiling SSE2 code.
 sdn id :
 hardware : x86
 os : solaris_10
 bug id : 0
date created : Mon Nov 14 04:19:23 MST 2011
 date eval : Mon Nov 14 15:42:59 MST 2011

ADDITIONAL OS VERSION INFORMATION :
uname -a: SunOS jabba 5.11 snv_130 i86pc i386 i86pc
This is a "SXCE snv_130 X86 (14 Dec 2009)" system running 32-bit kernel.
EXTRA RELEVANT SYSTEM CONFIGURATION :
$ CC -V
CC: Sun C++ 5.12 SunOS_i386 Spica 2011/07/21
A DESCRIPTION OF THE PROBLEM :
Compiling this peace of code results in compiler crash if optimization level is not zero:
#include <emmintrin.h>
class A {
public:
 ~A() {};
 char *data();
static A
foo(const short *src) {
 A a;
 char *dst = a.data();
 __m128i chunk = _mm_loadu_si128((__m128i*)src);
 const __m128i rv = _mm_packus_epi16(chunk, chunk);
 _mm_storeu_si128((__m128i*)dst, rv);
 return a;
A
bar() {
 short u[3];
 return foo(u);
}| $ CC -xO1 -c -xarch=sse2 -o t.o t.C
|
| assertion failed in function unzip() @ fall_thru.c:521
| assert(nd_not_null_(start_label))
|
| CC: ube failed for t.C
Compiling very similar peace of code results in compiler crash in ir2hf:
#include <emmintrin.h>
class A {
public:
 ~A() {};
 char *data();
static A
foo(const short *src) {
 A a;
 __m128i chunk = _mm_loadu_si128((__m128i*)src);
 const __m128i rv = _mm_packus_epi16(chunk, chunk);
 _mm_storeu_si128((__m128i*)a.data(), rv);
 return a;
A
bar() {
 short u[3];
 return foo(u);
}| $ CC -xO1 -c -xarch=sse2 -o t.o t.C
| CC: Fatal error in /opt/SUNWspro/prod/bin/ir2hf
| CC: Status 139
I nominate this bug as regression, because "Sun Studio Express 2009/03" compiles this code flawlessly.
With that, I shall strongly emphasize that SSX0903 is also buggy compiling SSE2 code. Below is the test case to crash SSX0903 C++, and that bug may still present in 12u3b release, but hidden by the front bug. I kindly invite the developers to check this bug too.
Here is a test case to crash SSX0903:
#include <emmintrin.h>
class A {
public:
 char *data();
static A
foo(const short *src) {
 A a;
 char *dst = a.data();
 for ( int i = 0; i < 1; ++ i ) {
 __m128i chunk1 = _mm_loadu_si128((__m128i*)src);
 __m128i chunk2 = _mm_loadu_si128((__m128i*)src);
 const __m128i rv = _mm_packus_epi16(chunk1, chunk2);
 _mm_storeu_si128((__m128i*)dst, rv);
 return a;
A
bar()
 short u[8];
 return foo(u);
}| $ CC -V
| CC: Sun Ceres C++ 5.10 SunOS_i386 2009/03/06
| $ CC -xO2 -c -xarch=sse2 -o t.o t.C
| Assembler: t.C
| "/tmp/ube.10982.6.s", line 63 : Syntax error
| Near line: "{ 14 } movdqa (%xmm0),%xmm1 "
REGRESSION Last worked in version ossx10.06
REPRODUCIBILITY This bug can be reproduced always.

JSObject programming was not working when compiled in JSDK1.4.2_06

JSObject programming was not working when compiled in JSDK1.4.2_06.
But problem solved when i compiled with JSDK1.3.1_15 and tested with JVM 1.3.1_15.
Still I could not run the class file generated in JSDK1.3.1_15 in JVM 1.4.2_06.
What do you think happened across the SDK versions? Shouldn't the JSObject
and other classes be part of the browser JVM.
I want to know whether JSObject supports in JSDK1.4.2_06.
It goes into the loop. It neither say error nor execute.

Do not spam the site by posting to 4 forums

Error when compiling the upload program (Message no. RSAR233)

Hello,
I tried to upload data from a flatfile but I did modified the Comm.Structure, Trans.Structure and Transfer Rules.
After activating the all changes, I check data from InfoPackage by previewing it. Unfortunately, I got the follow messages from the popup window:
Error 8 when compiling the upload program: row
227, message: Data type /BIC/CCABTWJI_STK01 was
found in a newer
I got this kind of problems many times. I solved it by create a new infosource and everything again. I don't think it's good idea to do this way.
Any better solution would be sincerely appreciated?
-WJ-

Another solution:
go out the transaction RSA1 ans return to the transaction RSA1 again.
This would help for me without restarting anything.
Thank you very much for all suggestion.
-WJ-

Error 8 when compiling the upload program: row 436

Hi all,
pls let me know how to solve this error
Error 8 when compiling the upload program: row 436, message: A newer version of data type /BIC/B0000582000 was
Thanks
Prashant

Hello SAP gurus.
I know it's a very long time the question was asked, but who cares if it can someday help somebody?
So i just faced the same issue, the solution was sample, i relaunch RSA1 and the problem was solved.
Hope i would be helpful
Salah

How to solve the problem when opening program illustrator cs6 ERROR: 16 It is WINDOWS 8.1 / 64 BIT help please

how to solve the problem when opening program illustrator cs6
ERROR: 16
It is WINDOWS 8.1 / 64 BIT
help please

Thanks, Jeff! The file Adobe Setup Error.log contains the following information:
02/14/14 07:20:26:474 | [INFO] | | OOBE | DE | | | | 8860 | DEVersion: 5.0.0.0
02/14/14 07:20:26:475 | [INFO] | | OOBE | DE | | | | 8860 | Loading library from C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\DECore\DE5\Setup.dll
[    8860] Fri Feb 14 07:20:26 2014 INFO
::START TIMER:: [Total Timer]
CHECK: Single instance running
CHECK : Credentials
Load Deployment File
CHECK : Another Native OS installer already running
Create Required Folders
Assuming uninstall mode
Lookup for master payload
[    8860] Fri Feb 14 07:20:26 2014 ERROR
DW040: The product "{893B3B44-0A1E-404B-8FE8-0A74509102A9}" is not installed. Cannot proceed with the uninstall
[    8860] Fri Feb 14 07:20:26 2014 INFO
:: END TIMER :: [Total Timer] took 6.90443 milliseconds (0.00690443 seconds) DTR = 579.338 KBPS (0.56576 MBPS)
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 1 error(s), 0 warning(s)
ERROR: DW040: The product "{893B3B44-0A1E-404B-8FE8-0A74509102A9}" is not installed. Cannot proceed with the uninstall
Please search the above error/warning string(s) to find when the error occurred.
These errors resulted in installer Exit Code mentioned below.
Exit Code: 33 - The product is not installed, cannot uninstall.
Please see specific errors and warnings for troubleshooting. For example, ERROR: DW040 ...

Excel extractor produces error "Error 8 when compiling the upload program"

I am trying to test a new Excel extractor I've created but when I do so I get the following error:
RSAR233
Error 8 when compiling the upload program: row 446, message: A newer version of data type /BIC/B0000788000 was
I've tried reactivating transfer structures and transfer rules but with no success. When I activate the transfer structures I can see in the status bar briefly a message refering "Activating Structure /BIC/B0000788000". I am assuming it's the technical name of the structure which supports the extraction.
Any ideas?
Thanks for the help.

OK, I can see your point. The Communication structure fields have data types, CHAR, CURR and DATS (those are the data types for the info-objects I am trying to load).
But if I try to assign the same data types to the objects of the transfer structure which match the flat file I get errors like "Invalid data type (DATS) for source systems of type Ext. System.". What I understand this means is that I cannot use data types other than CHAR in the flat file structure so how can I assign data from a CHAR flat file to a DATS destination object? Do I need some kind of conversion? How? Do I really need a routine in the transfer rules?

Error 8 when compiling the upload program: row

Error 8 when compiling the upload program: row
248, message: Data type /BIC/CCAWSAI_CID_TEXT was
found in a new
kindly help me out pls

Hi Raghu,
Error 8 Implies
The last words should be read as "was found in a newer version".
The system says that the active version of your Infosource is older then another version.
I'd recommend to delete Infosource - Source system assignment (with PSA tables etc.).
Then save (activate) the Infosource (communication structure). Then assign source system, create infopackage and load data again.
else..
Goto se38 and Run the program RS_TRANSTRU_ACTIVATE_ALL and relogin..
Plz look the link.
[Error when compiling the upload program (Message no. RSAR233) ]
Hope this helps...
Regards,
NR
Assign points if helpful...

Error 8 when compiling the upload program

When loading data to the Infocube it gives the following error
"Error 8 when compiling the upload
227, message: Data type /BIC/CCFBZ
found in a ne "
It doesnot go any further from thr infopackage also..

Error when compiling the upload program (Message no. RSAR233)

[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.

Which librarys are essential when compiling Oracle 10g OCCI program in CW9?

I'm using Mac OS X 10.3.6, gcc3.3, CodeWarrior 9.0, and installed XCode1.5 too.
I had installed Oracle Database 10g Client for Mac OS X fully.
I'm trying to build the demo of OCCI. I can run the'make -f demo_rdbms.mk occimb1' command
successfully, and generate a 'occimb1' execution file.
But when I build 'occimb1' demo with CodeWarrior, the statement 'Environment::createEnvironment()'
cause a error as below:
Link Error : undefined:
'_ZN6oracle4occi11Environment17createEnvironmentERKSsS4_NS1_4ModeEPvPFS6_S6_mEPFS6_S6_S6_
mEPFvS6_S6_E' (code)
Referenced from 'main' in occimb1.cpp
I had already added these lib: libclntsh.dylib.10.1, libocci.dylib.10.1, libnnz10.dylib, libociei.dylib.
Which librarys are essential when compiling Oracle 10g OCCI program in CW9?

Hi,
The same issue is faced by me when I was migrating my application from forms6i (oracle 8i) to forms 10g(oracle 10g).
Solution:
create a view based on the table on the other database (use db link)
now create a synonym using this view and make it public.
use this synonym in your form.
It looks like something weared but this worked !!
Try it !!

Linker error when compiling Fortran program

I have some problems when linking a Fortran program. The compiling (with gfortran) works without problems and produces (amongst others) several ".mod" files. As soon as the products are to be linked, these .mod-files provoke a "bad magic number (not a Mach-O file)" error from the linker.
I use gcc 4.3 with gfortran. Any ideas?
Powerbook G4 12", 1.33 GHz/MacBook Pro 2GHz Mac OS X (10.4.8)

Possibly, but the error doesn't come from gfortran itself, but from the linker (ld), so I don't see right now, why this should make a difference.
You think it is because these .mod-files are compiled incorrectly?

[Solved] Programs segfaults when compiled by makepkg

Similar Messages

Maybe you are looking for