RE: prc-tools-2.2 on FreeBSD-4.7 build errors

[Chris P. <pt...@te...>]

OK, here is what I did and a couple questions.

My base directory is /usr/local/pilot
Build directory is /usr/local/pilot/build (and then empty).

The libintl stuff is installed in FreeBSD, however it is in
/usr/local/(include | lib).  I didn't know if I should add /usr/local to the
search paths, would this have been ok or caused problems later?

So I did the following:
I created /usr/local/pilot/build/intl directory.
I then copied /usr/local/include/libintl.h to /usr/local/pilot/build/intl
I then copied /usr/local/lib/libintl* to /usr/local/pilot/build/intl

Then in the Makefile in /usr/local/pilot/build/tools I added -lintl to the
end of the obj-res and build-prc lines and -L../intl to the end of the
LIBDIRS variable.

Then in the Makefile in /usr/local/pilot/build/bfd I added -I../intl to the
INCLUDES variable.

This seems to work, though I havn't actually built/run anything yet.

My question is:
I noticed there is libintl stuff in the build/m68k-palmos/binutils/intl and
in the build/arm-palmos/binutils/intl directories.  I am wondering if I
should have used these instead?  I didn't see an easy way to dertermine
which target I was building so I could pick a directory.  Then again, the
problems with libintl only seemed to be with the tools.

  - Chris

-----Original Message-----
From: prc...@li...
[mailto:prc...@li...]On Behalf Of Eric J
Schwertfeger
Sent: Friday, October 18, 2002 1:13 PM
To: prc...@li...
Subject: Re: prc-tools-2.2 on FreeBSD-4.7 build errors



> On Thu, Oct 17, 2002 at 11:36:21AM -0700, Eric J Schwertfeger wrote:
> > This time it actually went smoother than the pilot-link upgrade.  Had
one
> > executable that I had to run the linking by hand to include
> > /usr/local/lib/libintl.*
>
> Which one?  Patches welcome...

I'd love to send in patches, but my understanding of autoconfigure ends at
./autoconfigure --help

However, the next message in the digest touches on the same issue, it
seems.  I'll only comment on the --enable-targets=m68k-palmos,arm-palmos
branch, since that's what I did.

> ../prc-tools-2.2/configure --enable-targets=m68k-palmos,arm-palmos
> --enable-languages=c,c++ --with-headers=`pwd`/empty
> --with-palmdev-prefix=/usr/local/pilot
>
> I get the following errors:
> ---------------------------
> rm -f bfd-tmp.h
> cp bfd-in3.h bfd-tmp.h
> /bin/sh ../../prc-tools-2.2/binutils/bfd/../move-if-change bfd-tmp.h bfd.h
> rm -f bfd-tmp.h
> touch stmp-bfd-h
> /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../../prc-tools-2.2/binutils/bfd -I. -D_GNU_SOURCE      -I.
> -I../../prc-tools-2.2/binutils/bfd
> -I../../prc-tools-2.2/binutils/bfd/../include
> -I../../prc-tools-2.2/binutils/bfd/../intl -I../intl   -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -g -O2 -c
> ../../prc-tools-2.2/binutils/bfd/archive.c
>
gcc -DHAVE_CONFIG_H -I. -I../../prc-tools-2.2/binutils/bfd -I. -D_GNU_SOURCE
> -I. -I../../prc-tools-2.2/binutils/bfd
> -I../../prc-tools-2.2/binutils/bfd/../include
> -I../../prc-tools-2.2/binutils/bfd/../intl -I../intl -W -Wall
> -Wstrict-prototypes -Wmissing-prototypes -g -O2 -c
> ../../prc-tools-2.2/binutils/bfd/archive.c -o archive.o
> In file included from ../../prc-tools-2.2/binutils/bfd/archive.c:131:
> ../../prc-tools-2.2/binutils/bfd/sysdep.h:135: libintl.h: No such file or
> directory
> gmake[3]: *** [archive.lo] Error 1
> gmake[3]: Leaving directory `/usr/local/pilot/build/bfd'
> gmake[2]: *** [all-recursive] Error 1
> gmake[2]: Leaving directory `/usr/local/pilot/build/bfd'
> gmake[1]: *** [all-recursive-am] Error 2
> gmake[1]: Leaving directory `/usr/local/pilot/build/bfd'
> gmake: *** [bfd] Error 2

This is the one.  libintl.h and corresponding libraries are not part of
the base FreeBSD distribution.  I forget which port/package installs them,
but it installs them to /usr/local/(include|lib).

I copied libintl.h into the directory it was compiling in, ran gmake
again, and then when it bombed out linking, added -L/usr/local/lib -lintl
to the command line, ran that, then reran gmake.   Compiling finished up
that time, so this was the only place it was an issue.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
prc-tools-devel mailing list
prc...@li...
https://lists.sourceforge.net/lists/listinfo/prc-tools-devel