From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] libglib2: fix alignment checks
Date: Fri, 20 Jul 2012 23:38:43 +0200 [thread overview]
Message-ID: <20120720233843.3e9dc2c3@skate> (raw)
In-Reply-To: <1342646260-11203-4-git-send-email-s.neumann@raumfeld.com>
Le Wed, 18 Jul 2012 23:17:38 +0200,
Sven Neumann <s.neumann@raumfeld.com> a ?crit :
> The configure script fails to calculate alignments when cross-compiling.
>
> This commit hardcodes alignments for 32 bit platforms. It will need to
> be adjusted for other platforms. Please advice on how to fix this properly.
OE is doing the same thing, so apparently, it seems like there isn't
any other obvious solution. We'll have to define those values for each
architecture.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-20 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 21:17 [Buildroot] RFC: update libglib2 to 2.32.4 Sven Neumann
2012-07-18 21:17 ` [Buildroot] [PATCH 1/5] libglib2: bump to version 2.32.4 Sven Neumann
2012-07-18 21:17 ` [Buildroot] [PATCH 2/5] libglib2: fix linker flags Sven Neumann
2012-07-20 21:32 ` Thomas Petazzoni
2012-08-07 15:40 ` Sven Neumann
2012-07-18 21:17 ` [Buildroot] [PATCH 3/5] libglib2: fix alignment checks Sven Neumann
2012-07-20 21:38 ` Thomas Petazzoni [this message]
2012-07-18 21:17 ` [Buildroot] [PATCH 4/5] libglib2: define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 Sven Neumann
2012-07-20 21:39 ` Thomas Petazzoni
2012-07-18 21:17 ` [Buildroot] [PATCH 5/5] libglib2: do not use xlocale Sven Neumann
2012-07-20 21:39 ` Thomas Petazzoni
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=20120720233843.3e9dc2c3@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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