MacOS X building instructions

[gpetty]

That sounds like a new problem, and we would certainly be interested in seeing the error messages.

If you have the fink gettext installed, you could remove all verions of it - I am working on the basis that Xara LX needs gettext installed independently.

The fink automake 1.9 should be O.K. for Xara LX (but not for some other packages).

Ben.

I found this thread via Google and wanted to mention that I'm having the exact same problem making gettext from the Gnu package... autoreconf reports the following:

Putting files in AC_CONFIG_AUX_DIR, `../build-aux'.
Putting files in AC_CONFIG_AUX_DIR, `../../build-aux'.
autoreconf: configure.ac: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION
Putting files in AC_CONFIG_AUX_DIR, `../build-aux'.
lib/Makefile.am:57: required file `lib/strtol.c' not found
Putting files in AC_CONFIG_AUX_DIR, `../build-aux'.
lib/Makefile.am:118: required file `lib/strdup.c' not found
lib/Makefile.am:118: required file `lib/regex.c' not found
lib/Makefile.am:118: required file `lib/memchr.c' not found
/usr/share/automake-1.6/am/compile.am: DEFS was set with `+=' and is now set with `='
autoreconf: automake failed with exit status: 1

Note that I am using Mac OS X 10.4.7 (Intel) with Xcode 2.4 (partial install from the distribution DVD, omitting Java- and Web-related tools).

The gettext tarball is 0.14.6.

The functions strtol and strdup are supposedly part of the GNU libiberty library, which are in turn supposedly distributed with gcc, gdb, and binutils. Althought I have gcc 4.0 installed, I can find no trace of libiberty on my machine, though man pages are present for the above functions.

HUH! I just looked up at the error messages again and noticed that the error message is from automake-1.6, even though I just downloaded and installed automake 1.9 via fink. Turns out 1.9 is installed in /sw/bin, while 1.6 remains in /usr/bin, which is earlier in my path. Reversing the path order got automake 1.9 to run when I called autoreconf, but now it generates a LOT of warnings similar to

/sw/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
/sw/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB

Otherwise, autoreconf now completes without an actual error.

./configure also completes without error, but make ends with

ar cru .libs/libintl.a bindtextdom.o dcgettext.o dgettext.o gettext.o finddomain.o loadmsgcat.o localealias.o textdomain.o l10nflist.o explodename.o dcigettext.o dcngettext.o dngettext.o ngettext.o plural.o plural-exp.o localcharset.o relocatable.o langprefs.o localename.o log.o printf.o osdep.o intl-compat.o~ranlib .libs/libintl.a
ar: intl-compat.o~ranlib: No such file or directory
make[3]: *** [libintl.la] Error 1

It appears to me (a non-guru) that for some reason 'make' is concatenating the 'ar' command with the 'ran' command, separated by a '~', so that 'ar' sees a spurious filename 'intl-compat.o~ranlib'

But for the life of me, I can't figure out why this is happening or how to make it stop, despite manually editing intl/Makefile.

Anyway, for now I'm stuck, unless there's another way to get the required version of 'gettext' installed.

[gpetty]

Found a binary for gettext that seems to work (so far) via i-Installer v2 from http://tug.org/i-packages/ii2.ii2

Now I'm running into problems using

autoreconf -f -i -s

in the XaraLX directory ... I get

Copying file mkinstalldirs
Makefile.am:29: directory should not contain `/'
Makefile.am:29: directory should not contain `/'
autoreconf: automake failed with exit status: 1

In short, I'm further along than I was, but stuck again.

[abligh]

Found a binary for gettext that seems to work (so Makefile.am:29: directory should not contain `/'
In short, I'm further along than I was, but stuck again.

You need to upgrade your autoconf and/or automake. I think that's an autoconf problem.

Alex

[gpetty]

Once again I was an unwitting victim of the path order ... I had automake 1.9 installed in /sw/bin, but it was hitting version 1.6 in /usr/bin first.

I've switched the path order in my .cshrc file, and that seems to have gotten me past the previous glitch. Now I'm on what I hope is my final glitch:

When I 'make' in ~/XaraLx, I get a bunch of warnings (see below) and then the following error:

dyld: Library not loaded: /usr/local/lib/libwx_macud-2.6.0.dylib
Referenced from: /Users/gpetty/wx/v263/build-unicode-debug/utils/wxrc/wxrc
Reason: image not found
Could not read dialogs for translation (empty or bad wxrc) [/bin/sh -c 'eval LD_LIBRARY_PATH=/Users/gpetty/wx/v263/build-unicode-debug/lib /Users/gpetty/wx/v263/build-unicode-debug/utils/wxrc/wxrc -g ./xrc/dialogs.xrc'] at .././Scripts/build-resources.pl line 423.
Makefile:335: *** "Resource build failed". Stop.


Note that I am also getting (earlier in the make):

Making all in wxOil
Testing for new resources and svn version
Rebuilding svn version
subversion/libsvn_wc/lock.c:377: (apr_err=155007)
svn: '..' is not a working copy
svnversion gives exported

It looks ominous to me, but maybe it means nothing.

Also, I get a lot of warnings about certain png files not being found ; e.g,

.././wxOil/xrc/EN/aboutres.xrc:23 Warning: Bitmap ./xrc/2.png not found
.././wxOil/xrc/EN/aboutres.xrc:82 Warning: Bitmap ./xrc/2.png not found
.././wxOil/xrc/EN/aboutres.xrc:149 Warning: Bitmap ./xrc/2.png not found
.././wxOil/xrc/EN/aboutrsw.xrc:23 Warning: Bitmap ./xrc/2.png not found
.././wxOil/xrc/EN/barsdlgs.xrc:762 Warning: Bitmap ./xrc/leftbrace.png not found
.././wxOil/xrc/EN/barsdlgs.xrc:766 Warning: Bitmap ./xrc/rightbrace.png not found
.././wxOil/xrc/EN/barsdlgs.xrc:770 Warning: Bitmap ./xrc/label.png not found
.././wxOil/xrc/EN/errordlg.xrc:31 Warning: Bitmap ./xrc/.png not found
.././wxOil/xrc/EN/register.xrc:19 Warning: Bitmap ./xrc/2.png not found
.././wxOil/xrc/EN/textres.xrc:26 Warning: Bitmap ./xrc/aspect.png not found
.././wxOil/xrc/EN/textres.xrc:74 Warning: Bitmap ./xrc/tracking.png not found
.././wxOil/xrc/EN/textres.xrc:78 Warning: Bitmap ./xrc/kerning.png not found

[gpetty]

Let me add that I just discovered that I have

/usr/local/lib/libwx_macud-2.5.3.dylib

but not the version 2.6.0 that is being sought in the make.

I did find:

/Users/gpetty/wx/v263/build-unicode-debug/lib/libwx_macud-2.6.0.dylib

I assume the build should be looking for that one; I don't know why it isn't.

[BPFowler]

Let me add that I just discovered that I have /usr/local/lib/libwx_macud-2.5.3.dylib but not the version 2.6.0 that is being sought in the make.

This was provided by Apple, FWIW I would suggest removing it (and all other traces of wxWidgets 2.5.x), but it was a pleasant surprise to find this library, and it would be very helpful to this project if future versions of MacOS has wxWidgets 2.6, 2.8 and so on.

... /Users/gpetty/wx/v263/build-unicode-debug/lib/libwx_macud-2.6.0.dylib
I assume the build should be looking for that one; I don't know why it isn't.

You want the --with-wx-config flag in your arguments to the configure script. See wxOil compiling issues for an example, and the Wx-Config page for more information about wx-config


Ben

[gpetty]

This was provided by Apple, FWIW I would suggest removing it (and all other traces of wxWidgets 2.5.x), but it was a pleasant surprise to find this library, and it would be very helpful to this project if future versions of MacOS has wxWidgets 2.6, 2.8 and so on.



You want the --with-wx-config flag in your arguments to the configure script. See wxOil compiling issues for an example, and the Wx-Config page for more information about wx-config


Ben

Here's the exact line I used, taking from my shell command history:

./configure --enable-debug --with-wx-config=/Users/gpetty/wx/v263/build-unicode-debug/wx-config

This in turn was taken verbatim from the "Xara LX Build for Mac" page, only substituting the slightly modified path to my wx-config

[gpetty]

This was provided by Apple, FWIW I would suggest removing it (and all other traces of wxWidgets 2.5.x), but it was a pleasant surprise to find this library, and it would be very helpful to this project if future versions of MacOS has wxWidgets 2.6, 2.8 and so on.

After 20 years of muddling through builds of diverse software packages under various flavors of Unix, I'm amazed that modern build scripts still don't automatically check for, and offer advice about, conflicting versions of and/or paths to previously installed packages. Especially since scripts like configure seem to check for literally everything else.

I think the inevitable pain, suffering, and frustrated cursing that accompanies the build of almost any moderately complicated package is one important reason why Unix and its variants still haven't caught on with most non-expert users (I'm probably a major exception). The worst part is never knowing whether success will come in 5 minutes or 5 days. Or never. At some point, you make a guess as to the odds that the additional time invested will ultimately pay for itself, and you either push on or else go do something you KNOW will have a successful outcome, like mowing your lawn.

Grant

[BPFowler]

[QUOTE=gpetty;168410]Once again I was an unwitting victim of the path order ... I had automake 1.9 installed in /sw/bin, but it was hitting version 1.6 in /usr/bin first.

I've switched the path order in my .cshrc file, .../QUOTE]

fink should provide you with a script like:

source /sw/bin/init.sh

and instructions concerning the .rc files. (Are you really using the tsch?).

Ben

[gpetty]

[QUOTE=BPFowler;168440]

Once again I was an unwitting victim of the path order ... I had automake 1.9 installed in /sw/bin, but it was hitting version 1.6 in /usr/bin first.

I've switched the path order in my .cshrc file, .../QUOTE]

fink should provide you with a script like:

source /sw/bin/init.sh

and instructions concerning the .rc files.

Interesting. When I installed Fink + Fink Commander yesterday, I don't recall it pointing out any of this when I fired it up for the first time. I'm new to Macs (as of a few days ago), but so far at least, my experience had been that when you install a new (precompiled) program, it runs, and there's no need to dig into docs unless you run across something you don't understand. In every obvious respect at least, Fink Commander had been working fine for me so far.

(Are you really using the tsch?).

Ben

Yes. It's what I've been using for 20 years, and no one had ever offered a reason why I should change. It gave me Emacs-style command-line editing and other benefits before other shells I knew about had that. If there's another shell (bash?) that I'd be better off with, I'm certainly willing to consider it, as long as the change isn't too painful.