[brailleblaster] Re: Running BB on a Mac
- From: "John J. Boyer" <john@xxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Tue, 23 Oct 2012 01:59:26 -0500
Hi Hanxiao,
I'm glad it is working, but I'm not sure what is going on. We need more
Mac users, especially someone who can make a reliable installer.
John
On Tue, Oct 23, 2012 at 01:44:36PM +0800, Hanxiao Fu wrote:
> Hi John,
>
> Thank your for the instructions, it works now. FYI, I was only able to
> install liblouis but not liblouisutdml. When I tried to install, I got the
> following error:
>
> checking for BASE_DEPENDENCIES... configure: error: Package requirements
> > (liblouis, libxml-2.0) were not met:
> > No package 'libxml-2.0' found
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> > Alternatively, you may set the environment variables
> > BASE_DEPENDENCIES_CFLAGS
> > and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
> > See the pkg-config man page for more details.
>
>
> Then I wasn't able to make or make install liblouisutdml. But I did
> succefully install and copy liblouis.dylib to BB folder. And when I ran BB
> with the new liblous.dylib and the liblouisutml.dylib from the package
> downloaded from the website, it finally worked. I've appended the complete
> log after the email.
>
> Maybe I have been a normal windows user for too long, and as a result, I'm
> not familiar with command line tools and I get used to those "one click
> install" mechanisms, I always find setting-up the environment and libraries
> hard for me, not just for BB but for all programs that require me doing
> so. I hope there could be some scripts that can enhance the robustness in
> the installation process. Is the intallers folder supposed to do the
> automation? If yes, I'd like to participate in making it come true.
>
> Here's the complete log:
>
> Hanxiaos-MacBook-Pro:liblouisutdml-2.3.0 Hanxiao$ ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking for ranlib... ranlib
> checking build system type... i686-apple-darwin12.0.0
> checking host system type... i686-apple-darwin12.0.0
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking whether the preprocessor supports include_next... yes
> checking getopt.h usability... yes
> checking getopt.h presence... yes
> checking for getopt.h... yes
> checking stdarg.h usability... yes
> checking stdarg.h presence... yes
> checking for stdarg.h... yes
> checking stddef.h usability... yes
> checking stddef.h presence... yes
> checking for stddef.h... yes
> checking for unistd.h... (cached) yes
> checking for getopt.h... (cached) yes
> checking for getopt_long_only... yes
> checking whether getopt is POSIX compatible... yes
> checking for working GNU getopt function... no
> checking whether getenv is declared... yes
> checking for wchar_t... yes
> checking whether program_invocation_name is declared... no
> checking whether program_invocation_short_name is declared... no
> checking for va_copy... yes
> checking whether NULL can be used in arbitrary expressions... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking whether make sets $(MAKE)... (cached) yes
> checking for library containing strerror... none required
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for ld used by gcc...
> /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
> checking if the linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
> checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
> option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm
> checking how to recognise dependent libraries... pass_all
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> rm: conftest.dSYM: is a directory
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for epcf90... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for gfortran... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether accepts -g... no
> checking the maximum length of command line arguments... 196608
> checking command to parse /usr/bin/nm output from gcc object... rm:
> conftest.dSYM: is a directory
> rm: conftest.dSYM: is a directory
> rm: conftest.dSYM: is a directory
> rm: conftest.dSYM: is a directory
> ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... (cached) ranlib
> checking for strip... strip
> rm: conftest.dSYM: is a directory
> rm: conftest.dSYM: is a directory
> checking if gcc supports -fno-rtti -fno-exceptions... rm: conftest.dSYM: is
> a directory
> no
> checking for gcc option to produce PIC... -fno-common
> checking if gcc PIC flag -fno-common works... rm: conftest.dSYM: is a
> directory
> yes
> checking if gcc static flag -static works... rm: conftest.dSYM: is a
> directory
> no
> checking if gcc supports -c -o file.o... rm: conftest.dSYM: is a directory
> yes
> checking whether the gcc linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports
> shared libraries... yes
> checking dynamic linker characteristics... darwin12.0.0 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> rm: conftest.dSYM: is a directory
> rm: conftest.dSYM: is a directory
> checking for ld used by g++...
> /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
> checking if the linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
> checking whether the g++ linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports
> shared libraries... yes
> checking for g++ option to produce PIC... -fno-common
> checking if g++ PIC flag -fno-common works... rm: conftest.dSYM: is a
> directory
> yes
> checking if g++ static flag -static works... rm: conftest.dSYM: is a
> directory
> no
> checking if g++ supports -c -o file.o... rm: conftest.dSYM: is a directory
> yes
> checking whether the g++ linker
> (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports
> shared libraries... yes
> checking dynamic linker characteristics... darwin12.0.0 dyld
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> checking for help2man... no
> checking for pkg-config... /usr/local/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for BASE_DEPENDENCIES... configure: error: Package requirements
> (liblouis, libxml-2.0) were not met:
>
> No package 'libxml-2.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables
> BASE_DEPENDENCIES_CFLAGS
> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> Thanks,
> Hanxiao
>
>
>
> On Mon, Oct 22, 2012 at 2:36 PM, John J. Boyer <john@xxxxxxxxxxxxxx> wrote:
>
> > Hi Hanxiao,
> >
> > The tarballs that you downloaded use Gnu autotools for installation. Use
> > the command
> >
> > tar xfz filename
> >
> > To uncompress them and create a directory. Install pkgconfig first. go
> > to the directory and type configure then make Use sudo to get root
> > permissions and type make install. return to your normal user login.
> > Install liblouis, then liblouisutdml. Go to /usr/local/lib and copy
> > liblouis.dylib and liblouisutdml.dylib into the native/lib subdirectory
> > of your BrailleBlaster directory.
> >
> > Hope this helps.
> > John
> >
> > On Mon, Oct 22, 2012 at 12:34:16PM +0800, Hanxiao Fu wrote:
> > > Hello,
> > >
> > > John, I found the thread posted earlier, but I don't think my problem is
> > > caused by wrong reference, because the exceptions are different. I've
> > > downloaded liblouisutdml and liblouis from the link, but I don't know
> > how I
> > > can use pkg-config to compile these packages. Can someone tell me more
> > > about it?
> > >
> > > Thanks,
> > > Hanxiao
> > >
> > > On Sat, Oct 20, 2012 at 8:35 PM, John J. Boyer <
> > john.boyer@xxxxxxxxxxxxxxxxx
> > > > wrote:
> > >
> > > > I'm pretty sure the jar file is correct, but to be on the safe side, if
> > > > you compile liblouisutdml you should recompile liblouisutdml.jar also
> > > > Just run ant in the java directory obtained from liblouisutdml.tar.gz
> > > >
> > > > Note that this will work only on your machine. We need to specify the
> > > > correct --prefix option when making the next Mac zip file.
> > > >
> > > > John
> > > >
> > > > On Sat, Oct 20, 2012 at 01:14:11PM +0100, Michael Whapples wrote:
> > > > > I am not sure but I guess its that the jliblouisutdml.jar and the
> > DLLs
> > > > > are from different builds.
> > > > >
> > > > > Did you build liblouisutdml yourself? If so did you compile
> > > > > jliblouisutdml.jar when building liblouisutdml and did you use that
> > jar
> > > > > file?
> > > > >
> > > > > Michael Whapples
> > > > > On 20/10/2012 12:57, Hanxiao Fu wrote:
> > > > > >Hello John,
> > > > > >
> > > > > >I can now run BB, but when I try to translate, I got the following
> > > > error:
> > > > > >
> > > > > >Exception in thread "main" java.lang.UnsatisfiedLinkError:
> > > > >
> > > >
> > >org.liblouis.liblouisutdml.translateFile(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;I)Z
> > > > > >at org.liblouis.liblouisutdml.translateFile(Native Method)
> > > > > >at
> > org.brailleblaster.wordprocessor.DocumentManager.translate(Unknown
> > > > > >Source)
> > > > > >at
> > > > >
> > >org.brailleblaster.wordprocessor.DocumentManager.translateView(Unknown
> > > > > >Source)
> > > > > >at
> > org.brailleblaster.wordprocessor.BBToolBar$3.widgetSelected(Unknown
> > > > > >Source)
> > > > > >at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Display.sendEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Widget.notifyListeners(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
> > > > > >at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
> > > > > >at org.brailleblaster.wordprocessor.DocumentManager.<init>(Unknown
> > > > Source)
> > > > > >at org.brailleblaster.wordprocessor.WPManager.<init>(Unknown Source)
> > > > > >at org.brailleblaster.Main.main(Unknown Source)
> > > > > >
> > > > > >Any clue?
> > > > > >
> > > > > >Hanxiao
> > > > > >
> > > > > >On Wed, Oct 17, 2012 at 4:00 PM, John J. Boyer
> > > > > ><john.boyer@xxxxxxxxxxxxxxxxx <mailto:john.boyer@xxxxxxxxxxxxxxxxx
> > >>
> > > > > >wrote:
> > > > > >
> > > > > > Look on the BrailleBlaster website. There is a zip file for the
> > mac
> > > > on
> > > > > > the "bet BrailleBlaster" page. However, liblouisutdml.dylib
> > > > references
> > > > > > liblouis.dylib incorrectly. There is a fix for this in the
> > archives.
> > > > > > Hope you can find it.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Wed, Oct 17, 2012 at 01:48:38PM +0800, Hanxiao Fu wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > I started using mac to run BB recently, but the libraries I
> > used
> > > > > > on my
> > > > > > > windows machine don't seem to be compatible with Mac. Where
> > > > > > should I find
> > > > > > > those dlls and jars for my 64-bit mac?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Hanxiao
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > John J. Boyer; President, Chief Software Developer
> > > > > > Abilitiessoft, Inc.
> > > > > > http://www.abilitiessoft.com
> > > > > > Madison, Wisconsin USA
> > > > > > Developing software for people with disabilities
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > --
> > > > John J. Boyer; President, Chief Software Developer
> > > > Abilitiessoft, Inc.
> > > > http://www.abilitiessoft.com
> > > > Madison, Wisconsin USA
> > > > Developing software for people with disabilities
> > > >
> > > >
> > > >
> >
> > --
> > John J. Boyer, Executive Director
> > GodTouches Digital Ministry, Inc.
> > http://www.godtouches.org
> > Madison, Wisconsin, USA
> > Peace, Love, Service
> >
> >
> >
--
John J. Boyer, Executive Director
GodTouches Digital Ministry, Inc.
http://www.godtouches.org
Madison, Wisconsin, USA
Peace, Love, Service
Other related posts:
