bug-gnucobol
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [open-cobol-list] cobc linkage bug on Mint Linux ?


From: Patrick
Subject: Re: [open-cobol-list] cobc linkage bug on Mint Linux ?
Date: Fri, 19 Jul 2013 15:21:01 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7

I have run the commands that Brian asked and sent them to him in a PM. If anyone would like them too, please just drop me a line.

Thanks again everyone


On 7/19/2013 1:59 AM, Brian Tiffin wrote:
On 7/18/13, Patrick <address@hidden> wrote:
Hi Vince

Thanks for the reminder about this.

I just tried this on my virtualbox mint install and it did not help.

I also believe I tried this under debian stable without a GUI and it did
not work either(I can't absolutely remember). I don't know why
installing XFCE helped but things are now fine after I did.

Thanks again


On 7/18/2013 7:38 PM, Vincent Coen wrote:
Hi;

Did you remember to run ldconfig having added the cobol runtime path
to ld.so.conf

such as :

include /etc/ld.so.conf.d/*.conf

/usr/local/lib

/usr/local/lib/open-cobol-ce

Vince

On Thursday 18 Jul 2013 17:40:13 Patrick wrote:

Hi Michael, Hi Charles, thanks for responding to my post :)
Brian, I have been worry about wasting your time today(or more time),
now that I have had a moment to stop, I have loaded Mint 15, Cinnamon
desktop, on Virtualbox with QT interface(non free version)
After the virgin install I ran sudo apt-get install open-cobol
python-dev -y

I copied and pasted your program from the sourceforge page.
I tided up the syntax issues from copying.
I compiled it with cobc -x cobpy.cob -lpython2.7
It compiled.
At runtime it failed with the libcob cannot find module error.
I am pretty sure this is a bug now.

Patrick,

No worries.  If I can help, I will, or when I can't, I won't.  ;-)

Can you try ldd on the executable for me?

Here's some of the commands I use when hunting for link symbols.

nm -a

ldd

strings -(n) (where the -n limits by length of symbol you are looking
for, -7 say) pipe through grep across the library trees.

strace

Then it comes down to judicious use of LD_RUN_PATH, LD_LIBRARY_PATH,
COB_LIBRARY_PATH, COB_PRE_LOAD, and both -l (lower case ell) and -L
during compiles.

Once you track down library locations, in particular 32 bit and 64 bit
libraries can be a hassle, but I find that installing both x86_64 and
i686 doesn't seem to hurt, look to LD_RUN_PATH, set it to build in the
directories you usually need, compile cobc and you'll have a local
development compiler that is -l hassle free.

... Errr, never mind, that may be why your builds aren't working as
mine may have.  Skip that last bit of advice.  Look to LD_RUN_PATH and
COB_PRE_LOAD at application compile time and tweak the tectonics with
the right minus ellses (-l, -L)

On the topic of stable development systems, hmm.  I've trusted (and
borked) Debian, Fedora, Ubuntu.  For traveling, Knoppix, which is a
nice rescue stick to have around, regardless.

The worst days are the hangovers from wanting to hang out with Debian
Sid or Fedora nightly and some recent upstream sources of some
experiment, and getting a completely mangled package subsystem.

Other than that. Chin up, bad GNU/Linux programming days fade, rear,
and fade again.  :-)

Then it'll kick you right in the data sack, just like any OS will, and
make you sad.  So, I'm always prepared to lose today's stuff, and
hopefully mindful enough to limit it to only today.  (Fossil is my
preferred distributed revision control), but I do admit to it being
hopefully.

Trust to the Linux kernel to have some cool low level features that
can get you out of a jam.  Virtual consoles, Ctrl-Alt-F4 for the 4th,
Ubuntu gui's usually on F7.  Even when stuff goes right sideways,
there are probably Linux and GNU tools to assist getting clean
compiles.

Cheers,
Brian

On 7/18/13, Patrick <address@hidden> wrote:
Hi Vince

Thanks for the reminder about this.

I just tried this on my virtualbox mint install and it did not help.

I also believe I tried this under debian stable without a GUI and it did
not work either(I can't absolutely remember). I don't know why
installing XFCE helped but things are now fine after I did.

Thanks again


On 7/18/2013 7:38 PM, Vincent Coen wrote:
Hi;

Did you remember to run ldconfig having added the cobol runtime path
to ld.so.conf

such as :

include /etc/ld.so.conf.d/*.conf

/usr/local/lib

/usr/local/lib/open-cobol-ce

Vince

On Thursday 18 Jul 2013 17:40:13 Patrick wrote:

Hi Michael, Hi Charles, thanks for responding to my post :)
Brian, I have been worry about wasting your time today(or more time),
now that I have had a moment to stop, I have loaded Mint 15, Cinnamon
desktop, on Virtualbox with QT interface(non free version)
After the virgin install I ran sudo apt-get install open-cobol
python-dev -y

I copied and pasted your program from the sourceforge page.
I tided up the syntax issues from copying.
I compiled it with cobc -x cobpy.cob -lpython2.7
It compiled.
At runtime it failed with the libcob cannot find module error.
I am pretty sure this is a bug now.


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk


_______________________________________________
open-cobol-list mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/open-cobol-list




reply via email to

[Prev in Thread] Current Thread [Next in Thread]