Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: kernel menuconfig broken?
Date: Mon, 2 Apr 2018 17:57:05 -0400	[thread overview]
Message-ID: <20180402215705.GA25121@linux-uys3> (raw)
In-Reply-To: <CALbNGRTAbsa9CzzXqtq7mpiknFzUB_=9eHcFHnD5W--HEM8bPw@mail.gmail.com>

On Sun 2018-04-01 @ 11:49:58 PM, Andreas Müller wrote:
> When running bitbake -cmenuconfig virtual/kernel I get a flood of
> undefined reference errors. Am I alone here?

Sadly, I think you might be.

	$ bitbake virtual/kernel -c menuconfig

works fine for me.

I assume you're doing this for something RaspberryPi-ish?

	Build Configuration:
	BB_VERSION           = "1.37.0"
	BUILD_SYS            = "x86_64-linux"
	NATIVELSBSTRING      = "opensuse-42.3"
	TARGET_SYS           = "arm-oe-linux-gnueabi"
	MACHINE              = "raspberrypi3"
	DISTRO               = "nodistro"
	DISTRO_VERSION       = "nodistro.0"
	TUNE_FEATURES        = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
	TARGET_FPU           = "hard"
	meta-raspberrypi     = "master:63e53f919089027259a513dc2cd4b140789bf1a3"
	meta                 = "master:4cedddb83623c79980b354642dfeaf78218ca4b7"
	meta-oe              
	meta-gnome           
	meta-python          
	meta-networking      
	meta-multimedia      = "master:b9d1d8718834f7287e5a65373b952cbfe9ce83fe"
	meta-qt5             = "master:e60e849de1158c879bd2c150fe79b207cdac031a"
	meta-qt5-extra       = "master:a0cf057b2f335e8d2be9180f20770773334ec209"
	meta-realtime        = "master:250bc6eaa47e550c1db5e2b0ebd42d86ee43650e"
	meta-browser         = "master:d1c902440cba26a9d1271cfb914633c68ee3791c"


  reply	other threads:[~2018-04-02 21:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-01 21:49 kernel menuconfig broken? Andreas Müller
2018-04-02 21:57 ` Trevor Woerner [this message]
2018-04-12 20:28   ` Andreas Müller
2018-04-12 21:19     ` Cal Sullivan
2018-04-12 21:29       ` Andreas Müller
2018-04-12 21:38     ` Cal Sullivan
2018-04-12 21:46       ` Andreas Müller
2018-04-12 22:12         ` Andreas Müller
2018-04-14  9:10           ` Paul Barker
2018-04-14 12:55             ` Andreas Müller
2018-04-14 18:42               ` Trevor Woerner
2018-04-14 19:06                 ` Andreas Müller
2018-09-21 10:04           ` Andreas Müller
2018-09-21 11:46             ` Anuj Mittal
2018-09-21 12:31               ` Bruce Ashfield
2018-09-21 14:39               ` Andreas Müller
2018-09-21 15:33                 ` Andreas Müller
2018-09-21 15:34                   ` Bruce Ashfield
2018-09-21 15:57                     ` Bruce Ashfield
2018-04-13 19:54       ` Bruce Ashfield

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=20180402215705.GA25121@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=schnitzeltony@gmail.com \
    /path/to/YOUR_REPLY

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

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