From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Alignment issue
Date: Fri, 13 Aug 2004 14:40:24 +0200 [thread overview]
Message-ID: <1092400824.28711.226.camel@pegasus> (raw)
In-Reply-To: <1092397956.10618.102.camel@hades.cambridge.redhat.com>
Hi David,
> I was overriding CFLAGS when I invoked make, because otherwise other
> stuff (like -m32) gets omitted. Can we do this in acinclude.m4?
>
> - CFLAGS="-Wall -O2"
> + if (test "${CFLAGS}" = ""); then
> + CFLAGS="-Wall -O2"
> + fi
> +
I was thinking of something like that, but actually never included it
until now. Fix is in CVS for libs, utils and hcidump.
> OK. I think I'm not supposed to ship a cvs snapshot -- I have to wait
> for 2.10. But I've isolated just the patch in question and added it into
> the bluez-utils-2.9-2 RPM, with the above change to inherit CFLAGS if
> they're already set.
I will use memmove for unaligned access and release libs and utils
tomorrow or the day after tomorrow. I like to test your unaligned code a
little bit more before making a release with it.
> > I did it this way, but there were reports of Sparc platforms where the
> > resulting binary should be run-tested.
>
> Hmmm. Can I revise my original answer.... don't. If the user asks for
> it, do it. Else don't.
>
> Random behavioural changes based on the characteristics of the system we
> _happen_ to build on today are probably a bad thing. Just build as
> configured and don't try to auto-adapt to _anything_ :)
Don't worry. You still have to use --enable-pie to activate it even if
configure finds out that the compile supports it.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-13 12:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:38 [Bluez-devel] Alignment issue Daryl Van Vorst
2004-08-10 23:12 ` Marcel Holtmann
2004-08-11 9:20 ` Stephen Crane
2004-08-11 11:08 ` David Woodhouse
2004-08-11 19:33 ` Marcel Holtmann
2004-08-11 7:13 ` Marcel Holtmann
2004-08-11 16:44 ` Daryl Van Vorst
2004-08-11 19:31 ` Marcel Holtmann
2004-08-12 8:34 ` David Woodhouse
2004-08-12 9:27 ` Marcel Holtmann
2004-08-12 10:01 ` David Woodhouse
2004-08-12 10:22 ` Marcel Holtmann
2004-08-12 10:35 ` David Woodhouse
2004-08-12 11:00 ` Marcel Holtmann
2004-08-12 11:33 ` David Woodhouse
2004-08-12 11:49 ` Marcel Holtmann
2004-08-12 12:02 ` David Woodhouse
2004-08-12 12:29 ` Marcel Holtmann
2004-08-12 13:36 ` Marcel Holtmann
2004-08-13 8:07 ` David Woodhouse
2004-08-13 9:05 ` Marcel Holtmann
2004-08-13 9:14 ` David Woodhouse
2004-08-13 11:52 ` David Woodhouse
2004-08-13 12:40 ` Marcel Holtmann [this message]
2004-08-12 12:53 ` David Woodhouse
2004-08-13 9:58 ` Marcel Holtmann
2004-08-13 10:56 ` David Woodhouse
2004-08-12 10:10 ` Stephen Crane
2004-08-12 10:25 ` Marcel Holtmann
2005-01-20 14:30 ` David Woodhouse
2005-01-20 14:45 ` Marcel Holtmann
2005-01-20 14:59 ` David Woodhouse
2005-01-20 18:14 ` Marcel Holtmann
2005-01-21 8:26 ` David Woodhouse
2005-01-23 8:12 ` Marcel Holtmann
2005-01-23 11:39 ` Marcel Holtmann
2005-01-23 12:29 ` David Woodhouse
2005-01-23 14:40 ` Marcel Holtmann
2005-01-23 15:11 ` David Woodhouse
2005-01-23 15:22 ` Marcel Holtmann
2005-01-23 23:16 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 9:48 john smith
2004-08-16 10:15 ` Marcel Holtmann
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=1092400824.28711.226.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.