I thought I'd give vmware a try, and installed a 30 day evaluation rpm of VMware Workstation 4.5.2 build-884 using yast. No problems there. However, when I attempt to start vmware I'm told to run vmware-config.pl which produces the following output: linux:~ # vmware-config.pl Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitordone Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Workstationis suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] yes Using compiler "/usr/bin/gcc". Use environment variable CCto override. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] /usr/src/linux/include // I was unsure about // this Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24' Makefile:465: .config: No such file or directory WARNING: Symbol version dump /usr/src/linux-2.6.8-24/Module.symvers is missing, modules will have CONFIG_MODVERSIONSdisabled. CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o /bin/sh: scripts/basic/fixdep: No such file or directory make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.8-24' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config2/vmmon-only' Unable to build the vmmon module. ------- All of which is a little over my head. Have I made some obvious error?
On Saturday 06 November 2004 2:42 pm, Jake wrote:
I thought I'd give vmware a try, and installed a 30 day evaluation rpm of VMware Workstation 4.5.2 build-884 using yast. No problems there. However, when I attempt to start vmware I'm told to run vmware-config.pl which produces the following output:
snip <
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24' Makefile:465: .config: No such file or directory ^^^^^^^^^^^^^^^ Install the kernel-source files through YaST. Then try again.
All of which is a little over my head. Have I made some obvious error?
Yes. You didn't install the kernel-source rpm. It isn't installed by default so you'd have to manually select it or know that you wanted it installed. Stan
On Saturday 06 November 2004 22:19, Stan Glasoe wrote:
On Saturday 06 November 2004 2:42 pm, Jake wrote:
I thought I'd give vmware a try, and installed a 30 day evaluation rpm of VMware Workstation 4.5.2 build-884 using yast. No problems there. However, when I attempt to start vmware I'm told to run vmware-config.pl which produces the following output:
snip <
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24' Makefile:465: .config: No such file or directory
^^^^^^^^^^^^^^^ Install the kernel-source files through YaST. Then try again.
That is just the first step, and is not enough: rpm -Uhv kernel-syms-2.6.8-24.i586.rpm cd /usr/src/linux cp ../linux-obj/i386/default/.config . cp ../linux-obj/i386/default/Module.symvers . make prepare vmware-config.pl I just did this, and the compilation went without any error. Cheers, Leen
On Saturday, 6 November 2004 21.42, Jake wrote:
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24' Makefile:465: .config: No such file or directory
WARNING: Symbol version dump /usr/src/linux-2.6.8-24/Module.symvers is missing, modules will have CONFIG_MODVERSIONSdisabled.
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o /bin/sh: scripts/basic/fixdep: No such file or directory make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.8-24' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config2/vmmon-only' Unable to build the vmmon module. -------
All of which is a little over my head. Have I made some obvious error?
Well, it's obvious if you know it :) Before you compile something that uses the kernel sources, you need to prepare them. So cd /usr/src/linux make cloneconfig make prepare Then try the vmware build again
On Saturday 06 November 2004 21:43, Anders Johansson wrote:
Before you compile something that uses the kernel sources, you need to prepare them. So
cd /usr/src/linux make cloneconfig make prepare
Then try the vmware build again
Thanks very much, that's what I needed. Now off to read the extensive documentation on how to use it.
On Sat, 6 Nov 2004 20:42:56 +0000, you wrote:
I thought I'd give vmware a try, and installed a 30 day evaluation rpm of VMware Workstation 4.5.2 build-884 using yast. No problems there. However, when I attempt to start vmware I'm told to run vmware-config.pl which produces the following output:
linux:~ # vmware-config.pl Making sure services for VMware Workstation are stopped.
Stopping VMware services: Virtual machine monitordone
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstationis suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] yes
Using compiler "/usr/bin/gcc". Use environment variable CCto override.
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] /usr/src/linux/include // I was unsure about // this
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config2/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24' Makefile:465: .config: No such file or directory
WARNING: Symbol version dump /usr/src/linux-2.6.8-24/Module.symvers is missing, modules will have CONFIG_MODVERSIONSdisabled.
CC [M] /tmp/vmware-config2/vmmon-only/linux/driver.o /bin/sh: scripts/basic/fixdep: No such file or directory make[2]: *** [/tmp/vmware-config2/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config2/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.8-24' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config2/vmmon-only' Unable to build the vmmon module. -------
All of which is a little over my head. Have I made some obvious error?
Currently running vmware 4.5.2(8848) on SuSE 9.2 Professional (kernel 2.6.8-24.3). Works fine. As usual, you need to run thru the kernel build procedure (no changes are needed) in order to create some intermediate files (I suspect the sym tables) that don't actually ship with SuSE. cd /usr/src/linux make oldconfig make bzImage make modules You can skip the installation steps (modules_install and install) if you want. After you do this, install vmware - it works great. Mike- -- If you can keep your head while those around you are losing theirs... You may have a great career as a network administrator ahead! -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
On Sun, Nov 07, 2004 at 09:57:14AM -0500, Michael W Cocke wrote:
cd /usr/src/linux make oldconfig make bzImage make modules
You can skip the installation steps (modules_install and install) if you want. After you do this, install vmware - it works great.
Actually, the necessary and sufficient steps on SUSE are: make cloneconfig make prepare vmware-config.pl Much faster than bzImage and modules. Regards, -Kastus
On Monday 08 November 2004 8:48 am, Kastus wrote:
On Sun, Nov 07, 2004 at 09:57:14AM -0500, Michael W Cocke wrote:
cd /usr/src/linux make oldconfig make bzImage make modules
You can skip the installation steps (modules_install and install) if you want. After you do this, install vmware - it works great.
Actually, the necessary and sufficient steps on SUSE are:
make cloneconfig make prepare vmware-config.pl
Much faster than bzImage and modules.
Regards, -Kastus
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module. Should I have run make modules and make modules-install after make cloneconfig and make prepare? I seem to recall some earlier discussion, that I did not save, about there being an appropriate module/better module already included in SuSE and to use this instead. Is this so? Where and how? Thanks for any assistance. Richard
On Sun, Dec 12, 2004 at 03:18:00PM -0800, Richard wrote:
On Monday 08 November 2004 8:48 am, Kastus wrote:
Actually, the necessary and sufficient steps on SUSE are:
make cloneconfig make prepare vmware-config.pl
Much faster than bzImage and modules.
Regards, -Kastus
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module.
What errors did you get?
Should I have run make modules and make modules-install after make cloneconfig and make prepare?
No, these steps are not needed.
I seem to recall some earlier discussion, that I did not save, about there being an appropriate module/better module already included in SuSE and to use this instead. Is this so? Where and how? Thanks for any assistance. Richard
There are no ready vmware modules included in 9.2. Moreover, vmware complaine about kernel version in 9.2 but runs fine. Worked for me on 4 systems already. Make sure that you have kernel-syms and kernel-source installed. (the latest are -2.6.8-24.5) Regards, -Kastus
<snip>
What errors did you get?
Should I have run make modules and make modules-install after make cloneconfig and make prepare?
No, these steps are not needed.
I seem to recall some earlier discussion, that I did not save, about there being an appropriate module/better module already included in SuSE and to use this instead. Is this so? Where and how? Thanks for any assistance. Richard
There are no ready vmware modules included in 9.2. Moreover, vmware complaine about kernel version in 9.2 but runs fine.
Worked for me on 4 systems already.
Make sure that you have kernel-syms and kernel-source installed. (the latest are -2.6.8-24.5)
I did not recall installing kernel-syms, but had installed kernel-source. I went back to DVD, installed kernel-syms, then did online update to ensure both kernel-source and kernel-syms were current, same (2.6.8-24.5-default, confirmed by uname -a). I then did make cloneconfig, make prepare, then ran vmware-config.pl. Again refuse to complete process. Error report follows: Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config4/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24.5' WARNING: Symbol version dump /usr/src/linux-2.6.8-24.5/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled. CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o /tmp/vmware-config4/vmmon-only/linux/hostif.c: In function `MapCrossPage': /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: `PAGE_KERNEL_EXECUTABLE' undeclared (first use in this function) /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: (Each undeclared identifier is reported only once /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: for each function it appears in.) make[2]: *** [/tmp/vmware-config4/vmmon-only/linux/hostif.o] Error 1 make[1]: *** [_module_/tmp/vmware-config4/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.8-24.5' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config4/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html". Execution aborted. I did not see an obvious location for Module.symvers above and am not sure where to go if I did find it, except maybe copy to /usr/src/linux and see what would happen next. What am I missing? Thanks again. Richard
On Sun, Dec 12, 2004 at 06:15:28PM -0800, Richard wrote:
I did not recall installing kernel-syms, but had installed kernel-source. I went back to DVD, installed kernel-syms, then did online update to ensure both kernel-source and kernel-syms were current, same (2.6.8-24.5-default, confirmed by uname -a). I then did make cloneconfig, make prepare, then ran vmware-config.pl. Again refuse to complete process.
That's strange. What version of vmware do you have? The forementioned procedure worked for me with VMwareWorkstation 4.5.2-8848
Error report follows:
Building the vmmon module.
Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config4/vmmon-only' make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.8-24.5'
WARNING: Symbol version dump /usr/src/linux-2.6.8-24.5/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled.
CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o /tmp/vmware-config4/vmmon-only/linux/hostif.c: In function `MapCrossPage': /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: `PAGE_KERNEL_EXECUTABLE' undeclared (first use in this function) /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: (Each undeclared identifier is reported only once /tmp/vmware-config4/vmmon-only/linux/hostif.c:566: error: for each function it appears in.) make[2]: *** [/tmp/vmware-config4/vmmon-only/linux/hostif.o] Error 1 make[1]: *** [_module_/tmp/vmware-config4/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.8-24.5' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config4/vmmon-only' Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
Execution aborted.
I did not see an obvious location for Module.symvers above and am not sure where to go if I did find it, except maybe copy to /usr/src/linux and see what would happen next.
This part is easy. When in /usr/src/linux directory just execute "cp ../linux-obj/i386/default/Module.symvers ." Replace "default" with "smp" if you are running SMP kernel.
What am I missing? Thanks again. Richard
Are you by any chance building it on 64-bit system? Regards, -Kastus
On Sunday 12 December 2004 7:02 pm, Kastus wrote: <snip> I then did make
cloneconfig, make prepare, then ran vmware-config.pl. Again refuse to complete process.
That's strange. What version of vmware do you have?
VMwareWorkstation 4.5.2-8848, built from .tar.gz file. <snip>
Execution aborted.
I did not see an obvious location for Module.symvers above and am not sure where to go if I did find it, except maybe copy to /usr/src/linux and see what would happen next.
This part is easy. When in /usr/src/linux directory just execute "cp ../linux-obj/i386/default/Module.symvers ."
copy to... /usr/src/linux ?
Are you by any chance building it on 64-bit system?
Uh, oh. Yes. MSI board, AMD 64 3000+. I hesitate to ask...is that a problem? Richard
Hi Guys, I have been running VM 4.5.2 build 8848 since I received my Suse 9.2 CDs without a problem. Reference : http://www.vmware.com/community/thread.jspa?forumID=19&threadID=9694&messageID=86137#86137 Steps under Suse 9.2: make clean make mrproper make cloneconfig make prepare-all After all this got some errors at compile time BUT everything works OK once I launched VMware Workstation. Restored a VM session from a backup, copied it to my Suse 9.2 and launched without a problem and I have been using it on a daily basis as a production workstation since then.. NAT, Bridged, Host Only -> Everything works. Only thing that I saw is that I had errors to create a new VM session. VMWare didn't want to see my CD drive. Replaced the CD from /dev/cdrom to /dev/cdrecorder and voilà it worked !!! No problems of lagging, crashing or anyhing in that order. Regards, Luis Richard wrote:
On Sunday 12 December 2004 7:02 pm, Kastus wrote: <snip> I then did make
cloneconfig, make prepare, then ran vmware-config.pl. Again refuse to complete process.
That's strange. What version of vmware do you have?
VMwareWorkstation 4.5.2-8848, built from .tar.gz file.
<snip>
Execution aborted.
I did not see an obvious location for Module.symvers above and am not sure where to go if I did find it, except maybe copy to /usr/src/linux and see what would happen next.
This part is easy. When in /usr/src/linux directory just execute "cp ../linux-obj/i386/default/Module.symvers ."
copy to... /usr/src/linux ?
Are you by any chance building it on 64-bit system?
Uh, oh. Yes. MSI board, AMD 64 3000+. I hesitate to ask...is that a problem?
Richard
On Sun, Dec 12, 2004 at 07:20:03PM -0800, Richard wrote:
That's strange. What version of vmware do you have?
VMwareWorkstation 4.5.2-8848, built from .tar.gz file.
That's the same I have
I did not see an obvious location for Module.symvers above and am not sure where to go if I did find it, except maybe copy to /usr/src/linux and see what would happen next.
This part is easy. When in /usr/src/linux directory just execute "cp ../linux-obj/i386/default/Module.symvers ."
copy to... /usr/src/linux ?
Yes, that's correct
Are you by any chance building it on 64-bit system?
Uh, oh. Yes. MSI board, AMD 64 3000+. I hesitate to ask...is that a problem?
I'm afraid, that's your problem. I have never used vmware on 64-bit system, so I cannot advise you on that. Your error happens in the piece of code starting #ifdef MODULE_X86_64 in hostif.c Could it be that the kernel you are running on that box does not match kernel sources installed? Just a guess. Sorry, I can't help more. You could probably get more responses if you put "vmware on x86_64" in the subject? Regards, -Kastus
On Sunday 12 December 2004 04:57 pm, Kastus wrote:
On Sun, Dec 12, 2004 at 03:18:00PM -0800, Richard wrote:
On Monday 08 November 2004 8:48 am, Kastus wrote:
Actually, the necessary and sufficient steps on SUSE are:
make cloneconfig make prepare vmware-config.pl
Much faster than bzImage and modules.
Regards, -Kastus
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module.
You need to fully configure the kernel sources first. "fully configure" means, basically, actually starting the build, though you may break out of it. The easiest way to ensure the ".config" file matches the running version is to copy some variation of /boot/config* to /usr/src/linux/. Good luck.
On Sunday 12 December 2004 6:23 pm, Bruce Korb wrote:
On Sunday 12 December 2004 04:57 pm, Kastus wrote:
On Sun, Dec 12, 2004 at 03:18:00PM -0800, Richard wrote:
On Monday 08 November 2004 8:48 am, Kastus wrote:
Actually, the necessary and sufficient steps on SUSE are:
make cloneconfig make prepare vmware-config.pl
Much faster than bzImage and modules.
Regards, -Kastus
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module.
You need to fully configure the kernel sources first. "fully configure" means, basically, actually starting the build, though you may break out of it. The easiest way to ensure the ".config" file matches the running version is to copy some variation of /boot/config* to /usr/src/linux/. Good luck.
Thanks, Bruce. I copied my /boot/config-2.6.8.24.5 file to /usr/src/linux, then I started a build, if I understood you correctly, with make config, then simply exited after a few steps with control-c. Then repeated the VMware build process and got the same result. Any other suggestions, or did I not follow the first ones correctly/closely enough? Richard
On Sun, Dec 12, 2004 at 06:23:05PM -0800, Bruce Korb wrote:
You need to fully configure the kernel sources first. "fully configure" means, basically, actually starting the build, though you may break out of it. The easiest way to ensure the ".config" file matches the running version is to copy some variation of /boot/config* to /usr/src/linux/. Good luck.
This is exactly what "make cloneconfig" does. Available in SUSE kernels only. Regards, -Kastus
the only way I've got it working is /usr/src/linux make cloneconfig make modules /usr/local/vmware-distb ./vmware-install.pl and take the defaults joe On Sun, 2004-12-12 at 15:18 -0800, Richard wrote:
On Monday 08 November 2004 8:48 am, Kastus wrote:
On Sun, Nov 07, 2004 at 09:57:14AM -0500, Michael W Cocke wrote:
cd /usr/src/linux make oldconfig make bzImage make modules
You can skip the installation steps (modules_install and install) if you want. After you do this, install vmware - it works great.
Actually, the necessary and sufficient steps on SUSE are:
make cloneconfig make prepare vmware-config.pl
Much faster than bzImage and modules.
Regards, -Kastus
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module. Should I have run make modules and make modules-install after make cloneconfig and make prepare? I seem to recall some earlier discussion, that I did not save, about there being an appropriate module/better module already included in SuSE and to use this instead. Is this so? Where and how? Thanks for any assistance. Richard
On Sunday 12 December 2004 7:08 pm, Joe Brockert wrote:
the only way I've got it working is /usr/src/linux make cloneconfig make modules
/usr/local/vmware-distb ./vmware-install.pl and take the defaults
joe
<snip>
Apparently, I do not completely get it. I followed this to try to install VM on new 9.2 installation and get error messages. While running vmware-config.pl I got to the line where it says no current module is ok so then asks to make a module. I said yes, and then the errors began with the conclusion that it could not build module. Should I have run make modules and make modules-install after make cloneconfig and make prepare? I seem to recall some earlier discussion, that I did not save, about there being an appropriate module/better module already included in SuSE and to use this instead. Is this so? Where and how? Thanks for any assistance. Richard
Thanks for taking the time to respond: as it turned out, the problem was with my x86_64 system, that VMWare is not quite ready for "this" primetime. Suggestion from Joe Morris with link to ...any..patch seems to have worked. Response quoted below: "I just googled, and came up with this patch. Try it. http://ftp.cvut.cz/vmware/vmware-any-any-update84.tar.gz -- Joe Morris New Tribes Mission" --Richard
Hello I have a little troupple with ODBC on my Suse linux ver 9.2. I have get the ODBC configuration to work, when I use isql -v "test" it give my the connection to mysql database. But when I try to get Open Office to connect to Mysql, I get a messages libodbcinst.so is missing or defect. The libodbcinst.so are located on /usr/lib/, so I don't know how to merge addresses and letter this way? So any help will be nice Thanks Tage.
--- Tage Danielsen
Hello
I have a little troupple with ODBC on my Suse linux ver 9.2. I have get the ODBC configuration to work, when I use isql -v "test" it give my the connection to mysql database. But when I try to get Open Office to connect to Mysql, I get a messages libodbcinst.so is missing or defect. The libodbcinst.so are located on /usr/lib/, so I don't know how to merge addresses and letter this way? So any help will be nice
Thanks Tage.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca
-- Original-Nachricht -- From: "Tage Danielsen"
To: Date: Mon, 13 Dec 2004 23:04:31 +0100 Subject: [SLE] ODBC for linux and Openoffice Hello
I have a little troupple with ODBC on my Suse linux ver 9.2. I have get
the
ODBC configuration to work, when I use isql -v "test" it give my the connection to mysql database. But when I try to get Open Office to connect to Mysql, I get a messages libodbcinst.so is missing or defect. The libodbcinst.so are located on /usr/lib/, so I don't know how to merge addresses and letter this way? So any help will be nice
Thanks Tage.
It seems that the Database type MySQL in Ooo1.3 from Suse 9.2 is broken. I did the following: uninstall Openoffice 1.3 (Suse version) install Openoffice 1.3 or 1.4 form Openoffice.org this worked for me Hope that helps Christopher
On Tuesday 14 December 2004 01:55, cbeynon@bluewin.ch wrote:
-- Original-Nachricht -- From: "Tage Danielsen"
To: Date: Mon, 13 Dec 2004 23:04:31 +0100 Subject: [SLE] ODBC for linux and Openoffice Hello
I have a little troupple with ODBC on my Suse linux ver 9.2. I have get
the
ODBC configuration to work, when I use isql -v "test" it give my the connection to mysql database. But when I try to get Open Office to connect to Mysql, I get a messages libodbcinst.so is missing or defect. The libodbcinst.so are located on /usr/lib/, so I don't know how to merge addresses and letter this way? So any help will be nice
Thanks Tage.
It seems that the Database type MySQL in Ooo1.3 from Suse 9.2 is broken. I did the following: uninstall Openoffice 1.3 (Suse version) install Openoffice 1.3 or 1.4 form Openoffice.org this worked for me
Hope that helps Christopher
If you don't just have to have the ODBC, the JDBC works just fine. If you need the ODBC working, you'll have to go with Chris' suggestion - I haven't tried that yet. -- DC Parris GNU Evangelist http://matheteuo.org/ http://chaddb.sourceforge.net/ "Free software is like God's love - you can share it with anyone anytime anywhere!"
participants (14)
-
Anders Johansson
-
Bruce Korb
-
cbeynon@bluewin.ch
-
Don Parris
-
George Stoianov
-
Jake
-
Joe Brockert
-
Kastus
-
Leendert Meyer
-
Luis-Miguel Astudillo
-
Michael W Cocke
-
Richard
-
Stan Glasoe
-
Tage Danielsen