From: "Dave Humphreys (Bob)" <dave@bob-the-boat.me.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] linux-3.6.x ARCH=um will not build
Date: Sat, 13 Oct 2012 13:13:02 +0000 [thread overview]
Message-ID: <14846952.alsA7bkick@vault01> (raw)
Apologies if this repeats any previous attempts made by me: problems with
something called 'gmane'
===
...
CC arch/um/os-Linux/signal.o
arch/um/os-Linux/signal.c:18:8: error: conflicting types for 'sig_info'
/nfs4xp/software/krn/linux-3.6.x/linux-3.6.2-um64/arch/um/include/shared/as-
layout.h:64:15: note: previous declaration of 'sig_info' was here
I get the above error when trying to build both linux-3.6 and linux-3.6.2 in
both x86 (gcc-4.7.2) and x86_64 (gcc-4.6.3) environments.
Since both files involved in the conflict are part of the source distribution,
I don't think that it can be a fault with my environment; but then I don't
understand why it obviously works for others.
arch/um/os-Linux/signal.c:18:8
arch/um/include/shared/as-layout.h:64:15
Regards,
David
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2012-10-13 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 13:13 Dave Humphreys (Bob) [this message]
2012-10-13 13:27 ` [uml-devel] linux-3.6.x ARCH=um will not build Richard Weinberger
2012-10-13 13:53 ` Geert Uytterhoeven
2012-10-20 20:33 ` Lekensteyn
2012-10-20 20:55 ` Richard Weinberger
2012-10-20 22:07 ` Lekensteyn
2012-10-20 22:18 ` richard -rw- weinberger
2012-10-20 22:41 ` Lekensteyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14846952.alsA7bkick@vault01 \
--to=dave@bob-the-boat.me.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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.