From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] cross compiling bluez-utils
Date: Fri, 04 Feb 2005 13:31:09 +0100 [thread overview]
Message-ID: <1107520269.6921.8.camel@pegasus> (raw)
In-Reply-To: <847626459@web.de>
Hi Martin,
> does it make sense to change the line "sysconfdir='${prefix}/etc'" into "sysconfdir='${exec_prefix}/etc'" in the configure file? I found that useful while compiling the utils for an ARM platform. The /etc will be generated in the right place then.
explain what the differences are. However the acinclude.m4 is a little
bit more complex and there are other corner cases.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-04 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 12:24 [Bluez-devel] cross compiling bluez-utils Martin Mueller
2005-02-04 12:31 ` Marcel Holtmann [this message]
2005-02-05 2:39 ` Anderson Clayton B Rodrigues
-- strict thread matches above, loose matches on Subject: below --
2005-02-04 12:44 Martin Mueller
2005-02-04 12:48 ` Marcel Holtmann
2005-02-05 6:48 Martin Mueller
2005-02-05 15:53 ` Marcel Holtmann
2005-02-08 23:24 omap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1107520269.6921.8.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox