Yes, please dig up and post a summary - otherwise this thread would be useless.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-10-14
Hi all-
re: ocesql from japan:
I am using fedora 32 to run ocesql. Windows instructions might
be different.
I ran into a few items that you may or may not run into with ocesql
from Japan.
When I was allmost finished building, I got the message multiple definitions.
It gave some lines and files affected. I just went in to the scanner
file named scanner.c and put externs and re ran make.
I caught holly hell with autoreconf msgs. What I did to fix that is there
is a file named configure.ac in ocesql. I think the step it acts
up on is autoreconf --force --install on these macros below.
I'd say I can't remember anything else unusual except getting the requirements
when the computer complains and in my instance mapping them with an
actual fedora package using dnf package manager.
I'd show you a screenshot but I already have one of those on my site
(of ocesql). The proof is in the japaneese on this one.
I hope that info helps if you run accross any of those situations on your linux system.
roboloki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have in /usr/local/bin a binary.
It took 10 men and a boy.
I think I just used all my powers of deductive reasoning.
Well at the expense of being awake tomorrow I will have pleasant cobol dreams.
If you wan t to here how I coerced it tomorrow I will try to dig up some stuff.
later,
roboloki
Yes, please dig up and post a summary - otherwise this thread would be useless.
Hi all-
re: ocesql from japan:
I am using fedora 32 to run ocesql. Windows instructions might
be different.
I ran into a few items that you may or may not run into with ocesql
from Japan.
When I was allmost finished building, I got the message multiple definitions.
It gave some lines and files affected. I just went in to the scanner
file named scanner.c and put externs and re ran make.
I caught holly hell with autoreconf msgs. What I did to fix that is there
is a file named configure.ac in ocesql. I think the step it acts
up on is autoreconf --force --install on these macros below.
I tweaked it:
AC_PREREQ([2.69])
AC_INIT([Open COBOL ESQL], [1.2], [opencobol@tsh-world.co.jp])
AC_CONFIG_SRCDIR([config.h.in])
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_AUX_DIR([.]) *
AM_INIT_AUTOMAKE
AC_CONFIG_MACRO_DIR([/usr/share/alocal]) *
The starred macros (you can strip out the stars) need to be there
to make autoreconf stop complaining. They weren't in my system in configure.ac.
remember to put entries in /etc/ld.so.conf.d if you need them.
I heard in linux you have to use autotools so I believe Simon
once said to run this command after installing autotools:
autoreconf --force --install
then you do your usual:
./configure
make
make install
Simon has very handy posts located at:
Simon's handy guide
I'd say I can't remember anything else unusual except getting the requirements
when the computer complains and in my instance mapping them with an
actual fedora package using dnf package manager.
I'd show you a screenshot but I already have one of those on my site
(of ocesql). The proof is in the japaneese on this one.
I hope that info helps if you run accross any of those situations on your linux system.
roboloki