All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: tools/makefile: Add build target
Date: Wed, 8 Aug 2012 10:45:17 +0100	[thread overview]
Message-ID: <5022352D.7080607@citrix.com> (raw)
In-Reply-To: <20513.24085.195729.702722@mariner.uk.xensource.com>

On 07/08/12 19:27, Ian Jackson wrote:
> Andrew Cooper writes ("[Xen-devel] tools/makefile: Add build target"):
>> The alternative is to change the root makefile to call "$(MAKE) -C
>> tools/ all" instead, but this way feels neater to me.
> Yes.
>
>> tools/makefile: Add build target
>>
>> The root Makefile has a build target which calls "$(MAKE) build" in each of xen/
>> tools/ stubdom/ and docs/, which fails because of the tools/ Makefile.
> That this didn't work is clearly a bug.
>
> But when I tried it my build did this:
>
>   CC    i386-stubdom/eeprom93xx.o
> /u/iwj/work/xen-unstable-tools.hg/stubdom/mini-os-x86_32-c/test.o: In function `app_main':
> /u/iwj/work/xen-unstable-tools.hg/extras/mini-os/test.c:441: multiple definition of `app_main'
> /u/iwj/work/xen-unstable-tools.hg/stubdom/mini-os-x86_32-c/main.o:/u/iwj/work/xen-unstable-tools.hg/extras/mini-os/main.c:187: first defined here
>   CC    i386-stubdom/eepro100.o
> make[2]: *** [/u/iwj/work/xen-unstable-tools.hg/stubdom/mini-os-x86_32-c/mini-os] Error 1
> make[2]: Leaving directory `/u/iwj/work/xen-unstable-tools.hg/extras/mini-os'
> make[1]: *** [c-stubdom] Error 2
> make[1]: *** Waiting for unfinished jobs....
>
> That's the result of:
>
>  (make -j4 build && echo ok.) 2>&1 | tee ../log
>
> Ian.

The issue there is that app_main() is defined as __attribute__((weak)),
and has two definitions in the code.

I have just tested and confirmed that minios (and therefore stubdom) is
not -j safe.  As a result, I would argue that this build failure is not
nesseserally a barrier of entry to the patch itself;  There are more
issues which need fixing as well.

stubdom itself has further build issues regarding relative paths to
configure scripts, which I was going to around to fixing after some of
my more important tasks.

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-08-08  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 18:22 tools/makefile: Add build target Andrew Cooper
2012-08-07 18:27 ` Ian Jackson
2012-08-08  9:45   ` Andrew Cooper [this message]
2012-08-09 16:59     ` Ian Jackson

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=5022352D.7080607@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.