SOLVED: Remedy API and gcc on Redhat Linux
Good morning: Using the changes to the Makefile shown below and copying the missing library files from ar_install_dir/approval/bin, I was able to compile and link the program driver. It works correctly. Despite what BMC told me via Maryville, I did not need to upgrade my gcc compiler. Thank you, thank you. Thorin From: Axton [mailto:axton.gr...@gmail.com] Sent: Saturday, August 22, 2009 3:17 AM Subject: Re: Remedy API and gcc on Redhat Linux ** Glad to hear you got it working; much easier than compiling a compiler and running into the same problem with the new compiler :) Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Sat, Aug 22, 2009 at 2:50 AM, Conny Martin conny.mar...@t-systems.com wrote: ** Axton, you're right, there is a mismatch. The CFLAGS settings tells gcc to generate 32-Bit object files. But in LDFLAGS -m32 wasn't set. The linker is then trying to generate a 64-Bit binary. But libar.so is definitely a 32-bit binary. The 64 bit version is named libar_lx64.so Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] Im Auftrag von Axton Gesendet: Freitag, 21. August 2009 21:36 An: arslist@ARSLIST.ORG Betreff: Re: Remedy API and gcc on Redhat Linux ** The libraries are provided in both 32-bit and 64-bit on the non-Windows releases of ARS 7.5. Page 64 provides additional information. http://documents.bmc.com/supportu/documents/53/84/95384/95384.pdf This looks like a mismatch between the 32/64 bit api and the CFLAGS you are using. See Lyle's message on how to straighten it out and set the flags properly. Axton Grams On Fri, Aug 21, 2009 at 1:40 PM, Conny Martin conny.mar...@t-systems.com wrote: ** libar.so is 32 bit-binary. The Makefile provided by BMC won't work unless you do a little customisation this one works for me. # # Parameters. PROGRAM = driver SOURCES = api.c get.c main.c print.c util.c OBJECTS = api.o get.o main.o print.o util.o # Compiler flags. CC = cc CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double CPPFLAGS = -I../include -I../../include LDFLAGS = -m32 -L../lib -L../../lib LDLIBS = -lar -lnsl -lpthread -lncurses -ldl -licuucbmc -licui18nbmc -licudatabmc # Standard targets. all: $(PROGRAM) objects: $(OBJECTS) $(PROGRAM): $(OBJECTS) $(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS) clean: $(RM) $(PROGRAM) $(OBJECTS) core --- There are also some libs missing in ar_install_dir/api/lib. So I copied them from ar_install_dir/bin libicudatabmc.so libicudatabmc.so.32 libicui18nbmc.so libicui18nbmc.so.32 libicuucbmc.so libicuucbmc.so.32 HTH Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] Im Auftrag von Lyle Taylor Gesendet: Freitag, 21. August 2009 18:56 An: arslist@ARSLIST.ORG Betreff: Re: Remedy API and gcc on Redhat Linux ** In your build directory, run the following command and send us the output: file ../../lib/libar.so Your build options seem to be telling it to build a 32-bit executable, but 75 is 64-bit on Linux. The command above will verify whether libar.so is a 32 or 64-bit binary. If it's 64-bit, then change -m32 to -m64 in your
AW: Remedy API and gcc on Redhat Linux
Axton, you're right, there is a mismatch. The CFLAGS settings tells gcc to generate 32-Bit object files. But in LDFLAGS -m32 wasn't set. The linker is then trying to generate a 64-Bit binary. But libar.so is definitely a 32-bit binary. The 64 bit version is named libar_lx64.so Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] Im Auftrag von Axton Gesendet: Freitag, 21. August 2009 21:36 An: arslist@ARSLIST.ORG Betreff: Re: Remedy API and gcc on Redhat Linux ** The libraries are provided in both 32-bit and 64-bit on the non-Windows releases of ARS 7.5. Page 64 provides additional information. http://documents.bmc.com/supportu/documents/53/84/95384/95384.pdf This looks like a mismatch between the 32/64 bit api and the CFLAGS you are using. See Lyle's message on how to straighten it out and set the flags properly. Axton Grams On Fri, Aug 21, 2009 at 1:40 PM, Conny Martin conny.mar...@t-systems.com wrote: ** libar.so is 32 bit-binary. The Makefile provided by BMC won't work unless you do a little customisation this one works for me. # # Parameters. PROGRAM = driver SOURCES = api.c get.c main.c print.c util.c OBJECTS = api.o get.o main.o print.o util.o # Compiler flags. CC = cc CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double CPPFLAGS = -I../include -I../../include LDFLAGS = -m32 -L../lib -L../../lib LDLIBS = -lar -lnsl -lpthread -lncurses -ldl -licuucbmc -licui18nbmc -licudatabmc # Standard targets. all: $(PROGRAM) objects: $(OBJECTS) $(PROGRAM): $(OBJECTS) $(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS) clean: $(RM) $(PROGRAM) $(OBJECTS) core --- There are also some libs missing in ar_install_dir/api/lib. So I copied them from ar_install_dir/bin libicudatabmc.so libicudatabmc.so.32 libicui18nbmc.so libicui18nbmc.so.32 libicuucbmc.so libicuucbmc.so.32 HTH Kind Regards Conny Von: Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] Im Auftrag von Lyle Taylor Gesendet: Freitag, 21. August 2009 18:56 An: arslist@ARSLIST.ORG Betreff: Re: Remedy API and gcc on Redhat Linux ** In your build directory, run the following command and send us the output: file ../../lib/libar.so Your build options seem to be telling it to build a 32-bit executable, but 75 is 64-bit on Linux. The command above will verify whether libar.so is a 32 or 64-bit binary. If it's 64-bit, then change -m32 to -m64 in your Makefile, do a make clean and then try building it again. Lyle ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are Outlook.jpg
Re: Remedy API and gcc on Redhat Linux
Glad to hear you got it working; much easier than compiling a compiler and running into the same problem with the new compiler :) Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Sat, Aug 22, 2009 at 2:50 AM, Conny Martin conny.mar...@t-systems.comwrote: ** Axton, you're right, there is a mismatch. The CFLAGS settings tells gcc to generate 32-Bit object files. But in LDFLAGS -m32 wasn't set. The linker is then trying to generate a 64-Bit binary. But libar.so is definitely a 32-bit binary. The 64 bit version is named libar_lx64.so Kind Regards Conny -- *Von:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *Im Auftrag von *Axton *Gesendet:* Freitag, 21. August 2009 21:36 *An:* arslist@ARSLIST.ORG *Betreff:* Re: Remedy API and gcc on Redhat Linux ** The libraries are provided in both 32-bit and 64-bit on the non-Windows releases of ARS 7.5. Page 64 provides additional information. http://documents.bmc.com/supportu/documents/53/84/95384/95384.pdf This looks like a mismatch between the 32/64 bit api and the CFLAGS you are using. See Lyle's message on how to straighten it out and set the flags properly. Axton Grams On Fri, Aug 21, 2009 at 1:40 PM, Conny Martin conny.mar...@t-systems.comwrote: ** libar.so is 32 bit-binary. The Makefile provided by BMC won't work unless you do a little customisation this one works for me. # # Parameters. PROGRAM = driver SOURCES = api.c get.c main.c print.c util.c OBJECTS = api.o get.o main.o print.o util.o # Compiler flags. CC = cc CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double CPPFLAGS = -I../include -I../../include LDFLAGS = -m32 -L../lib -L../../lib LDLIBS = -lar -lnsl -lpthread -lncurses -ldl -licuucbmc -licui18nbmc -licudatabmc # Standard targets. all: $(PROGRAM) objects: $(OBJECTS) $(PROGRAM): $(OBJECTS) $(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS) clean: $(RM) $(PROGRAM) $(OBJECTS) core --- There are also some libs missing in ar_install_dir/api/lib. So I copied them from ar_install_dir/bin libicudatabmc.so libicudatabmc.so.32 libicui18nbmc.so libicui18nbmc.so.32 libicuucbmc.so libicuucbmc.so.32 HTH Kind Regards Conny -- *Von:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *Im Auftrag von *Lyle Taylor *Gesendet:* Freitag, 21. August 2009 18:56 *An:* arslist@ARSLIST.ORG *Betreff:* Re: Remedy API and gcc on Redhat Linux ** In your build directory, run the following command and send us the output: file ../../lib/libar.so Your build options seem to be telling it to build a 32-bit executable, but 75 is 64-bit on Linux. The command above will verify whether libar.so is a 32 or 64-bit binary. If it’s 64-bit, then change -m32 to -m64 in your Makefile, do a make clean and then try building it again. Lyle _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Remedy API and gcc on Redhat Linux
Dear Axton:
Here is a listing of my Makefile (same as out-of-the-box), the run,
and a directory listing after the run.
Thorin
remedy75{xxremedy}57: more Makefile
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lcurses -ldl
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
___
remedy75{xxremedy}58: make
cc -o driver api.o get.o main.o print.o util.o -L../lib -L../../lib -lar
-lnsl -lpthread -lcurses -ldl
/usr/bin/ld: skipping incompatible ../../lib/libar.so when searching for
-lar
/usr/bin/ld: skipping incompatible ../../lib/libar.a when searching for
-lar
/usr/bin/ld: cannot find -lar
collect2: ld returned 1 exit status
make: *** [driver] Error 1
___
remedy75{xxremedy}59: ls -l
total 1880
-rwxr-xr-x 1 xxremedy ftp 411821 Mar 10 04:03 api.c*
-rwxr-xr-x 1 xxremedy ftp 5906 Mar 10 04:03 api.h*
-rw-r--r-- 1 xxremedy ftp 314412 Aug 21 11:22 api.o
-rwxr-xr-x 1 xxremedy ftp 210747 Mar 10 04:03 get.c*
-rwxr-xr-x 1 xxremedy ftp 6902 Aug 7 15:08 get.h*
-rw-r--r-- 1 xxremedy ftp 153016 Aug 21 11:22 get.o
-rwxr-xr-x 1 xxremedy ftp 5727 Mar 10 04:03 globals.h*
-rwxr-xr-x 1 xxremedy ftp 65161 Aug 17 13:30 main.c*
-rwxr-xr-x 1 xxremedy ftp 19440 Mar 10 04:03 main.h*
-rw-r--r-- 1 xxremedy ftp 47636 Aug 21 11:22 main.o
-rwxr-xr-x 1 xxremedy ftp509 Aug 21 11:22 Makefile*
-rwxr-xr-x 1 xxremedy ftp 282759 Mar 10 04:03 print.c*
-rwxr-xr-x 1 xxremedy ftp 7934 Mar 10 04:03 print.h*
-rw-r--r-- 1 xxremedy ftp 200340 Aug 21 11:22 print.o
-rwxr-xr-x 1 xxremedy ftp 46470 Aug 14 19:24 util.c*
-rwxr-xr-x 1 xxremedy ftp 2054 Mar 10 04:03 util.h*
-rw-r--r-- 1 xxremedy ftp 31184 Aug 21 11:22 util.o
-rw-r--r-- 1 xxremedy ftp 1674 Aug 14 19:21 wfd_shared.h
rmdy-papr02.comp.wepco.com{xxremedy}60:
From: Axton [mailto:axton.gr...@gmail.com]
Sent: Thursday, August 20, 2009 7:27 PM
Subject: Re: Remedy API and gcc on Redhat Linux
** I'm not sure why you would need 4.4.1. Why don't you post the
compiler/linker output and the build options.
Axton Grams
The opinions, statements, and/or suggested courses of action expressed
in this E-mail do not necessarily reflect those of BMC Software, Inc. My
voluntary participation in this forum is not intended to convey a role
as a spokesperson, liaison or public relations representative for BMC
Software, Inc.
On Thu, Aug 20, 2009 at 4:24 PM, Marty.Thorin
thorin.ma...@we-energies.com wrote:
**
Good afternoon:
I tried to compile the out-of-the-box program 'driver'.
It compiled but would not link. When I asked BMC I was informed my copy
of gcc (3.4.6) is too old and I need to upgrade to 4.4.1.
I downloaded 4.4.1 today but it looks like I need to build the
gcc compiler!?! This is not a small task. So I figure I must have done
something wrong. Does anyone know where to download gcc 4.4.1 for
Redhat in a tar or zip file?
Thank you,
Thorin
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the
Answers Are_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers
Are_
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Remedy API and gcc on Redhat Linux
In your build directory, run the following command and send us the output:
file ../../lib/libar.so
Your build options seem to be telling it to build a 32-bit executable, but 75
is 64-bit on Linux. The command above will verify whether libar.so is a 32 or
64-bit binary. If it's 64-bit, then change -m32 to -m64 in your Makefile, do a
make clean and then try building it again.
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Marty.Thorin
Sent: Friday, August 21, 2009 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy API and gcc on Redhat Linux
**
Dear Axton:
Here is a listing of my Makefile (same as out-of-the-box), the run, and a
directory listing after the run.
Thorin
remedy75{xxremedy}57: more Makefile
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lcurses -ldl
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
___
remedy75{xxremedy}58: make
cc -o driver api.o get.o main.o print.o util.o -L../lib -L../../lib -lar -lnsl
-lpthread -lcurses -ldl
/usr/bin/ld: skipping incompatible ../../lib/libar.so when searching for -lar
/usr/bin/ld: skipping incompatible ../../lib/libar.a when searching for -lar
/usr/bin/ld: cannot find -lar
collect2: ld returned 1 exit status
make: *** [driver] Error 1
___
remedy75{xxremedy}59: ls -l
total 1880
-rwxr-xr-x 1 xxremedy ftp 411821 Mar 10 04:03 api.c*
-rwxr-xr-x 1 xxremedy ftp 5906 Mar 10 04:03 api.h*
-rw-r--r-- 1 xxremedy ftp 314412 Aug 21 11:22 api.o
-rwxr-xr-x 1 xxremedy ftp 210747 Mar 10 04:03 get.c*
-rwxr-xr-x 1 xxremedy ftp 6902 Aug 7 15:08 get.h*
-rw-r--r-- 1 xxremedy ftp 153016 Aug 21 11:22 get.o
-rwxr-xr-x 1 xxremedy ftp 5727 Mar 10 04:03 globals.h*
-rwxr-xr-x 1 xxremedy ftp 65161 Aug 17 13:30 main.c*
-rwxr-xr-x 1 xxremedy ftp 19440 Mar 10 04:03 main.h*
-rw-r--r-- 1 xxremedy ftp 47636 Aug 21 11:22 main.o
-rwxr-xr-x 1 xxremedy ftp509 Aug 21 11:22 Makefile*
-rwxr-xr-x 1 xxremedy ftp 282759 Mar 10 04:03 print.c*
-rwxr-xr-x 1 xxremedy ftp 7934 Mar 10 04:03 print.h*
-rw-r--r-- 1 xxremedy ftp 200340 Aug 21 11:22 print.o
-rwxr-xr-x 1 xxremedy ftp 46470 Aug 14 19:24 util.c*
-rwxr-xr-x 1 xxremedy ftp 2054 Mar 10 04:03 util.h*
-rw-r--r-- 1 xxremedy ftp 31184 Aug 21 11:22 util.o
-rw-r--r-- 1 xxremedy ftp 1674 Aug 14 19:21 wfd_shared.h
rmdy-papr02.comp.wepco.com{xxremedy}60:
From: Axton [mailto:axton.gr...@gmail.com]
Sent: Thursday, August 20, 2009 7:27 PM
Subject: Re: Remedy API and gcc on Redhat Linux
** I'm not sure why you would need 4.4.1. Why don't you post the
compiler/linker output and the build options.
Axton Grams
The opinions, statements, and/or suggested courses of action expressed in this
E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary
participation in this forum is not intended to convey a role as a spokesperson,
liaison or public relations representative for BMC Software, Inc.
On Thu, Aug 20, 2009 at 4:24 PM, Marty.Thorin
thorin.ma...@we-energies.commailto:thorin.ma...@we-energies.com wrote:
**
Good afternoon:
I tried to compile the out-of-the-box program 'driver'. It compiled
but would not link. When I asked BMC I was informed my copy of gcc (3.4.6) is
too old and I need to upgrade to 4.4.1.
I downloaded 4.4.1 today but it looks like I need to build the gcc compiler!?!
This is not a small task. So I figure I must have done something wrong. Does
anyone know where to download gcc 4.4.1 for Redhat in a tar or zip file?
Thank you,
Thorin
_Platinum Sponsor: rmisoluti...@verizon.netmailto:rmisoluti...@verizon.net
ARSlist: Where the Answers Are_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy all
copies of the original message.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
AW: Remedy API and gcc on Redhat Linux
libar.so is 32 bit-binary. The Makefile provided by BMC won't work
unless you do a little customisation
this one works for me.
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -m32 -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lncurses -ldl -licuucbmc -licui18nbmc
-licudatabmc
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
---
There are also some libs missing in ar_install_dir/api/lib. So I
copied them from ar_install_dir/bin
libicudatabmc.so
libicudatabmc.so.32
libicui18nbmc.so
libicui18nbmc.so.32
libicuucbmc.so
libicuucbmc.so.32
HTH
Kind Regards Conny
Von: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] Im Auftrag von Lyle Taylor
Gesendet: Freitag, 21. August 2009 18:56
An: arslist@ARSLIST.ORG
Betreff: Re: Remedy API and gcc on Redhat Linux
**
In your build directory, run the following command and send us the
output:
file ../../lib/libar.so
Your build options seem to be telling it to build a 32-bit executable,
but 75 is 64-bit on Linux. The command above will verify whether
libar.so is a 32 or 64-bit binary. If it's 64-bit, then change -m32 to
-m64 in your Makefile, do a make clean and then try building it again.
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Marty.Thorin
Sent: Friday, August 21, 2009 10:28 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy API and gcc on Redhat Linux
**
Dear Axton:
Here is a listing of my Makefile (same as out-of-the-box), the run,
and a directory listing after the run.
Thorin
remedy75{xxremedy}57: more Makefile
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lcurses -ldl
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
___
remedy75{xxremedy}58: make
cc -o driver api.o get.o main.o print.o util.o -L../lib -L../../lib -lar
-lnsl -lpthread -lcurses -ldl
/usr/bin/ld: skipping incompatible ../../lib/libar.so when searching for
-lar
/usr/bin/ld: skipping incompatible ../../lib/libar.a when searching for
-lar
/usr/bin/ld: cannot find -lar
collect2: ld returned 1 exit status
make: *** [driver] Error 1
___
remedy75{xxremedy}59: ls -l
total 1880
-rwxr-xr-x 1 xxremedy ftp 411821 Mar 10 04:03 api.c*
-rwxr-xr-x 1 xxremedy ftp 5906 Mar 10 04:03 api.h*
-rw-r--r-- 1 xxremedy ftp 314412 Aug 21 11:22 api.o
-rwxr-xr-x 1 xxremedy ftp 210747 Mar 10 04:03 get.c*
-rwxr-xr-x 1 xxremedy ftp 6902 Aug 7 15:08 get.h*
-rw-r--r-- 1 xxremedy ftp 153016 Aug 21 11:22 get.o
-rwxr-xr-x 1 xxremedy ftp 5727 Mar 10 04:03 globals.h*
-rwxr-xr-x 1 xxremedy ftp 65161 Aug 17 13:30 main.c*
-rwxr-xr-x 1 xxremedy ftp 19440 Mar 10 04:03 main.h*
-rw-r--r-- 1 xxremedy ftp 47636 Aug 21 11:22 main.o
-rwxr-xr-x 1 xxremedy ftp509 Aug 21 11:22 Makefile*
-rwxr-xr-x 1 xxremedy ftp 282759 Mar 10 04:03 print.c*
-rwxr-xr-x 1 xxremedy ftp 7934 Mar 10 04:03 print.h*
-rw-r--r-- 1 xxremedy ftp 200340 Aug 21 11:22 print.o
-rwxr-xr-x 1 xxremedy ftp 46470 Aug 14 19:24 util.c*
-rwxr-xr-x 1 xxremedy ftp 2054 Mar 10 04:03 util.h*
-rw-r--r-- 1 xxremedy ftp 31184 Aug 21 11:22 util.o
-rw-r--r-- 1 xxremedy ftp 1674 Aug 14 19:21 wfd_shared.h
rmdy-papr02.comp.wepco.com{xxremedy}60:
From: Axton [mailto:axton.gr...@gmail.com]
Sent: Thursday, August 20, 2009 7:27 PM
Subject: Re: Remedy API and gcc on Redhat Linux
** I'm not sure why you would need 4.4.1. Why don't you post the
compiler/linker output and the build options.
Axton Grams
The opinions, statements, and/or suggested courses of action expressed
in this E-mail do not necessarily reflect those of BMC Software, Inc. My
voluntary participation in this forum is not intended to convey a role
as a spokesperson, liaison or public relations representative for BMC
Software, Inc
Re: Remedy API and gcc on Redhat Linux
The libraries are provided in both 32-bit and 64-bit on the non-Windows
releases of ARS 7.5.
Page 64 provides additional information.
http://documents.bmc.com/supportu/documents/53/84/95384/95384.pdf
This looks like a mismatch between the 32/64 bit api and the CFLAGS you are
using. See Lyle's message on how to straighten it out and set the flags
properly.
Axton Grams
On Fri, Aug 21, 2009 at 1:40 PM, Conny Martin conny.mar...@t-systems.comwrote:
** libar.so is 32 bit-binary. The Makefile provided by BMC won't work
unless you do a little customisation
this one works for me.
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -m32 -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lncurses -ldl -licuucbmc -licui18nbmc
-licudatabmc
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
---
There are also some libs missing in ar_install_dir/api/lib. So I copied
them from ar_install_dir/bin
libicudatabmc.so
libicudatabmc.so.32
libicui18nbmc.so
libicui18nbmc.so.32
libicuucbmc.so
libicuucbmc.so.32
HTH
Kind Regards Conny
--
*Von:* Action Request System discussion list(ARSList) [mailto:
arsl...@arslist.org] *Im Auftrag von *Lyle Taylor
*Gesendet:* Freitag, 21. August 2009 18:56
*An:* arslist@ARSLIST.ORG
*Betreff:* Re: Remedy API and gcc on Redhat Linux
**
In your build directory, run the following command and send us the output:
file ../../lib/libar.so
Your build options seem to be telling it to build a 32-bit executable, but
75 is 64-bit on Linux. The command above will verify whether libar.so is a
32 or 64-bit binary. If it’s 64-bit, then change -m32 to -m64 in your
Makefile, do a make clean and then try building it again.
Lyle
*From:* Action Request System discussion list(ARSList) [mailto:
arsl...@arslist.org] *On Behalf Of *Marty.Thorin
*Sent:* Friday, August 21, 2009 10:28 AM
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Remedy API and gcc on Redhat Linux
**
Dear Axton:
Here is a listing of my Makefile (same as out-of-the-box), the run,
and a directory listing after the run.
Thorin
remedy75{xxremedy}57: more Makefile
#
# Parameters.
PROGRAM = driver
SOURCES = api.c get.c main.c print.c util.c
OBJECTS = api.o get.o main.o print.o util.o
# Compiler flags.
CC = cc
CFLAGS = -m32 -g -DDEBUG -D_REENTRANT -malign-double
CPPFLAGS = -I../include -I../../include
LDFLAGS = -L../lib -L../../lib
LDLIBS = -lar -lnsl -lpthread -lcurses -ldl
# Standard targets.
all: $(PROGRAM)
objects: $(OBJECTS)
$(PROGRAM): $(OBJECTS)
$(CC) -o $(PROGRAM) $(OBJECTS) $(LDFLAGS) $(LDLIBS)
clean:
$(RM) $(PROGRAM) $(OBJECTS) core
___
remedy75{xxremedy}58: make
cc -o driver api.o get.o main.o print.o util.o -L../lib -L../../lib -lar
-lnsl -lpthread -lcurses -ldl
/usr/bin/ld: skipping incompatible ../../lib/libar.so when searching for
-lar
/usr/bin/ld: skipping incompatible ../../lib/libar.a when searching for
-lar
/usr/bin/ld: cannot find -lar
collect2: ld returned 1 exit status
make: *** [driver] Error 1
___
remedy75{xxremedy}59: ls -l
total 1880
-rwxr-xr-x 1 xxremedy ftp 411821 Mar 10 04:03 api.c*
-rwxr-xr-x 1 xxremedy ftp 5906 Mar 10 04:03 api.h*
-rw-r--r-- 1 xxremedy ftp 314412 Aug 21 11:22 api.o
-rwxr-xr-x 1 xxremedy ftp 210747 Mar 10 04:03 get.c*
-rwxr-xr-x 1 xxremedy ftp 6902 Aug 7 15:08 get.h*
-rw-r--r-- 1 xxremedy ftp 153016 Aug 21 11:22 get.o
-rwxr-xr-x 1 xxremedy ftp 5727 Mar 10 04:03 globals.h*
-rwxr-xr-x 1 xxremedy ftp 65161 Aug 17 13:30 main.c*
-rwxr-xr-x 1 xxremedy ftp 19440 Mar 10 04:03 main.h*
-rw-r--r-- 1 xxremedy ftp 47636 Aug 21 11:22 main.o
-rwxr-xr-x 1 xxremedy ftp509 Aug 21 11:22 Makefile*
-rwxr-xr-x 1 xxremedy ftp 282759 Mar 10 04:03 print.c*
-rwxr-xr-x 1 xxremedy ftp 7934 Mar 10 04:03 print.h*
-rw-r--r-- 1 xxremedy ftp 200340 Aug 21 11:22 print.o
-rwxr-xr-x 1 xxremedy ftp 46470 Aug 14 19:24 util.c*
-rwxr-xr-x 1 xxremedy ftp 2054 Mar 10 04:03 util.h*
-rw-r--r-- 1 xxremedy ftp 31184 Aug 21 11:22 util.o
-rw-r--r-- 1 xxremedy ftp 1674 Aug 14 19:21 wfd_shared.h
rmdy-papr02.comp.wepco.com{xxremedy}60:
--
*From
Remedy API and gcc on Redhat Linux
Good afternoon: I tried to compile the out-of-the-box program 'driver'. It compiled but would not link. When I asked BMC I was informed my copy of gcc (3.4.6) is too old and I need to upgrade to 4.4.1. I downloaded 4.4.1 today but it looks like I need to build the gcc compiler!?! This is not a small task. So I figure I must have done something wrong. Does anyone know where to download gcc 4.4.1 for Redhat in a tar or zip file? Thank you, Thorin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Remedy API and gcc on Redhat Linux
Building the compiler is actually not that difficult. You just need to make sure that you get your options right when you run the configure command that generates the Makefiles (e.g., where to install it, what modules - compilers - to include with it, etc.). Once you determine what options you need, you run the configure command with the appropriate options, and that builds the Makefiles. You then run make bootstrap (or at least, that's what you used to do to build the compiler). That will take a while (it builds the compiler 2-3 times - once with your current compiler, then again with itself). Once it's built, you might be able to run make test to have it run its regression test suite, but you'd have to take a look at the current docs to see. After that, you run make install, and it will install it. If you do decide to do that, you probably don't want to overwrite your system compiler. I would recommend installing it either into another directory, perhaps something like /usr/local/gcc4 or somewhere under your home directory, if you'll be the only one using it. Using it after that is mostly a matter of making sure that the new compiler comes first in your PATH. For example, /usr/local/gcc4/bin:$PATH. That way, when you go to build things, it will use the new compiler instead of the system compiler. Otherwise, you may be able to find an RPM of the compiler for Red Hat. It's possible, though, that if you're on an older version of RedHat, and the build that you find was built for a newer version of RedHat, you could have issues with dependent libraries. If that's the case, your safest bet is to build it yourself. The primary difficulty you could run into while building it (if you decide to go that route), besides just determining the correct options, could be that it may require newer versions of some libraries and/or utilities on your system. If so, you would need to upgrade those as well. For example, certain versions of GCC require certain versions of GNU binutils. When you run the configure script, it will verify that you have usable versions of everything and will tell you if you don't, however. Lyle From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Marty.Thorin Sent: Thursday, August 20, 2009 3:24 PM To: arslist@ARSLIST.ORG Subject: Remedy API and gcc on Redhat Linux ** Good afternoon: I tried to compile the out-of-the-box program 'driver'. It compiled but would not link. When I asked BMC I was informed my copy of gcc (3.4.6) is too old and I need to upgrade to 4.4.1. I downloaded 4.4.1 today but it looks like I need to build the gcc compiler!?! This is not a small task. So I figure I must have done something wrong. Does anyone know where to download gcc 4.4.1 for Redhat in a tar or zip file? Thank you, Thorin _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Remedy API and gcc on Redhat Linux
I'm not sure why you would need 4.4.1. Why don't you post the compiler/linker output and the build options. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Thu, Aug 20, 2009 at 4:24 PM, Marty.Thorin thorin.ma...@we-energies.comwrote: ** Good afternoon: I tried to compile the out-of-the-box program 'driver'. It compiled but would not link. When I asked BMC I was informed my copy of gcc (3.4.6) is too old and I need to upgrade to 4.4.1. I downloaded 4.4.1 today but it looks like I need to build the gcc compiler!?! This is not a small task. So I figure I must have done something wrong. Does anyone know where to download gcc 4.4.1 for Redhat in a tar or zip file? Thank you, Thorin _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
