--Cqq5NadOW2RfLMJ/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 14, 2005 at 08:46:31AM -0700, Bill Studenmund wrote:
  | I strongly suggest forgetting about all these conditional compile=20
  | directives. They are not an officially-supported way to compile (last I=
=20
  | heard); folks will fix issues you see, but they will not receive the ma=
in=20
  | debugging emphasis that other compile issues will.
  |=20
  | I note you have "embed" in one of the path names, and so I suspect you =
may=20
  | be trying to generate a release for an embedded system. I think you wil=
l=20
  | be much more successful to just build a release into a destdir, then co=
py=20
  | only the files you want from there into a hierarcy for your procuct. Th=
e=20
  | latter method will permit you file-by-file control over exactly what yo=
u=20
  | get. Build options will never be the precise, and you'll probably keep=
=20
  | running into ussues like the ones you're seeing.

I concur with Bill; I meant to make a similar recommendation in my
previous reply.

--Cqq5NadOW2RfLMJ/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFCXvIWpBhtmn8zJHIRAtRFAJ43ghpX4vCYFCOJagGob02qL6m5mQCgx/SP
1KU7dM+2pwAKYN+9vJu0XCQ=
=Pf1M
-----END PGP SIGNATURE-----

--Cqq5NadOW2RfLMJ/--