* RE: [RFC] Change ECC algorithm from userspace
From: Ricard Wanderlof @ 2011-10-31 8:04 UTC (permalink / raw)
To: Jon Povey
Cc: Enric Balletbo i Serra, Javier Martinez Canillas,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0BF244FAD1@Cloud.RL.local>
On Fri, 28 Oct 2011, Jon Povey wrote:
> linux-mtd-bounces@lists.infradead.org wrote:
>> I want to be able to use 1-bit ECC for the first partition where I
>> save the loader binary and has to be accessed by the ROM boot but use
>> a 4-bit ECC for my rootfs partition.
>>
>> Does anyone have this same issue?
>
> DM355 and DM365 has similar issues as the RBL expects a different OOB/ECC
> layout to Linux.
Slightly off-topic, but in the 355/365 (etc) case it's possible to modify
the Linux driver so it uses the RBL ECC layout. For us, it seemed the
easiest thing to do, as having different ECC layouts in different parts
of the flash proved to be a pain. If you need different ECC algorithms in
different parts of the flash this wouldn't work of course.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply
* RE: [RFC] Change ECC algorithm from userspace
From: Ricard Wanderlof @ 2011-10-31 8:04 UTC (permalink / raw)
To: Jon Povey
Cc: Enric Balletbo i Serra, Javier Martinez Canillas,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0BF244FAD1@Cloud.RL.local>
On Fri, 28 Oct 2011, Jon Povey wrote:
> linux-mtd-bounces@lists.infradead.org wrote:
>> I want to be able to use 1-bit ECC for the first partition where I
>> save the loader binary and has to be accessed by the ROM boot but use
>> a 4-bit ECC for my rootfs partition.
>>
>> Does anyone have this same issue?
>
> DM355 and DM365 has similar issues as the RBL expects a different OOB/ECC
> layout to Linux.
Slightly off-topic, but in the 355/365 (etc) case it's possible to modify
the Linux driver so it uses the RBL ECC layout. For us, it seemed the
easiest thing to do, as having different ECC layouts in different parts
of the flash proved to be a pain. If you need different ECC algorithms in
different parts of the flash this wouldn't work of course.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
^ permalink raw reply
* Re: [PATCH v2] GIO bus support for SGI IP22/28
From: Joshua Kinard @ 2011-10-31 8:04 UTC (permalink / raw)
To: Thomas Bogendoerfer; +Cc: linux-mips, linux-fbdev, ralf, FlorianSchandinat
In-Reply-To: <20111030223418.GA16346@alpha.franken.de>
On 10/30/2011 18:34, Thomas Bogendoerfer wrote:
>
> no, but it will make live a lot easier, because address and interrupts don't
> need to be probed by the driver. Right now interrupts are on my todo, since
> there is some weirdness between guiness and fullhouse boxes...
It wouldn't be an SGI machine if it didn't implement something weird or just
plain backwards...
> it still needs something to setup the PCI bus on the card and issue
> the probing. The problem with the Tulip Phobos cards is, that they
> messed up the endianess, so that none of the Linux Tulip drivers will
> work out of the box...
A.k.a., Tulip (and possibly ThunderLAN) assume little-endian, when we're
talking big-endian archs here. Interesting. Simple fix, as in defining a
few driver structures with little- and big-endian versions (if they're doing
something like packing bits or using bitfields)? Or is it more complex than
that?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
^ permalink raw reply
* RE: GATT Dbus API on BlueZ - attirbute-api.txt modifications
From: Ajay Pillai @ 2011-10-31 8:04 UTC (permalink / raw)
To: Ganir, Chen, Anderson Lizardo
Cc: Luiz Augusto von Dentz, Mat Martineau, Claudio Takahasi,
linux-bluetooth@vger.kernel.org, bgix@codeaurora.org,
ingas@codeaurora.org
In-Reply-To: <7769C83744F2C34A841232EF77AEA20C01DCBC482A@dnce01.ent.ti.com>
Hi Chen,
>Can you please try and think of a situation where a client may need the old value, knowing that it may not be the correct one? Why would >anyone needing a value from the server need a cached value which has no meaning at the time of the "get_properties", knowing also that it >should wait for the "property_changed" event ?
I am not sure if we should be making assumptions about if such a "lazy read" would be of use to DBUS Apps. What I am trying to convey is that a design that supports both "lazy reads"(current approach suggested by Anderson which can potentially lead to less over-the-air operations, in multi-App scenarios) and "precise reads" (as described by ReadValue method) would cater to a wider set of usecases.
This also has potential to simplify quite a lot of "Clients" while dealing with servers that do not require polling. The Client just need to write the Client Characteristics Config and just forget about handling notifications or Indications, but just go on reading the value property whenever it needs it, trusting BlueZ to handle the notifications or indications and keeping the "value" property updated. However this would require a change in the way connections are managed as the DBUS Apps would need to be given more control over connections (something like reference counting of connections).
>This design is totally wrong, and may cause problems. I really see no reason for keeping the cached value. The correct behavior can be one >of the two :
>1. ReadValue method, blocking if a connection is up, returning the value, or returning some kind of error to let the client know that a >value can not be read at the moment if the link is down or pending.
>2. ReadValue method invokes a procedure for reading the value. A ReadValueComplete signal/watcher method is then raised when the value was >actually read from the server (connection is successful).
>These should replace the "Value" property, removing it from the list.
>I would prefer method 1, since it's more straight forward, and allows the client to know exactly what is going on.
I see method 2 as just an extension of method 1 where the API behaves likes method1 if the connection persists and if the connection is not present, then it lets the client know (as method1) and then moves on to method2.
Tank you
ajay
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
^ permalink raw reply
* Re: [PATCH v2] GIO bus support for SGI IP22/28
From: Joshua Kinard @ 2011-10-31 8:04 UTC (permalink / raw)
To: Thomas Bogendoerfer; +Cc: linux-mips, linux-fbdev, ralf, FlorianSchandinat
In-Reply-To: <20111030223418.GA16346@alpha.franken.de>
On 10/30/2011 18:34, Thomas Bogendoerfer wrote:
>
> no, but it will make live a lot easier, because address and interrupts don't
> need to be probed by the driver. Right now interrupts are on my todo, since
> there is some weirdness between guiness and fullhouse boxes...
It wouldn't be an SGI machine if it didn't implement something weird or just
plain backwards...
> it still needs something to setup the PCI bus on the card and issue
> the probing. The problem with the Tulip Phobos cards is, that they
> messed up the endianess, so that none of the Linux Tulip drivers will
> work out of the box...
A.k.a., Tulip (and possibly ThunderLAN) assume little-endian, when we're
talking big-endian archs here. Interesting. Simple fix, as in defining a
few driver structures with little- and big-endian versions (if they're doing
something like packing bits or using bitfields)? Or is it more complex than
that?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
^ permalink raw reply
* [U-Boot] [PATCH] Reintroduce MACH_TYPE_KM_KIRKWOOD for keymile ARM boards
From: Valentin Longchamp @ 2011-10-31 8:06 UTC (permalink / raw)
To: u-boot
We got dropped from Linux mach-types.h because of a lack of mainline
support and this is needed since the last Linux/u-boot mach-types
synchro.
Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
---
include/configs/km/km_arm.h | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/include/configs/km/km_arm.h b/include/configs/km/km_arm.h
index c117943..eaf6017 100644
--- a/include/configs/km/km_arm.h
+++ b/include/configs/km/km_arm.h
@@ -36,6 +36,9 @@
#ifndef _CONFIG_KM_ARM_H
#define _CONFIG_KM_ARM_H
+/* We got removed from Linux mach-types.h */
+#define MACH_TYPE_KM_KIRKWOOD 2255
+
/*
* High Level Configuration Options (easy to change)
*/
--
1.7.1
^ permalink raw reply related
* Re: [PATCH] drm: serialize access to debugs_nodes.list
From: Daniel Vetter @ 2011-10-31 8:06 UTC (permalink / raw)
To: Marcin Slusarz; +Cc: nouveau, dri-devel
In-Reply-To: <20111030220401.GA3628@joi.lan>
On Sun, Oct 30, 2011 at 11:04:48PM +0100, Marcin Slusarz wrote:
> Nouveau, when configured with debugfs, creates debugfs files for every
> channel, so structure holding list of files needs to be protected from
> simultaneous changes by multiple threads.
>
> Without this patch it's possible to hit kernel oops in
> drm_debugfs_remove_files just by running a couple of xterms with
> looped glxinfo.
>
> Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> ---
> drivers/gpu/drm/drm_debugfs.c | 5 +++++
> include/drm/drmP.h | 1 +
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_debugfs.c b/drivers/gpu/drm/drm_debugfs.c
> index 9d2668a..1144fbe 100644
> --- a/drivers/gpu/drm/drm_debugfs.c
> +++ b/drivers/gpu/drm/drm_debugfs.c
> @@ -120,7 +120,9 @@ int drm_debugfs_create_files(struct drm_info_list *files, int count,
> tmp->minor = minor;
> tmp->dent = ent;
> tmp->info_ent = &files[i];
> + mutex_lock(&minor->debugfs_nodes.mutex);
> list_add(&(tmp->list), &(minor->debugfs_nodes.list));
> + mutex_unlock(&minor->debugfs_nodes.mutex);
> }
> return 0;
>
> @@ -149,6 +151,7 @@ int drm_debugfs_init(struct drm_minor *minor, int minor_id,
> int ret;
>
> INIT_LIST_HEAD(&minor->debugfs_nodes.list);
> + mutex_init(&minor->debugfs_nodes.mutex);
> sprintf(name, "%d", minor_id);
> minor->debugfs_root = debugfs_create_dir(name, root);
> if (!minor->debugfs_root) {
> @@ -194,6 +197,7 @@ int drm_debugfs_remove_files(struct drm_info_list *files, int count,
> struct drm_info_node *tmp;
> int i;
>
> + mutex_lock(&minor->debugfs_nodes.mutex);
> for (i = 0; i < count; i++) {
> list_for_each_safe(pos, q, &minor->debugfs_nodes.list) {
> tmp = list_entry(pos, struct drm_info_node, list);
> @@ -204,6 +208,7 @@ int drm_debugfs_remove_files(struct drm_info_list *files, int count,
> }
> }
> }
> + mutex_unlock(&minor->debugfs_nodes.mutex);
> return 0;
> }
> EXPORT_SYMBOL(drm_debugfs_remove_files);
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index 9b7c2bb..c70c943 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -970,6 +970,7 @@ struct drm_info_list {
> * debugfs node structure. This structure represents a debugfs file.
> */
> struct drm_info_node {
> + struct mutex mutex;
> struct list_head list;
> struct drm_minor *minor;
> struct drm_info_list *info_ent;
This is just ugly, you're adding a mutex to every drm_info_node, but only
use the one embedded into the minor. On a quick grep we're only ever using
the list in there, so I suggest to
- replace minor->debugfs_node.list with minor->debugfs_list and kill
->debugfs_node
- add the mutex as minor->debugfs_lock
That way it's clear what's going on.
Also, you've forgotten to add the locking to i915/i915_debugfs.c
Yours, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
^ permalink raw reply
* Re: [Qemu-devel] [PATCH] qed: adjust the way to get nb_sectors
From: Kevin Wolf @ 2011-10-31 8:10 UTC (permalink / raw)
To: Zhi Yong Wu; +Cc: qemu-devel, stefanha
In-Reply-To: <1320030109-20476-1-git-send-email-wuzhy@linux.vnet.ibm.com>
Am 31.10.2011 04:01, schrieb Zhi Yong Wu:
> It is better to use qiov.size in qed-table.c to get nb_sectors than iov.iov_len.
>
> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
The commit message should probably say why it's better. Not saying
otherwise, but I can't see the different at the first sight.
Kevin
^ permalink raw reply
* Re: [GIT PULL rcu/next] RCU commits for 3.1
From: Li Zefan @ 2011-10-31 8:09 UTC (permalink / raw)
To: paulmck
Cc: Ingo Molnar, eric.dumazet, shaohua.li, ak, mhocko, alex.shi,
efault, linux-kernel, Peter Zijlstra, Paul Turner
In-Reply-To: <20111029182710.GG6160@linux.vnet.ibm.com>
(Let's cc Peter and Paul Turner for this perf cgroup issue.)
> Thank you for the analysis. Does the following patch fix this problem?
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> fs: Add RCU protection in set_task_comm()
>
> Running "perf stat true" results in the following RCU-lockdep splat:
>
> ===============================
> [ INFO: suspicious RCU usage. ]
> -------------------------------
> include/linux/cgroup.h:548 suspicious rcu_dereference_check() usage!
>
> other info that might help us debug this:
>
> rcu_scheduler_active = 1, debug_locks = 0
> 1 lock held by true/655:
> #0: (&sig->cred_guard_mutex){+.+.+.}, at: [<810d1bd7>] prepare_bprm_creds+0x27/0x70
>
> stack backtrace:
> Pid: 655, comm: true Not tainted 3.1.0-tip-01868-g1271bd2-dirty #161079
> Call Trace:
> [<81abe239>] ? printk+0x18/0x1a
> [<81064920>] lockdep_rcu_suspicious+0xc0/0xd0
> [<8108aa02>] perf_event_enable_on_exec+0x1d2/0x1e0
> [<81063764>] ? __lock_release+0x54/0xb0
> [<8108cca8>] perf_event_comm+0x18/0x60
> [<810d1abd>] ? set_task_comm+0x5d/0x80
> [<81af622d>] ? _raw_spin_unlock+0x1d/0x40
> [<810d1ac4>] set_task_comm+0x64/0x80
> [<810d25fd>] setup_new_exec+0xbd/0x1d0
> [<810d1b61>] ? flush_old_exec+0x81/0xa0
> [<8110753e>] load_elf_binary+0x28e/0xa00
> [<810d2101>] ? search_binary_handler+0xd1/0x1d0
> [<81063764>] ? __lock_release+0x54/0xb0
> [<811072b0>] ? load_elf_library+0x260/0x260
> [<810d2108>] search_binary_handler+0xd8/0x1d0
> [<810d2060>] ? search_binary_handler+0x30/0x1d0
> [<810d242f>] do_execve_common+0x22f/0x2a0
> [<810d24b2>] do_execve+0x12/0x20
> [<81009592>] sys_execve+0x32/0x70
> [<81af7752>] ptregs_execve+0x12/0x20
> [<81af76d4>] ? sysenter_do_call+0x12/0x36
>
> Li Zefan noted that this is due to set_task_comm() dropping the task
> lock before invoking perf_event_comm(), which could in fact result in
> the task being freed up before perf_event_comm() completed tracing in
> the case where one task invokes set_task_comm() on another task -- which
> actually does occur via comm_write(), which can be invoked via /proc.
>
This is not true. The caller should ensure @tsk is valid during
set_task_comm().
The warning comes from perf_cgroup_from_task(). We can trigger this warning
in some other cases where perf cgroup is used, for example:
# mount -t cgroup -o perf_event xxx /mnt
# ./perf record -a -e 'sched:*' -G / true
[ 171.603171] ===============================
[ 171.603173] [ INFO: suspicious RCU usage. ]
[ 171.603175] -------------------------------
[ 171.603178] include/linux/cgroup.h:548 suspicious rcu_dereference_check() usage!
[ 171.603180]
[ 171.603181] other info that might help us debug this:
[ 171.603182]
[ 171.603184]
[ 171.603185] rcu_scheduler_active = 1, debug_locks = 0
[ 171.603188] 2 locks held by perf/2899:
[ 171.603190] #0: (&cpuctx_mutex){+.+...}, at: [<c04b2fe7>] sys_perf_event_open+0x4ed/0x62a
[ 171.603201] #1: (&cpuctx_lock){......}, at: [<c04ac4bc>] perf_ctx_lock+0xe/0x1d
[ 171.603210]
[ 171.603211] stack backtrace:
[ 171.603214] Pid: 2899, comm: perf Not tainted 3.1.0+ #12
[ 171.603216] Call Trace:
[ 171.603222] [<c07e7234>] ? printk+0x25/0x29
[ 171.603227] [<c046279d>] lockdep_rcu_suspicious+0x90/0x9b
[ 171.603232] [<c04ac688>] perf_cgroup_from_task+0x5e/0x64
[ 171.603236] [<c04adfe7>] update_cgrp_time_from_event.clone.18+0x16/0x25
[ 171.603240] [<c04b01a1>] __perf_install_in_context+0xa0/0xcf
[ 171.603244] [<c04ac355>] ? pmu_dev_release+0xa/0xa
[ 171.603248] [<c04ac386>] remote_function+0x31/0x37
[ 171.603253] [<c0468aaa>] smp_call_function_single+0x7d/0xf5
[ 171.603257] [<c04ac41d>] cpu_function_call+0x29/0x2e
[ 171.603261] [<c04b0101>] ? perf_pm_suspend_cpu+0x9f/0x9f
[ 171.603264] [<c04ae85b>] perf_install_in_context+0x53/0x9f
[ 171.603268] [<c04b3033>] sys_perf_event_open+0x539/0x62a
[ 171.603273] [<c04566f5>] ? up_read+0x1b/0x2e
[ 171.603277] [<c07ec856>] ? do_page_fault+0x2e6/0x314
[ 171.603283] [<c07ef2df>] sysenter_do_call+0x12/0x38
> This commit fixes this problem by entering an RCU read-side critical
> section before acquiring the task lock and exiting this critical section
> after perf_event_comm() returns.
>
> Reported-by: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 25dcbe5..fb928d3 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1056,6 +1056,7 @@ EXPORT_SYMBOL_GPL(get_task_comm);
>
> void set_task_comm(struct task_struct *tsk, char *buf)
> {
> + rcu_read_lock(); /* protect task pointer through tracing. */
> task_lock(tsk);
>
> /*
> @@ -1069,6 +1070,7 @@ void set_task_comm(struct task_struct *tsk, char *buf)
> strlcpy(tsk->comm, buf, sizeof(tsk->comm));
> task_unlock(tsk);
> perf_event_comm(tsk);
> + rcu_read_unlock();
> }
>
> int flush_old_exec(struct linux_binprm * bprm)
>
^ permalink raw reply
* [U-Boot] [PATCH 3/4] EHCI: adjust for mx5
From: Igor Grinberg @ 2011-10-31 8:11 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1317253971-24558-4-git-send-email-fermata7@gmail.com>
Hi Jana,
On 09/29/11 02:52, Jana Rapava wrote:
> Add macros and structures needed by Efika USB support code.
> Move shared offset and bits definitions into common header file.
>
> Signed-off-by: Jana Rapava <fermata7@gmail.com>
> Cc: Marek Vasut <marek.vasut@gmail.com>
> Cc: Remy Bohmer <linux@bohmer.net>
> Cc: Stefano Babic <sbabic@denx.de>
> ---
> drivers/usb/host/ehci-mxc.c | 31 +--------
> include/usb/ehci-fsl.h | 146 ++++++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 148 insertions(+), 29 deletions(-)
>
[...]
> diff --git a/include/usb/ehci-fsl.h b/include/usb/ehci-fsl.h
> index 67600ed..727134f 100644
> --- a/include/usb/ehci-fsl.h
> +++ b/include/usb/ehci-fsl.h
[...]
> @@ -169,6 +169,106 @@
> #define CONFIG_SYS_FSL_USB_ADDR CONFIG_SYS_MPC512x_USB_ADDR
> #endif
>
> +#if defined(CONFIG_MX25) || defined(CONFIG_MX31)
> +#define USBCTRL_OTGBASE_OFFSET 0x600
> +#endif
> +
> +#ifdef CONFIG_MX25
> +#define MX25_USB_CTRL_IP_PUE_DOWN_BIT (1<<6)
> +#define MX25_USB_CTRL_HSTD_BIT (1<<5)
> +#define MX25_USB_CTRL_USBTE_BIT (1<<4)
> +#define MX25_USB_CTRL_OCPOL_OTG_BIT (1<<3)
Why not align the above?
Also, there should be spaces around the shift operators.
> +#endif
> +
> +#ifdef CONFIG_MX31
> +#define MX31_H2_SIC_SHIFT 21
> +#define MX31_H2_SIC_MASK (0x3 << MX31_H2_SIC_SHIFT)
> +#define MX31_H2_PM_BIT (1 << 16)
> +#define MX31_H2_DT_BIT (1 << 5)
Alignment?
> +
> +#define MX31_H1_SIC_SHIFT 13
> +#define MX31_H1_SIC_MASK (0x3 << MX31_H1_SIC_SHIFT)
> +#define MX31_H1_PM_BIT (1 << 8)
> +#define MX31_H1_DT_BIT (1 << 4)
ditto
> +#endif
> +
> +#if defined(CONFIG_MX51) || defined(CONFIG_MX53)
> +/* offset for first USB CTRL register */
> +#define MX5_CTRL_REGS_OFFSET 0x800
> +#endif
> +
> +#if defined(CONFIG_MX51) || defined(CONFIG_MX31)
> +/* USB_CTRL register bits of interest*/
> +#define MXC_OTG_SIC_SHIFT 29
> +#define MXC_OTG_SIC_MASK (0x3 << MX31_OTG_SIC_SHIFT)
> +#define MXC_OTG_WUE (1 << 27)
> +#define MXC_OTG_PM (1 << 24)
> +#endif
> +
> +#ifdef CONFIG_MX51
> +#define MX51_REGISTER_LAYOUT_LENGTH 0x200
> +
> +/* Register offsets for MX51 */
> +#define MX51_OTG_ID 0x000
> +#define MX51_UH1_ID 0x200
> +#define MX51_UH2_ID 0x400
> +
> +/* USB_CTRL register bits of interest*/
> +#define MX51_OTG_PM (1 << 24)
> +#define MX51_H1_ULPI_IE (1 << 12)
> +#define MX51_H1_WUE (1 << 11)
> +#define MX51_H1_PM (1 << 8)
> +
> +/* PHY_CTRL_0 register bits of interest */
> +#define MX51_OTG_OVERCURD (1 << 8)
> +#define MX51_EHCI_POWERPINSE (1 << 5)
> +
> +/* PHY_CTRL_1 register bits of interest */
> +#define MX51_SYSCLOCK_24_MHZ (1 << 0)
> +#define MX51_SYSCLOCK_MASK (~(0xffffffff << 2))
This is something, I don't understand.
Isn't it just 0x3?
> +
> +/* USB_CTRL_1 register bits of interest */
> +#define MX51_H1_EXTCLKE (1 << 25)
> +
> +/* USB Host 2 CTRL register bits of interest */
> +#define MX51_H2_ULPI_IE (1 << 8)
> +#define MX51_H2_WUE (1 << 7)
> +#define MX51_H2_PM (1 << 4)
> +
> +/* PORTSCx bits of interest */
> +#define MX51_ULPI_MODE_MASK (2 << 30)
> +#define MX51_16BIT_UTMI (1 << 28)
> +
> +/* USBCMD bits of interest */
> +#define MX51_ITC_IMMEDIATE_MASK (0xff << 16)
> +#endif
> +
> +/*
> +* ULPI
> +*/
Something went wrong with the comment formatting here...
> +#define ULPI_ID_REGS_COUNT 4
> +#define ULPI_TEST_VALUE 0x55
> +#define ULPI_TIMEOUT 1000 /* some reasonable value */
> +
> +/* ULPI viewport control bits */
> +#define ULPI_WU (1 << 31)
> +#define ULPI_SS (1 << 27)
> +#define ULPI_RWRUN (1 << 30)
> +#define ULPI_RWCTRL (1 << 29)
> +
> +/* ULPI OTG Control bits of interest */
> +#define ULPI_OTG_EXT_VBUS_IND (1 << 7)
> +#define ULPI_OTG_DM_PULLDOWN (1 << 2)
> +#define ULPI_OTG_DP_PULLDOWN (1 << 1)
> +#define ULPI_OTG_DRV_VBUS (1 << 5)
> +#define ULPI_OTG_DRV_VBUS_EXT (1 << 6)
> +#define ULPI_OTG_CHRG_VBUS (1 << 4)
alignment
> +
> +/* ULPI Function Control bits of interest */
> +#define ULPI_FC_XCVR_SELECT (1 << 0)
> +#define ULPI_FC_OPMODE_NORMAL (0 << 3)
> +#define ULPI_FC_SUSPENDM_PWRED (1 << 6)
ditto
[...]
> +
> +struct mxc_ulpi_regs {
> + u8 vendor_id_low; /* 0x00 - Vendor ID lower byte */
> + u8 vendor_id_high; /* 0x01 - Vendor ID upper byte */
> + u8 product_id_low; /* 0x02 - Product ID lower byte */
> + u8 product_id_high; /* 0x03 - Product ID higher byte */
> + /* Function Control; 0x04 - 0x06 Read, 0x04 Write */
> + u8 function_ctrl_write;
> + u8 function_ctrl_set; /* 0x05 Set */
> + u8 function_ctrl_clear; /* 0x06 Clear */
> + /* Interface Control; 0x07 - 0x09 Read, 0x07 Write */
> + u8 iface_ctrl_write;
> + u8 iface_ctrl_set; /* 0x08 Set */
> + u8 iface_ctrl_clear; /* 0x09 Clear */
> + /* OTG Control; 0x0A - 0x0C Read, 0x0A Write */
> + u8 otg_ctrl_write;
> + u8 otg_ctrl_set; /* 0x0B Set */
> + u8 otg_ctrl_clear; /* 0x0C Clear */
> + /* USB Interrupt Enable Rising; 0x0D - 0x0F Read, 0x0D Write */
> + u8 usb_ie_rising_write;
> + u8 usb_ie_rising_set; /* 0x0E Set */
> + u8 usb_ie_rising_clear; /* 0x0F Clear */
> + /* USB Interrupt Enable Falling; 0x10 - 0x12 Read, 0x10 Write */
> + u8 usb_ie_falling_write;
> + u8 usb_ie_falling_set; /* 0x11 Set */
> + u8 usb_ie_falling_clear; /* 0x12 Clear */
> + u8 usb_int_status; /* 0x13 - USB Interrupt Status */
> + u8 usb_int_latch; /* 0x14 - USB Interrupt Latch */
> + u8 debug; /* 0x15 - Debug */
> + /* Scratch Register; 0x16 - 0x18 Read, 0x16 Write */
> + u8 scratch_write;
> + u8 scratch_set; /* 0x17 Set */
> + u8 scratch_clear; /* 0x18 Clear*/
> +};
These are the generic ULPI specification registers
and not mxc specific.
I'd expect to have them in a more generic location.
> +
> #endif /* _EHCI_FSL_H */
--
Regards,
Igor.
^ permalink raw reply
* [U-Boot] [PATCH] gplugD: Fix for error:MACH_TYPE_SHEEVAD undeclared
From: Igor Grinberg @ 2011-10-31 8:11 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1320046607-14445-1-git-send-email-ajay.bhargav@einfochips.com>
On 10/31/11 09:36, Ajay Bhargav wrote:
> This patch fix the build failure (error: 'MACH_TYPE_SHEEVAD' undeclared
> (first use in this function)) for gplugD due to recent sync of
> mach-types.h with its linux original.
>
> Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
Acked-by: Igor Grinberg <grinberg@compulab.co.il>
> ---
> include/configs/gplugd.h | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/include/configs/gplugd.h b/include/configs/gplugd.h
> index 24bf767..9813309 100644
> --- a/include/configs/gplugd.h
> +++ b/include/configs/gplugd.h
> @@ -32,6 +32,16 @@
> #define __CONFIG_GPLUGD_H
>
> /*
> + * FIXME: fix for error caused due to recent update to mach-types.h
> + */
> +#include <asm/mach-types.h>
> +#ifdef MACH_TYPE_SHEEVAD
> +#error "MACH_TYPE_SHEEVAD has been defined properly, please remove this."
> +#else
> +#define MACH_TYPE_SHEEVAD 2625
> +#endif
> +
> +/*
> * Version number information
> */
> #define CONFIG_IDENT_STRING "\nMarvell-gplugD"
> @@ -42,7 +52,7 @@
> #define CONFIG_SHEEVA_88SV331xV5 1 /* CPU Core subversion */
> #define CONFIG_ARMADA100 1 /* SOC Family Name */
> #define CONFIG_ARMADA168 1 /* SOC Used on this Board */
> -#define CONFIG_MACH_SHEEVAD /* Machine type */
> +#define CONFIG_MACH_TYPE MACH_TYPE_SHEEVAD /* Machine type */
> #define CONFIG_SKIP_LOWLEVEL_INIT /* disable board lowlevel_init */
>
> #define CONFIG_SYS_TEXT_BASE 0x00f00000
--
Regards,
Igor.
^ permalink raw reply
* RE: [GIT PULL] mm: frontswap (for 3.2 window)
From: James Bottomley @ 2011-10-31 8:12 UTC (permalink / raw)
To: Dan Magenheimer
Cc: John Stoffel, Johannes Weiner, Pekka Enberg, Cyclonus J,
Sasha Levin, Christoph Hellwig, David Rientjes, Linus Torvalds,
linux-mm, LKML, Andrew Morton, Konrad Wilk, Jeremy Fitzhardinge,
Seth Jennings, ngupta, Chris Mason, JBeulich, Dave Hansen,
Jonathan Corbet
In-Reply-To: <3982e04f-8607-4f0a-b855-2e7f31aaa6f7@default>
On Fri, 2011-10-28 at 13:19 -0700, Dan Magenheimer wrote:
> For those who "hack on the VM", I can't imagine why the handful
> of lines in the swap subsystem, which is probably the most stable
> and barely touched subsystem in Linux or any OS on the planet,
> is going to be a burden or much of a cost.
Saying things like this doesn't encourage anyone to trust you. The
whole of the MM is a complex, highly interacting system. The recent
issues we've had with kswapd and the shrinker code gives a nice
demonstration of this ... and that was caused by well tested code
updates. You can't hand wave away the need for benchmarks and
performance tests.
You have also answered all questions about inactive cost by saying "the
code has zero cost when it's compiled out" This also is a non starter.
For the few use cases it has, this code has to be compiled in. I
suspect even Oracle isn't going to ship separate frontswap and
non-frontswap kernels in its distro. So you have to quantify what the
performance impact is when this code is compiled in but not used.
Please do so.
James
^ permalink raw reply
* RE: [GIT PULL] mm: frontswap (for 3.2 window)
From: James Bottomley @ 2011-10-31 8:12 UTC (permalink / raw)
To: Dan Magenheimer
Cc: John Stoffel, Johannes Weiner, Pekka Enberg, Cyclonus J,
Sasha Levin, Christoph Hellwig, David Rientjes, Linus Torvalds,
linux-mm, LKML, Andrew Morton, Konrad Wilk, Jeremy Fitzhardinge,
Seth Jennings, ngupta, Chris Mason, JBeulich, Dave Hansen,
Jonathan Corbet
In-Reply-To: <3982e04f-8607-4f0a-b855-2e7f31aaa6f7@default>
On Fri, 2011-10-28 at 13:19 -0700, Dan Magenheimer wrote:
> For those who "hack on the VM", I can't imagine why the handful
> of lines in the swap subsystem, which is probably the most stable
> and barely touched subsystem in Linux or any OS on the planet,
> is going to be a burden or much of a cost.
Saying things like this doesn't encourage anyone to trust you. The
whole of the MM is a complex, highly interacting system. The recent
issues we've had with kswapd and the shrinker code gives a nice
demonstration of this ... and that was caused by well tested code
updates. You can't hand wave away the need for benchmarks and
performance tests.
You have also answered all questions about inactive cost by saying "the
code has zero cost when it's compiled out" This also is a non starter.
For the few use cases it has, this code has to be compiled in. I
suspect even Oracle isn't going to ship separate frontswap and
non-frontswap kernels in its distro. So you have to quantify what the
performance impact is when this code is compiled in but not used.
Please do so.
James
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* [U-Boot] [PATCH 1/5] arm/km: adapt bootcounter evaluation
From: Holger Brunck @ 2011-10-31 8:13 UTC (permalink / raw)
To: u-boot
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A14DD8804@SC-VEXCH4.marvell.com>
On 10/31/2011 08:29 AM, Prafulla Wadaskar wrote:
>
>
>> -----Original Message-----
>> From: Holger Brunck [mailto:holger.brunck at keymile.com]
>> Sent: Friday, October 28, 2011 6:43 PM
>> To: Prafulla Wadaskar
>> Cc: u-boot at lists.denx.de; Valentin Longchamp
>> Subject: Re: [PATCH 1/5] arm/km: adapt bootcounter evaluation
>>
>> Hi Prafulla,
>>
>> On 09/14/2011 10:41 AM, Holger Brunck wrote:
>>> The bootcounter (stored in the RAM) is not enough protected
>> with the 4 Bytes
>>> BOOTCOUNT_MAGIC against bit errors due to short power loss or
>> holding a system
>>> in RESET. It has been seen, that the bootcounter value has
>> been changed due to
>>> a bit flip on a system holding in RESET, but the
>> BOOTCOUNT_MAGIC was still valid.
>>>
>>> A bit pattern with 4000 bytes (after BOOTCOUNT_MAGIC) has
>> been implemented,
>>> which should be enough to detect a bit error.
>>>
>>> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
>>> Signed-off-by: Valentin Longchamp
>> <valentin.longchamp@keymile.com>
>>> cc: Prafulla Wadaskar <prafulla@marvell.com>
>>> ---
>>> board/keymile/km_arm/km_arm.c | 32
>> +++++++++++++++++++++++++++-----
>>> 1 files changed, 27 insertions(+), 5 deletions(-)
>>>
>>
>> ...ping...
>>
>> Or should this serie not go through your tree? If so then
>> please let me know.
>
> Generally not, this was done earlier by Wolfgang or Albert.
> So I was assuming someone will pull.
>
Hm, in the past the patches for keymile ARM boards go through your tree Prafulla.
Anyway Wolfgang or Albert, who should pick up the patches for our Keymile
Kirkwood boards?
This two series have only board specific patches:
http://lists.denx.de/pipermail/u-boot/2011-September/101328.html
http://lists.denx.de/pipermail/u-boot/2011-September/102534.html
Best regards
Holger
^ permalink raw reply
* [PATCH] oom: fix integer overflow of points in oom_badness
From: Frantisek Hrbata @ 2011-10-31 8:14 UTC (permalink / raw)
To: rientjes
Cc: linux-mm, linux-kernel, akpm, kosaki.motohiro, oleg, minchan.kim,
stable, eteo, pmatouse
An integer overflow will happen on 64bit archs if task's sum of rss, swapents
and nr_ptes exceeds (2^31)/1000 value. This was introduced by commit
f755a04 oom: use pte pages in OOM score
where the oom score computation was divided into several steps and it's no
longer computed as one expression in unsigned long(rss, swapents, nr_pte are
unsigned long), where the result value assigned to points(int) is in
range(1..1000). So there could be an int overflow while computing
176 points *= 1000;
and points may have negative value. Meaning the oom score for a mem hog task
will be one.
196 if (points <= 0)
197 return 1;
For example:
[ 3366] 0 3366 35390480 24303939 5 0 0 oom01
Out of memory: Kill process 3366 (oom01) score 1 or sacrifice child
Here the oom1 process consumes more than 24303939(rss)*4096~=92GB physical
memory, but it's oom score is one.
In this situation the mem hog task is skipped and oom killer kills another and
most probably innocent task with oom score greater than one.
This patch puts the computation of points back in one expression, so the int
overflow will not happen.
My understanding is that we may just change the type of points variable from int
to long and keep the current imho clearer(better readable) computation. There
should not be an overflow on 32bit and there is a plenty of space for 64bit.
If you like this solution better I will post the patch as v2.
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
---
mm/oom_kill.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 626303b..d029e9b 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -192,11 +192,9 @@ unsigned int oom_badness(struct task_struct *p, struct mem_cgroup *mem,
* The baseline for the badness score is the proportion of RAM that each
* task's rss, pagetable and swap space use.
*/
- points = get_mm_rss(p->mm) + p->mm->nr_ptes;
- points += get_mm_counter(p->mm, MM_SWAPENTS);
+ points = (int)((get_mm_rss(p->mm) + get_mm_counter(p->mm, MM_SWAPENTS) +
+ p->mm->nr_ptes) * 1000UL / totalpages);
- points *= 1000;
- points /= totalpages;
task_unlock(p);
/*
--
1.7.6.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply related
* [PATCH] oom: fix integer overflow of points in oom_badness
From: Frantisek Hrbata @ 2011-10-31 8:14 UTC (permalink / raw)
To: rientjes
Cc: linux-mm, linux-kernel, akpm, kosaki.motohiro, oleg, minchan.kim,
stable, eteo, pmatouse
An integer overflow will happen on 64bit archs if task's sum of rss, swapents
and nr_ptes exceeds (2^31)/1000 value. This was introduced by commit
f755a04 oom: use pte pages in OOM score
where the oom score computation was divided into several steps and it's no
longer computed as one expression in unsigned long(rss, swapents, nr_pte are
unsigned long), where the result value assigned to points(int) is in
range(1..1000). So there could be an int overflow while computing
176 points *= 1000;
and points may have negative value. Meaning the oom score for a mem hog task
will be one.
196 if (points <= 0)
197 return 1;
For example:
[ 3366] 0 3366 35390480 24303939 5 0 0 oom01
Out of memory: Kill process 3366 (oom01) score 1 or sacrifice child
Here the oom1 process consumes more than 24303939(rss)*4096~=92GB physical
memory, but it's oom score is one.
In this situation the mem hog task is skipped and oom killer kills another and
most probably innocent task with oom score greater than one.
This patch puts the computation of points back in one expression, so the int
overflow will not happen.
My understanding is that we may just change the type of points variable from int
to long and keep the current imho clearer(better readable) computation. There
should not be an overflow on 32bit and there is a plenty of space for 64bit.
If you like this solution better I will post the patch as v2.
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
---
mm/oom_kill.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 626303b..d029e9b 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -192,11 +192,9 @@ unsigned int oom_badness(struct task_struct *p, struct mem_cgroup *mem,
* The baseline for the badness score is the proportion of RAM that each
* task's rss, pagetable and swap space use.
*/
- points = get_mm_rss(p->mm) + p->mm->nr_ptes;
- points += get_mm_counter(p->mm, MM_SWAPENTS);
+ points = (int)((get_mm_rss(p->mm) + get_mm_counter(p->mm, MM_SWAPENTS) +
+ p->mm->nr_ptes) * 1000UL / totalpages);
- points *= 1000;
- points /= totalpages;
task_unlock(p);
/*
--
1.7.6.4
^ permalink raw reply related
* Re: [GIT PULL] mm: frontswap (for 3.2 window)
From: KAMEZAWA Hiroyuki @ 2011-10-31 8:13 UTC (permalink / raw)
To: Dan Magenheimer
Cc: Linus Torvalds, linux-mm, LKML, Andrew Morton, Konrad Wilk,
Jeremy Fitzhardinge, Seth Jennings, ngupta, levinsasha928,
Chris Mason, JBeulich, Dave Hansen, Jonathan Corbet, Neo Jia
In-Reply-To: <b2fa75b6-f49c-4399-ba94-7ddf08d8db6e@default>
On Thu, 27 Oct 2011 11:52:22 -0700 (PDT)
Dan Magenheimer <dan.magenheimer@oracle.com> wrote:
> Hi Linus --
>
> Frontswap now has FOUR users: Two already merged in-tree (zcache
> and Xen) and two still in development but in public git trees
> (RAMster and KVM). Frontswap is part 2 of 2 of the core kernel
> changes required to support transcendent memory; part 1 was cleancache
> which you merged at 3.0 (and which now has FIVE users).
>
> Frontswap patches have been in linux-next since June 3 (with zero
> changes since Sep 22). First posted to lkml in June 2009, frontswap
> is now at version 11 and has incorporated feedback from a wide range
> of kernel developers. For a good overview, see
> http://lwn.net/Articles/454795.
> If further rationale is needed, please see the end of this email
> for more info.
>
> SO... Please pull:
>
> git://oss.oracle.com/git/djm/tmem.git #tmem
>
> since git commit b6fd41e29dea9c6753b1843a77e50433e6123bcb
> Linus Torvalds (1):
>
Why bypass -mm tree ?
I think you planned to merge this via -mm tree and, then, posted patches
to linux-mm with CC -mm guys.
I think you posted 2011/09/16 at the last time, v10. But no further submission
to gather acks/reviews from Mel, Johannes, Andrew, Hugh etc.. and no inclusion
request to -mm or -next. _AND_, IIUC, at v10, the number of posted pathces was 6.
Why now 8 ? Just because it's simple changes ?
I don't have heavy concerns to the codes itself but this process as bypassing -mm
or linux-next seems ugly.
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: [GIT PULL] mm: frontswap (for 3.2 window)
From: KAMEZAWA Hiroyuki @ 2011-10-31 8:13 UTC (permalink / raw)
To: Dan Magenheimer
Cc: Linus Torvalds, linux-mm, LKML, Andrew Morton, Konrad Wilk,
Jeremy Fitzhardinge, Seth Jennings, ngupta, levinsasha928,
Chris Mason, JBeulich, Dave Hansen, Jonathan Corbet, Neo Jia
In-Reply-To: <b2fa75b6-f49c-4399-ba94-7ddf08d8db6e@default>
On Thu, 27 Oct 2011 11:52:22 -0700 (PDT)
Dan Magenheimer <dan.magenheimer@oracle.com> wrote:
> Hi Linus --
>
> Frontswap now has FOUR users: Two already merged in-tree (zcache
> and Xen) and two still in development but in public git trees
> (RAMster and KVM). Frontswap is part 2 of 2 of the core kernel
> changes required to support transcendent memory; part 1 was cleancache
> which you merged at 3.0 (and which now has FIVE users).
>
> Frontswap patches have been in linux-next since June 3 (with zero
> changes since Sep 22). First posted to lkml in June 2009, frontswap
> is now at version 11 and has incorporated feedback from a wide range
> of kernel developers. For a good overview, see
> http://lwn.net/Articles/454795.
> If further rationale is needed, please see the end of this email
> for more info.
>
> SO... Please pull:
>
> git://oss.oracle.com/git/djm/tmem.git #tmem
>
> since git commit b6fd41e29dea9c6753b1843a77e50433e6123bcb
> Linus Torvalds (1):
>
Why bypass -mm tree ?
I think you planned to merge this via -mm tree and, then, posted patches
to linux-mm with CC -mm guys.
I think you posted 2011/09/16 at the last time, v10. But no further submission
to gather acks/reviews from Mel, Johannes, Andrew, Hugh etc.. and no inclusion
request to -mm or -next. _AND_, IIUC, at v10, the number of posted pathces was 6.
Why now 8 ? Just because it's simple changes ?
I don't have heavy concerns to the codes itself but this process as bypassing -mm
or linux-next seems ugly.
Thanks,
-Kame
^ permalink raw reply
* [U-Boot] [PATCH v6 4/4] usb: add USB support for Efika
From: Igor Grinberg @ 2011-10-31 8:17 UTC (permalink / raw)
To: u-boot
In-Reply-To: <4EADB213.5040401@denx.de>
Hi Stefano,
On 10/30/11 22:22, Stefano Babic wrote:
> On 10/30/2011 09:18 PM, Marek Vasut wrote:
>>> This commit adds USB support for EfikaMX and EfikaSB.
>>>
>>> Signed-off-by: Jana Rapava <fermata7@gmail.com>
>>> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
>>> Cc: Remy Bohmer <linux@bohmer.net>
>>> Cc: Stefano Babic <sbabic@denx.de>
>>>
>>> Acked-by: Marek Vasut <marek.vasut@gmail.com>
>>> ---
>>> Changes for v2:
>>> - introduce temporary variable in ulpi_write
>>> - whitespace changes
>>> Changes for v3:
>>> - add protection against multiple inclusion of efika.h
>>> Changes for v4:
>>> - rename multiple inclusion protection macro in efika.h
>>> Changes for v5:
>>> - fix unterminated #ifndef in efika.h
>>> Changes for v6:
>>> - add Acked-by
>>> - no changes
>>>
>>
>> Guys, there's been no update on this for a month.
>>
>> Stefano, can you apply please? I see no negative comments.
>
> I do not have seen any open issues, too. If nobody argues and because
> they are related to USB for i.MX boards, I will apply them to u-boot-imx.
Sorry for jumping in that late.
I've just got back from my trip.
There are some issues with: [PATCH 3/4] EHCI: adjust for mx5
If you have already applied it and also because I don't want
to block this patch set, the issues I've pointed can be fixed
in a follow up patch.
>
> Best regards,
> Stefano Babic
>
>
--
Regards,
Igor.
^ permalink raw reply
* Re: Re: Re: HT (Hyper Threading) aware process scheduling doesn't work as it should
From: Artem S. Tashkinov @ 2011-10-31 8:18 UTC (permalink / raw)
To: yong.zhang0; +Cc: arjan, linux-kernel, mingo, peterz
In-Reply-To: <20111031031907.GB18057@zhy>
>
> (Cc'ing more people)
>
> Maybe you can also show your test case here?
>
The test case is perfectly outlined in the first message I posted to LKML but I
can repeat it for you ( https://lkml.org/lkml/2011/10/30/106 ).
On a HT enabled completely idle system run as many different tasks as you have
real CPU cores, e.g. on an Intel Core i7 2600 CPU, that will be four tasks.
For the best performance all tasks should be attached to different physical cores.
However often the opposite behaviour can be observed, the process scheduler
binds pairs of tasks to virtual HT cores of the same physical CPU module, e.g.
in theory you should get this distribution of tasks: 1:3:5:7 but often I get this
distribution 1:6:7:8 (three physical cores loaded instead of four) or 1:2:7:8 (two
physical cores loaded instead of four).
Artem
^ permalink raw reply
* Re: [git patches] libata updates, GPG signed (but see admin notes)
From: James Bottomley @ 2011-10-31 8:19 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Jeff Garzik, Andrew Morton, linux-ide, LKML
In-Reply-To: <CA+55aFx1NGWfNJAKDTvZfsHDDKiEtS4t4RydSgHurBeyGPyhXg@mail.gmail.com>
On Sun, 2011-10-30 at 10:12 -0700, Linus Torvalds wrote:
> On Sun, Oct 30, 2011 at 3:05 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > You can fix this by using mime and detached signatures as well but I
> > wouldn't worry too much about it. What emerged at KS is that Linus uses
> > gmail and gmail has no integration with pgp, thus pgp signing of pull
> > requests is superfluous since Linus won't add the steps of saving the
> > message to a text file and manually running pgp over it to verify
> > because of the huge elongation in workflow this causes especially during
> > a merge window.
>
> Actually, I have been running "gpg --verify" on the email that use the
> standard PGP encapsulation (ie the kind that Jeff used, that has
> "-----BEGIN PGP SIGNED MESSAGE-----" in it.
>
> It's the rfc3516-type email (aka protocol="application/pgp-encrypted")
> type that I can't even verify, because that's not something that gpg
> knows inherently how to check: you have to decode the message the
> right way and know what the rules are, and I have no intention of
> trying to figure it out. I have yet to find any usable tool that is
> able to check it, and I'm certainly not going to waste time trying to
> parse the rfc and write my own.
OK, so I get clearly no partial PGP messages and no using rfc3516
formatted pgp mail.
> That said, even the "BEGIN PGP SIGNED MESSAGE" things are a massive
> pain in the butt. We need to automate this some sane way, both for the
> sender and for the recipient.
But this doesn't help with what practise you want us to follow. Do you
want us to send full signed email using pgp encapsulation for pull
requests in spite of the mangling it does to attached patches and the
amount of extra pain it causes you? Or is relying on looking at the
received headers and always using public email lists to detect spoofing
by revocation OK until we find a mechanism for integrating pgp into git?
James
^ permalink raw reply
* [Cluster-devel] [fence-virt PATCH] backend plugin for monitoring a host's status
From: Kazunori INOUE @ 2011-10-31 8:19 UTC (permalink / raw)
To: cluster-devel.redhat.com
In-Reply-To: <4EA763D9.8080105@redhat.com>
Hi, Lon
(2011/10/26 10:35), Lon Hohberger wrote:
> On 10/05/2011 04:56 AM, Kazunori INOUE wrote:
>> Hi all,
>>
>> I think that the communication function of fence-virt is flexible,
>> so I want to use it more effectively.
>>
>> Therefore I made backend plugin for a guest to get the host's status
>> using the communication facility of fence-virt,
>> and I changed to allow specifying one more backend (for fencing, and
>> replying the host's status).
>>
>> I created the backend "pm-monitor" which has met the following
>> configurations / requirements.
>> - Both hosts and VMs, cluster (Pacemaker) have been configured.
>>
>> Here's an overview of function. Please refer to attached 'overview.png'.
>> (*) pingd resource notifies the status of connection with a specific
>> host to pacemaker, and pacemaker manages the result.
>> (1) resource (vm-client) which requires the host's status is executed.
>> (2) vm-client requests 'host_status (result of pingd)' to the host
>> with fence_virt.
>> (3) use the serial listener,
>> (4) fence_virtd (pm-monitor backend) gets the 'result of pingd' from
>> pacemaker and answers it after conversion.
>> - the conversion rule is set in /etc/pm-monitor.conf
>
> Originally, the devstatus callback was supposed to be what provided the
> answer to the question "is my fencing [device|host] operational?" - but
> your patch is more than that, it looks like a generalized way to do
> arbitrary request/response pacemaker resource monitoring from within VMs.
>
> That kind of monitoring is interesting.
>
>> Here's a description of the attached files.
>> * add_general_backend.patch
>> - add the server/pm-fence.c
>> - change the configure.in and server/Makefile.in
>
> I think I understand how it operates; your explanation is very detailed.
>
> * I don't quite understand all of the benefits. Presumably, one uses
> the serial configuration to prevent guests/hosts from sharing the same
> networks - i.e., it's designed for environments where guests and hosts
> are not allowed to talk over the network to each other. So, presumably,
> we're using this to indirectly monitor an IP on the host network, using
> fence-virt as a bridge. What I don't understand is the benefit to the
> virtual machine cluster in doing this.
>
> * Do you see other uses besides monitoring pingd sets?
>
Yes, VM can get the status of host's hardware (status of disk, status
of CPU, etc.) if the following RAs are running on the host.
- HealthCPU
- SysInfo
- diskd (disk monitor RA - published only in Japanese community.
http://hg.sourceforge.jp/view/linux-ha/pm_diskd/)
Since such RA writes status of hardware into the CIB(*), vm-client can
specify the attribute and can get it's value.
(*) example of the CIB
# cibadmin -Q
<cib>
<status>
<node_state ...>
<transient_attributes ...>
<instance_attributes ...>
<nvpair id="..." name="default_ping_set" value="100"/>
<nvpair id="..." name="#health-cpu" value="green"/>
<nvpair id="..." name="diskd" value="normal"/>
:
Our final purpose is to get the status of host's hardware who cannot
perform acquisition directly from a guest by this way.
> * It may be that this new project may be a better "backbone" for this
> sort of general request/response than fence-virt; it's a much more
> general communications medium for guest<->host communication:
>
> http://git.fedorahosted.org/git/?p=vios-proxy.git
>
> (although it is written in C++ ;) ).
>
OK, thank you. We will also see it.
>
> Notes about the patch itself:
>
> * no support for multicast listener (this looks intentional -
> is it?)
>
Yes. This patch is only support for serial listener.
Best Regards,
Kazunori INOUE
> * this will break on-wire compatibility; we need to be very careful
> here.
>
> * some duplicate build system changes with the other
> patch (not a big deal)
>
> * [not directly related to your patch] the vmchannel/serial support
> in fence-virt probably should be replaced with more recent
> technology in libvirt
>
> -- Lon
^ permalink raw reply
* [U-Boot] [PATCH] gplugD: Fix for error:MACH_TYPE_SHEEVAD undeclared
From: Prafulla Wadaskar @ 2011-10-31 8:20 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1320046607-14445-1-git-send-email-ajay.bhargav@einfochips.com>
> -----Original Message-----
> From: Ajay Bhargav [mailto:ajay.bhargav at einfochips.com]
> Sent: Monday, October 31, 2011 1:07 PM
> To: Prafulla Wadaskar
> Cc: u-boot at lists.denx.de; albert.u.boot at aribaud.net;
> marek.vasut at gmail.com; Ajay Bhargav
> Subject: [PATCH] gplugD: Fix for error:MACH_TYPE_SHEEVAD
> undeclared
>
> This patch fix the build failure (error: 'MACH_TYPE_SHEEVAD'
> undeclared
> (first use in this function)) for gplugD due to recent sync of
> mach-types.h with its linux original.
>
> Signed-off-by: Ajay Bhargav <ajay.bhargav@einfochips.com>
> ---
> include/configs/gplugd.h | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/include/configs/gplugd.h
> b/include/configs/gplugd.h
> index 24bf767..9813309 100644
> --- a/include/configs/gplugd.h
> +++ b/include/configs/gplugd.h
> @@ -32,6 +32,16 @@
> #define __CONFIG_GPLUGD_H
>
> /*
> + * FIXME: fix for error caused due to recent update to mach-
> types.h
> + */
> +#include <asm/mach-types.h>
> +#ifdef MACH_TYPE_SHEEVAD
> +#error "MACH_TYPE_SHEEVAD has been defined properly, please
> remove this."
> +#else
> +#define MACH_TYPE_SHEEVAD 2625
> +#endif
> +
> +/*
> * Version number information
> */
> #define CONFIG_IDENT_STRING "\nMarvell-gplugD"
> @@ -42,7 +52,7 @@
> #define CONFIG_SHEEVA_88SV331xV5 1 /* CPU Core subversion */
> #define CONFIG_ARMADA100 1 /* SOC Family Name */
> #define CONFIG_ARMADA168 1 /* SOC Used on this Board */
> -#define CONFIG_MACH_SHEEVAD /* Machine type */
> +#define CONFIG_MACH_TYPE MACH_TYPE_SHEEVAD /* Machine type
> */
> #define CONFIG_SKIP_LOWLEVEL_INIT /* disable board
> lowlevel_init */
>
> #define CONFIG_SYS_TEXT_BASE 0x00f00000
> --
> 1.7.0.4
Applied to u-boot-marvell.git master branch
Regards..
Prafulla . . .
^ permalink raw reply
* [U-Boot] [PATCH] Reintroduce MACH_TYPE_KM_KIRKWOOD for keymile ARM boards
From: Igor Grinberg @ 2011-10-31 8:20 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1320048407-24701-1-git-send-email-valentin.longchamp@keymile.com>
Hi Valentin,
On 10/31/11 10:06, Valentin Longchamp wrote:
> We got dropped from Linux mach-types.h because of a lack of mainline
> support and this is needed since the last Linux/u-boot mach-types
> synchro.
>
> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
> ---
> include/configs/km/km_arm.h | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/include/configs/km/km_arm.h b/include/configs/km/km_arm.h
> index c117943..eaf6017 100644
> --- a/include/configs/km/km_arm.h
> +++ b/include/configs/km/km_arm.h
> @@ -36,6 +36,9 @@
> #ifndef _CONFIG_KM_ARM_H
> #define _CONFIG_KM_ARM_H
>
> +/* We got removed from Linux mach-types.h */
> +#define MACH_TYPE_KM_KIRKWOOD 2255
While you are at it, probably, it is a good time
to switch to the new standard and use the CONFIG_MACH_TYPE
option. Please, read the README file.
> +
> /*
> * High Level Configuration Options (easy to change)
> */
--
Regards,
Igor.
^ permalink raw reply
* [Buildroot] [Bug 4429] New: buildroot 2011.08 does not build on Ubuntu 11.10
From: bugzilla at busybox.net @ 2011-10-31 8:22 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=4429
Summary: buildroot 2011.08 does not build on Ubuntu 11.10
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: busybox at reliableembeddedsystems.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
/usr/bin/make -j2 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
make[1]: Entering directory `/home/student/beagle/buildroot-2011.08'
mkdir -p
/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/lxdialog
/usr/bin/make CC="/usr/bin/gcc" HOSTCC="/usr/bin/gcc"
obj=/home/student/beagle/buildroot-2011.08/output/build/buildroot-config -C
package/config -f Makefile.br conf
make[2]: Entering directory
`/home/student/beagle/buildroot-2011.08/package/config'
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE
-I/home/student/beagle/buildroot-2011.08/output/build/buildroot-config
/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/conf.o
/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/zconf.tab.o
-o /home/student/beagle/buildroot-2011.08/output/build/buildroot-config/conf
make[2]: Leaving directory
`/home/student/beagle/buildroot-2011.08/package/config'
KCONFIG_AUTOCONFIG=/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/auto.conf
KCONFIG_AUTOHEADER=/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/autoconf.h
KCONFIG_TRISTATE=/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/tristate.config
BUILDROOT_CONFIG=/home/student/beagle/buildroot-2011.08/.config
/home/student/beagle/buildroot-2011.08/output/build/buildroot-config/conf
--silentoldconfig Config.in
#
# make dependencies written to .auto.deps
# ATTENTION buildroot devels!
# See top of this file before playing with this auto-preprequisites!
#
make[1]: Leaving directory `/home/student/beagle/buildroot-2011.08'
>>> host-gmp 5.0.1 Extracting
bzcat /home/student/beagle/buildroot-2011.08/dl/gmp-5.0.1.tar.bz2 | tar
--strip-components=1 -C
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1 -xf -
>>> host-gmp 5.0.1 Patching package/gmp
for file in config.guess config.sub; do for i in $(find
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1 -name
$file); do cp package/gnuconfig/$file $i; done; done
>>> host-gmp 5.0.1 Patching libtool
Applying buildroot-libtool-v2.2.patch using plaintext:
patching file ltmain.sh
>>> host-gmp 5.0.1 Configuring
(cd /home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/ && rm
-rf config.cache;
PATH=/home/student/beagle/buildroot-2011.08/output/host/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/sbin:/usr/sbin:/home/student/beagle/crosstool-ng/development/xtools/bin:/home/student/beagle/crosstool-ng/development/xtools/arm-unknown-linux-gnueabi/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin
AR="/usr/bin/ar" AS="/usr/bin/as" LD="/usr/bin/ld" NM="/usr/bin/nm"
CC="/usr/bin/gcc" GCC="/usr/bin/gcc" CXX="/usr/bin/g++" CPP="/usr/bin/cpp"
CFLAGS="-O2 -I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include"
CXXFLAGS="-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include"
LDFLAGS="-L/home/student/beagle/buildroot-2011.08/output/host/lib
-L/home/student/beagle/buildroot-2011.08/output/host/usr/lib
-Wl,-rpath,/home/student/beagle/buildroot-2011.08/output/host/usr/lib"
PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 PKG_CONFIG_ALLOW_SYSTEM_LIBS=1
PKG_CONFIG="/home/student/beagle/buildroot-2011.08/output/host/usr/bin/pkg-config"
PKG_CONFIG_SYSROOT_DIR="/"
PKG_CONFIG_LIBDIR="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/pkgconfig:/home/student/beagle/buildroot-2011.08/output/host/usr/share/pkgconfig"
PERLLIB="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/perl"
LD_LIBRARY_PATH="/home/student/beagle/buildroot-2011.08/output/host/usr/lib:"
CFLAGS="-O2 -I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include"
LDFLAGS="-L/home/student/beagle/buildroot-2011.08/output/host/lib
-L/home/student/beagle/buildroot-2011.08/output/host/usr/lib
-Wl,-rpath,/home/student/beagle/buildroot-2011.08/output/host/usr/lib"
./configure --prefix="/home/student/beagle/buildroot-2011.08/output/host/usr"
--sysconfdir="/home/student/beagle/buildroot-2011.08/output/host/etc"
--enable-shared --disable-static )
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=32
checking compiler /usr/bin/gcc -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include ... yes
checking compiler /usr/bin/gcc -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include has
sizeof(long)==4... yes
checking for gcc... /usr/bin/gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/gcc accepts -g... yes
checking for /usr/bin/gcc option to accept ISO C89... none needed
checking for /usr/bin/gcc option to accept ISO C99... -std=gnu99
checking for /usr/bin/gcc -std=gnu99 option to accept ISO Standard C...
(cached) -std=gnu99
checking how to run the C preprocessor... /usr/bin/cpp
checking build system compiler /usr/bin/gcc -std=gnu99... yes
checking for build system preprocessor... /usr/bin/gcc -std=gnu99 -E
checking for build system executable suffix...
checking whether build system compiler is ANSI... yes
checking for build system compiler math library... -lm
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
using ABI="32"
CC="/usr/bin/gcc -std=gnu99"
CFLAGS="-O2 -I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include"
CPPFLAGS=""
MPN_PATH=" x86/p6 x86 generic"
checking for function prototypes... yes
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for string.h... (cached) yes
checking whether assembler supports --noexecstack option... yes
checking for ar... /usr/bin/ar
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm
checking the name lister (/usr/bin/nm) interface... BSD nm
checking for a sed that does not truncate output... /bin/sed -i -e
checking for fgrep... /bin/grep -F
checking for ld used by /usr/bin/gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether ln -s works... yes
checking the maximum length of command line arguments... 805306365
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... (cached) /usr/bin/ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm output from /usr/bin/gcc -std=gnu99
object... /bin/sed: no input files
ok
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++ accepts -g... yes
checking how to run the C++ preprocessor... /usr/bin/g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking for objdir... .libs
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: no input files
/bin/sed: no input files
checking if /usr/bin/gcc -std=gnu99 supports -fno-rtti -fno-exceptions...
/bin/sed: -e expression #1, char 1: unknown command: `-'
no
checking for /usr/bin/gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
checking if /usr/bin/gcc -std=gnu99 PIC flag -fPIC -DPIC works... /bin/sed: -e
expression #1, char 1: unknown command: `-'
no
checking if /usr/bin/gcc -std=gnu99 static flag -static works... yes
checking if /usr/bin/gcc -std=gnu99 supports -c -o file.o... /bin/sed: -e
expression #1, char 1: unknown command: `-'
no
checking if /usr/bin/gcc -std=gnu99 supports -c -o file.o... (cached) no
checking if we can lock with hard links... yes
checking whether the /usr/bin/gcc -std=gnu99 linker (/usr/bin/ld) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... /bin/sed: -e expression #1, char 1:
unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
/bin/sed: no input files
/bin/sed: no input files
/bin/sed: -e expression #1, char 1: unknown command: `-'
checking for ld used by /usr/bin/g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the /usr/bin/g++ linker (/usr/bin/ld) supports shared
libraries... yes
/bin/sed: -e expression #1, char 1: unknown command: `-'
checking for /usr/bin/g++ option to produce PIC... -fPIC -DPIC
checking if /usr/bin/g++ PIC flag -fPIC -DPIC works... /bin/sed: -e expression
#1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
yes
checking if /usr/bin/g++ static flag -static works... yes
checking if /usr/bin/g++ supports -c -o file.o... /bin/sed: -e expression #1,
char 1: unknown command: `-'
no
checking if /usr/bin/g++ supports -c -o file.o... (cached) no
checking if we can lock with hard links... yes
checking whether the /usr/bin/g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... /bin/sed: -e expression #1, char 1:
unknown command: `-'
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking invent.h usability... no
checking invent.h presence... no
checking for invent.h... no
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking sys/attributes.h usability... no
checking sys/attributes.h presence... no
checking for sys/attributes.h... no
checking sys/iograph.h usability... no
checking sys/iograph.h presence... no
checking for sys/iograph.h... no
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/processor.h usability... no
checking sys/processor.h presence... no
checking for sys/processor.h... no
checking sys/pstat.h usability... no
checking sys/pstat.h presence... no
checking for sys/pstat.h... no
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking sys/syssgi.h usability... no
checking sys/syssgi.h presence... no
checking for sys/syssgi.h... no
checking sys/systemcfg.h usability... no
checking sys/systemcfg.h presence... no
checking for sys/systemcfg.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for sys/resource.h... yes
checking for sys/sysctl.h... yes
checking for machine/hal_sysinfo.h... no
checking whether fgetc is declared... yes
checking whether fscanf is declared... yes
checking whether optarg is declared... yes
checking whether ungetc is declared... yes
checking whether vfprintf is declared... yes
checking whether sys_errlist is declared... yes
checking whether sys_nerr is declared... yes
checking return type of signal handlers... void
checking for intmax_t... yes
checking for long double... yes
checking for long long... yes
checking for ptrdiff_t... yes
checking for quad_t... yes
checking for uint_least32_t... yes
checking for intptr_t... yes
checking for preprocessor stringizing operator... yes
checking for working volatile... yes
checking for C/C++ restrict keyword... __restrict
checking whether <stdarg.h> exists and works... yes
checking whether gcc __attribute__ ((const)) works... yes
checking whether gcc __attribute__ ((malloc)) works... yes
checking whether gcc __attribute__ ((mode (XX))) works... yes
checking whether gcc __attribute__ ((noreturn)) works... yes
checking for inline... inline
checking for cos in -lm... yes
checking for working alloca.h... yes
checking for alloca (via gmp-impl.h)... yes
checking how to allocate temporary memory... alloca
checking whether byte ordering is bigendian... no
checking format of `double' floating point... IEEE little endian
checking for alarm... yes
checking for attr_get... no
checking for clock... yes
checking for clock_gettime... no
checking for cputime... no
checking for getpagesize... yes
checking for getrusage... yes
checking for gettimeofday... yes
checking for getsysinfo... no
checking for localeconv... yes
checking for memset... yes
checking for mmap... yes
checking for mprotect... yes
checking for nl_langinfo... yes
checking for obstack_vprintf... yes
checking for popen... yes
checking for processor_info... no
checking for pstat_getprocessor... no
checking for raise... yes
checking for read_real_time... no
checking for sigaction... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for syssgi... no
checking for strchr... yes
checking for strerror... yes
checking for strnlen... yes
checking for strtol... yes
checking for strtoul... yes
checking for sysconf... yes
checking for sysctl... yes
checking for sysctlbyname... no
checking for times... yes
checking for vsnprintf... yes
checking whether vsnprintf works... yes
checking whether sscanf needs writable input... no
checking for struct pst_processor.psp_iticksperclktick... no
checking for suitable m4... m4
checking if m4wrap produces spurious output... no
checking how to switch to text section... .text
checking how to switch to data section... .data
checking for assembler label suffix... :
checking for assembler global directive... .globl
checking for assembler global directive attribute...
checking if globals are prefixed by underscore... no
checking how to switch to read-only data section... .section .rodata
checking for assembler .type directive... .type $1,@$2
checking for assembler .size directive... .size $1,$2
checking for assembler local label prefix... .L
checking for assembler byte directive... .byte
checking how to define a 32-bit word... .long
checking if .align assembly directive is logarithmic... no
checking if the .align directive accepts an 0x90 fill in .text... yes
checking for assembler COFF type directives... no
checking if _GLOBAL_OFFSET_TABLE_ is prefixed by underscore... no
checking if the assembler takes cl with shldl... yes
checking size of void *... 4
checking size of unsigned short... 2
checking size of unsigned... 4
checking size of unsigned long... 4
checking size of mp_limb_t... 4
checking for stack_t... yes
checking for tputs in -lncurses... yes
checking for readline in -lreadline... no
checking readline detected... no
checking for bison... bison -y
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for ranlib... (cached) ranlib
creating config.m4
configure: creating ./config.status
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
/bin/sed: -e expression #1, char 1: unknown command: `-'
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
./config.status: line 789: X/usr/bin/gcc: No such file or directory
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
X: user not authorized to run the X server, aborting.
config.status: creating demos/pexpr-config.h
config.status: creating demos/calc/calc-config.h
config.status: creating Makefile
config.status: creating mpbsd/Makefile
config.status: creating mpf/Makefile
config.status: creating mpn/Makefile
config.status: creating mpq/Makefile
config.status: creating mpz/Makefile
config.status: creating printf/Makefile
config.status: creating scanf/Makefile
config.status: creating cxx/Makefile
config.status: creating tests/Makefile
config.status: creating tests/devel/Makefile
config.status: creating tests/mpbsd/Makefile
config.status: creating tests/mpf/Makefile
config.status: creating tests/mpn/Makefile
config.status: creating tests/mpq/Makefile
config.status: creating tests/mpz/Makefile
config.status: creating tests/rand/Makefile
config.status: creating tests/misc/Makefile
config.status: creating tests/cxx/Makefile
config.status: creating doc/Makefile
config.status: creating tune/Makefile
config.status: creating demos/Makefile
config.status: creating demos/calc/Makefile
config.status: creating demos/expr/Makefile
config.status: creating gmp.h
config.status: creating mp.h
config.status: creating config.h
config.status: linking mpn/generic/add.c to mpn/add.c
config.status: linking mpn/generic/add_1.c to mpn/add_1.c
config.status: linking mpn/x86/p6/aors_n.asm to mpn/add_n.asm
config.status: linking mpn/generic/sub.c to mpn/sub.c
config.status: linking mpn/generic/sub_1.c to mpn/sub_1.c
config.status: linking mpn/x86/p6/aors_n.asm to mpn/sub_n.asm
config.status: linking mpn/generic/neg.c to mpn/neg.c
config.status: linking mpn/generic/com.c to mpn/com.c
config.status: linking mpn/x86/mul_1.asm to mpn/mul_1.asm
config.status: linking mpn/x86/p6/aorsmul_1.asm to mpn/addmul_1.asm
config.status: linking mpn/x86/p6/aorsmul_1.asm to mpn/submul_1.asm
config.status: linking mpn/x86/lshift.asm to mpn/lshift.asm
config.status: linking mpn/x86/rshift.asm to mpn/rshift.asm
config.status: linking mpn/x86/p6/dive_1.asm to mpn/dive_1.asm
config.status: linking mpn/generic/diveby3.c to mpn/diveby3.c
config.status: linking mpn/generic/divis.c to mpn/divis.c
config.status: linking mpn/generic/divrem.c to mpn/divrem.c
config.status: linking mpn/x86/divrem_1.asm to mpn/divrem_1.asm
config.status: linking mpn/x86/divrem_2.asm to mpn/divrem_2.asm
config.status: linking mpn/generic/fib2_ui.c to mpn/fib2_ui.c
config.status: linking mpn/generic/mod_1.c to mpn/mod_1.c
config.status: linking mpn/x86/p6/mod_34lsub1.asm to mpn/mod_34lsub1.asm
config.status: linking mpn/x86/p6/mode1o.asm to mpn/mode1o.asm
config.status: linking mpn/generic/pre_divrem_1.c to mpn/pre_divrem_1.c
config.status: linking mpn/generic/pre_mod_1.c to mpn/pre_mod_1.c
config.status: linking mpn/generic/dump.c to mpn/dump.c
config.status: linking mpn/generic/mod_1_1.c to mpn/mod_1_1.c
config.status: linking mpn/generic/mod_1_2.c to mpn/mod_1_2.c
config.status: linking mpn/generic/mod_1_3.c to mpn/mod_1_3.c
config.status: linking mpn/generic/mod_1_4.c to mpn/mod_1_4.c
config.status: linking mpn/generic/lshiftc.c to mpn/lshiftc.c
config.status: linking mpn/generic/mul.c to mpn/mul.c
config.status: linking mpn/generic/mul_fft.c to mpn/mul_fft.c
config.status: linking mpn/generic/mul_n.c to mpn/mul_n.c
config.status: linking mpn/generic/sqr.c to mpn/sqr.c
config.status: linking mpn/x86/p6/mul_basecase.asm to mpn/mul_basecase.asm
config.status: linking mpn/x86/p6/sqr_basecase.asm to mpn/sqr_basecase.asm
config.status: linking mpn/generic/nussbaumer_mul.c to mpn/nussbaumer_mul.c
config.status: linking mpn/generic/random.c to mpn/random.c
config.status: linking mpn/generic/random2.c to mpn/random2.c
config.status: linking mpn/generic/pow_1.c to mpn/pow_1.c
config.status: linking mpn/generic/rootrem.c to mpn/rootrem.c
config.status: linking mpn/generic/sqrtrem.c to mpn/sqrtrem.c
config.status: linking mpn/generic/get_str.c to mpn/get_str.c
config.status: linking mpn/generic/set_str.c to mpn/set_str.c
config.status: linking mpn/generic/scan0.c to mpn/scan0.c
config.status: linking mpn/generic/scan1.c to mpn/scan1.c
config.status: linking mpn/generic/popham.c to mpn/popcount.c
config.status: linking mpn/generic/popham.c to mpn/hamdist.c
config.status: linking mpn/generic/cmp.c to mpn/cmp.c
config.status: linking mpn/generic/perfsqr.c to mpn/perfsqr.c
config.status: linking mpn/generic/perfpow.c to mpn/perfpow.c
config.status: linking mpn/generic/gcd_1.c to mpn/gcd_1.c
config.status: linking mpn/generic/gcd.c to mpn/gcd.c
config.status: linking mpn/generic/gcdext_1.c to mpn/gcdext_1.c
config.status: linking mpn/generic/gcdext.c to mpn/gcdext.c
config.status: linking mpn/generic/gcd_lehmer.c to mpn/gcd_lehmer.c
config.status: linking mpn/generic/gcd_subdiv_step.c to mpn/gcd_subdiv_step.c
config.status: linking mpn/generic/gcdext_lehmer.c to mpn/gcdext_lehmer.c
config.status: linking mpn/generic/gcdext_subdiv_step.c to
mpn/gcdext_subdiv_step.c
config.status: linking mpn/generic/div_q.c to mpn/div_q.c
config.status: linking mpn/generic/tdiv_qr.c to mpn/tdiv_qr.c
config.status: linking mpn/generic/jacbase.c to mpn/jacbase.c
config.status: linking mpn/generic/get_d.c to mpn/get_d.c
config.status: linking mpn/generic/matrix22_mul.c to mpn/matrix22_mul.c
config.status: linking mpn/generic/hgcd2.c to mpn/hgcd2.c
config.status: linking mpn/generic/hgcd.c to mpn/hgcd.c
config.status: linking mpn/generic/mullo_n.c to mpn/mullo_n.c
config.status: linking mpn/generic/mullo_basecase.c to mpn/mullo_basecase.c
config.status: linking mpn/generic/toom22_mul.c to mpn/toom22_mul.c
config.status: linking mpn/generic/toom32_mul.c to mpn/toom32_mul.c
config.status: linking mpn/generic/toom42_mul.c to mpn/toom42_mul.c
config.status: linking mpn/generic/toom52_mul.c to mpn/toom52_mul.c
config.status: linking mpn/generic/toom62_mul.c to mpn/toom62_mul.c
config.status: linking mpn/generic/toom33_mul.c to mpn/toom33_mul.c
config.status: linking mpn/generic/toom43_mul.c to mpn/toom43_mul.c
config.status: linking mpn/generic/toom53_mul.c to mpn/toom53_mul.c
config.status: linking mpn/generic/toom63_mul.c to mpn/toom63_mul.c
config.status: linking mpn/generic/toom44_mul.c to mpn/toom44_mul.c
config.status: linking mpn/generic/toom6h_mul.c to mpn/toom6h_mul.c
config.status: linking mpn/generic/toom6_sqr.c to mpn/toom6_sqr.c
config.status: linking mpn/generic/toom8h_mul.c to mpn/toom8h_mul.c
config.status: linking mpn/generic/toom8_sqr.c to mpn/toom8_sqr.c
config.status: linking mpn/generic/toom_couple_handling.c to
mpn/toom_couple_handling.c
config.status: linking mpn/generic/toom2_sqr.c to mpn/toom2_sqr.c
config.status: linking mpn/generic/toom3_sqr.c to mpn/toom3_sqr.c
config.status: linking mpn/generic/toom4_sqr.c to mpn/toom4_sqr.c
config.status: linking mpn/generic/toom_eval_dgr3_pm1.c to
mpn/toom_eval_dgr3_pm1.c
config.status: linking mpn/generic/toom_eval_dgr3_pm2.c to
mpn/toom_eval_dgr3_pm2.c
config.status: linking mpn/generic/toom_eval_pm1.c to mpn/toom_eval_pm1.c
config.status: linking mpn/generic/toom_eval_pm2.c to mpn/toom_eval_pm2.c
config.status: linking mpn/generic/toom_eval_pm2exp.c to mpn/toom_eval_pm2exp.c
config.status: linking mpn/generic/toom_eval_pm2rexp.c to
mpn/toom_eval_pm2rexp.c
config.status: linking mpn/generic/toom_interpolate_5pts.c to
mpn/toom_interpolate_5pts.c
config.status: linking mpn/generic/toom_interpolate_6pts.c to
mpn/toom_interpolate_6pts.c
config.status: linking mpn/generic/toom_interpolate_7pts.c to
mpn/toom_interpolate_7pts.c
config.status: linking mpn/generic/toom_interpolate_8pts.c to
mpn/toom_interpolate_8pts.c
config.status: linking mpn/generic/toom_interpolate_12pts.c to
mpn/toom_interpolate_12pts.c
config.status: linking mpn/generic/toom_interpolate_16pts.c to
mpn/toom_interpolate_16pts.c
config.status: linking mpn/generic/invertappr.c to mpn/invertappr.c
config.status: linking mpn/generic/invert.c to mpn/invert.c
config.status: linking mpn/generic/binvert.c to mpn/binvert.c
config.status: linking mpn/generic/mulmod_bnm1.c to mpn/mulmod_bnm1.c
config.status: linking mpn/generic/sqrmod_bnm1.c to mpn/sqrmod_bnm1.c
config.status: linking mpn/generic/sbpi1_div_q.c to mpn/sbpi1_div_q.c
config.status: linking mpn/generic/sbpi1_div_qr.c to mpn/sbpi1_div_qr.c
config.status: linking mpn/generic/sbpi1_divappr_q.c to mpn/sbpi1_divappr_q.c
config.status: linking mpn/generic/dcpi1_div_q.c to mpn/dcpi1_div_q.c
config.status: linking mpn/generic/dcpi1_div_qr.c to mpn/dcpi1_div_qr.c
config.status: linking mpn/generic/dcpi1_divappr_q.c to mpn/dcpi1_divappr_q.c
config.status: linking mpn/generic/mu_div_qr.c to mpn/mu_div_qr.c
config.status: linking mpn/generic/mu_divappr_q.c to mpn/mu_divappr_q.c
config.status: linking mpn/generic/mu_div_q.c to mpn/mu_div_q.c
config.status: linking mpn/generic/bdiv_q_1.c to mpn/bdiv_q_1.c
config.status: linking mpn/generic/sbpi1_bdiv_q.c to mpn/sbpi1_bdiv_q.c
config.status: linking mpn/generic/sbpi1_bdiv_qr.c to mpn/sbpi1_bdiv_qr.c
config.status: linking mpn/generic/dcpi1_bdiv_q.c to mpn/dcpi1_bdiv_q.c
config.status: linking mpn/generic/dcpi1_bdiv_qr.c to mpn/dcpi1_bdiv_qr.c
config.status: linking mpn/generic/mu_bdiv_q.c to mpn/mu_bdiv_q.c
config.status: linking mpn/generic/mu_bdiv_qr.c to mpn/mu_bdiv_qr.c
config.status: linking mpn/generic/bdiv_q.c to mpn/bdiv_q.c
config.status: linking mpn/generic/bdiv_qr.c to mpn/bdiv_qr.c
config.status: linking mpn/generic/divexact.c to mpn/divexact.c
config.status: linking mpn/x86/bdiv_dbm1c.asm to mpn/bdiv_dbm1c.asm
config.status: linking mpn/generic/redc_1.c to mpn/redc_1.c
config.status: linking mpn/generic/redc_2.c to mpn/redc_2.c
config.status: linking mpn/generic/redc_n.c to mpn/redc_n.c
config.status: linking mpn/generic/powm.c to mpn/powm.c
config.status: linking mpn/generic/powlo.c to mpn/powlo.c
config.status: linking mpn/generic/powm_sec.c to mpn/powm_sec.c
config.status: linking mpn/generic/subcnd_n.c to mpn/subcnd_n.c
config.status: linking mpn/generic/redc_1_sec.c to mpn/redc_1_sec.c
config.status: linking mpn/generic/trialdiv.c to mpn/trialdiv.c
config.status: linking mpn/generic/remove.c to mpn/remove.c
config.status: linking mpn/generic/logops_n.c to mpn/and_n.c
config.status: linking mpn/generic/logops_n.c to mpn/andn_n.c
config.status: linking mpn/generic/logops_n.c to mpn/nand_n.c
config.status: linking mpn/generic/logops_n.c to mpn/ior_n.c
config.status: linking mpn/generic/logops_n.c to mpn/iorn_n.c
config.status: linking mpn/generic/logops_n.c to mpn/nior_n.c
config.status: linking mpn/generic/logops_n.c to mpn/xor_n.c
config.status: linking mpn/generic/logops_n.c to mpn/xnor_n.c
config.status: linking mpn/x86/copyi.asm to mpn/copyi.asm
config.status: linking mpn/x86/p6/copyd.asm to mpn/copyd.asm
config.status: linking mpn/generic/zero.c to mpn/zero.c
config.status: linking mpn/x86/umul.asm to mpn/umul.asm
config.status: linking mpn/x86/udiv.asm to mpn/udiv.asm
config.status: linking mpn/x86/invert_limb.asm to mpn/invert_limb.asm
config.status: linking mpn/x86/p6/gmp-mparam.h to gmp-mparam.h
config.status: executing libtool commands
libtool: you must specify a MODE
libtool: Try `libtool --help' for more information.
>>> host-gmp 5.0.1 Building
PATH=/home/student/beagle/buildroot-2011.08/output/host/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/sbin:/usr/sbin:/home/student/beagle/crosstool-ng/development/xtools/bin:/home/student/beagle/crosstool-ng/development/xtools/arm-unknown-linux-gnueabi/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin
LD_LIBRARY_PATH="/home/student/beagle/buildroot-2011.08/output/host/usr/lib:"
PKG_CONFIG=""
PKG_CONFIG_LIBDIR="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/pkgconfig"
PERLLIB="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/perl"
/usr/bin/make -j2 -C
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/
make[1]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
/usr/bin/gcc -std=gnu99 `test -f 'gen-fac_ui.c' || echo './'`gen-fac_ui.c -o
gen-fac_ui
/usr/bin/gcc -std=gnu99 `test -f 'gen-fib.c' || echo './'`gen-fib.c -o gen-fib
/usr/bin/gcc -std=gnu99 `test -f 'gen-bases.c' || echo './'`gen-bases.c -o
gen-bases -lm
/usr/bin/gcc -std=gnu99 `test -f 'gen-trialdivtab.c' || echo
'./'`gen-trialdivtab.c -o gen-trialdivtab -lm
/usr/bin/gcc -std=gnu99 `test -f 'gen-psqr.c' || echo './'`gen-psqr.c -o
gen-psqr -lm
./gen-fac_ui 32 0 >mpz/fac_ui.h || (rm -f mpz/fac_ui.h; exit 1)
./gen-fib header 32 0 >fib_table.h || (rm -f fib_table.h; exit 1)
./gen-fib table 32 0 >mpn/fib_table.c || (rm -f mpn/fib_table.c; exit 1)
./gen-bases header 32 0 >mp_bases.h || (rm -f mp_bases.h; exit 1)
./gen-bases table 32 0 >mpn/mp_bases.c || (rm -f mpn/mp_bases.c; exit 1)
./gen-trialdivtab 32 8000 >trialdivtab.h || (rm -f trialdivtab.h; exit 1)
./gen-psqr 32 0 >mpn/perfsqr.h || (rm -f mpn/perfsqr.h; exit 1)
/usr/bin/make all-recursive
make[2]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
Making all in tests
make[3]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in .
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in devel
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/devel'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/devel'
Making all in mpn
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpn'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpn'
Making all in mpz
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpz'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpz'
Making all in mpq
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpq'
Making all in mpf
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpf'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpf'
Making all in rand
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/rand'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/rand'
Making all in misc
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/misc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/misc'
Making all in cxx
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/cxx'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/cxx'
Making all in mpbsd
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpbsd'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpbsd'
make[3]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in mpn
make[3]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/mpn'
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc -std=gnu99
-DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo fib_table |
sed 's/_$//'` -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include -c -o
fib_table.lo fib_table.c
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc -std=gnu99
-DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo mp_bases |
sed 's/_$//'` -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include -c -o
mp_bases.lo mp_bases.c
../libtool: line 519: CDPATH: command not found
../libtool: line 519: CDPATH: command not found
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/libtool:
line 519: CDPATH: command not found
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/libtool:
line 519: CDPATH: command not found
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[3]: *** [fib_table.lo] Error 63
make[3]: *** Waiting for unfinished jobs....
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[3]: *** [mp_bases.lo] Error 63
make[3]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/mpn'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
make: ***
[/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/.stamp_built]
Error 2
>>> host-gmp 5.0.1 Building
PATH=/home/student/beagle/buildroot-2011.08/output/host/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/sbin:/usr/sbin:/home/student/beagle/crosstool-ng/development/xtools/bin:/home/student/beagle/crosstool-ng/development/xtools/arm-unknown-linux-gnueabi/bin:/home/student/beagle/buildroot-2011.08/output/host/usr/bin
LD_LIBRARY_PATH="/home/student/beagle/buildroot-2011.08/output/host/usr/lib:"
PKG_CONFIG=""
PKG_CONFIG_LIBDIR="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/pkgconfig"
PERLLIB="/home/student/beagle/buildroot-2011.08/output/host/usr/lib/perl"
/usr/bin/make -j2 -C
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/
make[1]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
/usr/bin/make all-recursive
make[2]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
Making all in tests
make[3]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in .
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in devel
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/devel'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/devel'
Making all in mpn
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpn'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpn'
Making all in mpz
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpz'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpz'
Making all in mpq
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpq'
Making all in mpf
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpf'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpf'
Making all in rand
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/rand'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/rand'
Making all in misc
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/misc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/misc'
Making all in cxx
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/cxx'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/cxx'
Making all in mpbsd
make[4]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpbsd'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests/mpbsd'
make[3]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/tests'
Making all in mpn
make[3]: Entering directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/mpn'
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc -std=gnu99
-DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo fib_table |
sed 's/_$//'` -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include -c -o
fib_table.lo fib_table.c
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc -std=gnu99
-DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo mp_bases |
sed 's/_$//'` -O2
-I/home/student/beagle/buildroot-2011.08/output/host/include
-I/home/student/beagle/buildroot-2011.08/output/host/usr/include -c -o
mp_bases.lo mp_bases.c
../libtool: line 519: CDPATH: command not found
../libtool: line 519: CDPATH: command not found
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/libtool:
line 519: CDPATH: command not found
/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/libtool:
line 519: CDPATH: command not found
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[3]: *** [fib_table.lo] Error 63
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [mp_bases.lo] Error 63
make[3]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/mpn'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1'
make: ***
[/home/student/beagle/buildroot-2011.08/output/build/host-gmp-5.0.1/.stamp_built]
Error 2
student at ThinkPad-X60s-2:~/projects/lf411/LF411_for_trainer/11$
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
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.