search for: hostcflags

The attached patch adds -Werror to HOSTCFLAGS in Config.mk, makes xen/tools actually use HOSTCFLAGS (it was already using HOSTCC), and fixes some gcc-4.0 signedness warnings in xen/tools/symbols.c. Signed-off-by: Josh Triplett <josht@us.ibm.com> - Josh Triplett _______________________________________________ Xen-devel mailing list X...

Hi. HOSTCC should be used to set HOSTCFLAGS instead of CC. There is a case where HOSTCC doesn''t accept -Wdeclaration-after-statement, while CC does. It results in a compilation error. This patch fixes it Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> -- diff -r 94cb428d363d -r 164e8408c67a Config.mk --- a/Config.mk...

..., Anatoly Pugachev said: >> Hello! >> >> Can someone please help me in building debug version of klibc ? >> >> I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but >> failed to build it with debug info >> >> added "-g" to HOSTCFLAGS in Makefile, but > > Hint: HOSTCFLAGS is applied to code that needs to run on the machine that's > doing the build, not the target code. So for instance, if I'm cross-compiling on > an x86_64 for an ARM target (which I do quite a bit, building Lede router images > for...

Hello! Can someone please help me in building debug version of klibc ? I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but failed to build it with debug info added "-g" to HOSTCFLAGS in Makefile, but $ make -j KLIBCKERNELSRC=`pwd`/../linux-2.6/usr still strips every debug symbol , and i'm failed to change scripts/Kbuild.klibc and Makefile to remove strip usage klibc$ find . -name fstype | xargs file ./usr/kinit/fstype: directory ./usr/kinit/fstype/static/fs...

...Sat, 30 Dec 2017 13:54:05 +0300, Anatoly Pugachev said: > Hello! > > Can someone please help me in building debug version of klibc ? > > I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but > failed to build it with debug info > > added "-g" to HOSTCFLAGS in Makefile, but Hint: HOSTCFLAGS is applied to code that needs to run on the machine that's doing the build, not the target code. So for instance, if I'm cross-compiling on an x86_64 for an ARM target (which I do quite a bit, building Lede router images for my wireless), HOSTCFLAGS is...

...30, 2017 at 01:54:05PM +0300, Anatoly Pugachev wrote: > Hello! > > Can someone please help me in building debug version of klibc ? > > I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but > failed to build it with debug info > > added "-g" to HOSTCFLAGS in Makefile, but HOSTCFLAGS is used when building tools running on your build machine. Try something like this (untested, whitespace damaged): diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index f500d535..3e8124f7 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -69,7 +...

...ello! > >> > >> Can someone please help me in building debug version of klibc ? > >> > >> I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but > >> failed to build it with debug info > >> > >> added "-g" to HOSTCFLAGS in Makefile, but > it's usual git kernel compile and install. And it's the first time I > started to get segfault from fstype. I missed where you went from klibc to building a new kernel, probably because you changed topics in mid-email. Why were you building a new kernel for your...

...> >> Can someone please help me in building debug version of klibc ? >> >> >> >> I've cloned git://git.kernel.org/pub/scm/libs/klibc/klibc.git , but >> >> failed to build it with debug info >> >> >> >> added "-g" to HOSTCFLAGS in Makefile, but > >> it's usual git kernel compile and install. And it's the first time I >> started to get segfault from fstype. > > I missed where you went from klibc to building a new kernel, probably > because you changed topics in mid-email. Why were you build...

...rint-file-name=include) -export ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) +export ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/parisc64/parisc/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) export HOSTCC := gcc export HOSTCFLAGS := -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer

...nutils for consistency, > added the missing ones too for klcc. > > > diff --git a/Makefile b/Makefile > index bfae8de..640eec4 100644 > --- a/Makefile > +++ b/Makefile > @@ -19,6 +19,11 @@ export ARCH := $(shell uname -m | sed -e > export HOSTCC := gcc > export HOSTCFLAGS := -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer > export PERL := perl > +export LD := ld > +export AR := ar > +export RANLIB := ranlib > +export STRIP := strip > +export NM := nm This will clash with the namespace used by the kernel. A...

Hi there, I''ve just built xen & dom0 kernel from gentoo ebuilds (bugs.gentoo.org), but my dom0 kernel crashes during boot. Any help is appreciated. Console log, grub.conf and .config are included, machine is celeron/466, 128MB of RAM. Console log: Linux version 2.6.9-xen0 (root@zirafa) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #2 Sun Nov 14

...h: %.h: %.asl iasl > iasl -vs -p $* -tc $< > - sed -e ''s/AmlCode/$*/g'' $*.hex >$@ > + sed -e ''s/AmlCode/$*/g'' $*.hex > $@.tmp > + $(call move-if-changed,$@.tmp $@) > rm -f $*.hex $*.aml > > mk_dsdt: mk_dsdt.c > $(HOSTCC) $(HOSTCFLAGS) $(CFLAGS_xeninclude) -o $@ mk_dsdt.c > > dsdt_anycpu_qemu_xen.asl: dsdt.asl mk_dsdt > - awk ''NR > 1 {print s} {s=$$0}'' $< > $@ > - ./mk_dsdt --dm-version qemu-xen >> $@ > + awk ''NR > 1 {print s} {s=$$0}'' $< > $@.tmp >...

...= -nostdlib -nostdinc -i ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/parisc64/parisc/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) export KLIBCARCH ?= $(ARCH) +export KLIBCARCHDIR := $(shell echo $(KLIBCARCH) | sed -e s/s390x/s390/) export HOSTCC := gcc export HOSTCFLAGS := -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer diff -purN a/scripts/Kbuild.install b/scripts/Kbuild.install --- a/scripts/Kbuild.install 2006-05-11 08:09:08.000000000 +0200 +++ b/scripts/Kbuild.install 2006-05-11 08:10:07.000000000 +0200 @@ -95,7 +95,7 @@ header: $(Q)mkdir -p $(INSTALLROOT...

...+0200 @@ -180,6 +180,7 @@ UTS_MACHINE := $(ARCH) # Architecture used to compile user-space code KLIBCARCH ?= $(ARCH) +KLIBCARCHDIR ?= $(ARCH) # klibc definitions export KLIBCINC := usr/include @@ -326,7 +327,7 @@ export VERSION PATCHLEVEL SUBLEVEL KERNE export KLIBCARCH CONFIG_SHELL HOSTCC HOSTCFLAGS CROSS_COMPILE AS LD export CC CPP AR RANLIB NM STRIP OBJCOPY OBJDUMP MAKE AWK GENKSYMS export PERL UTS_MACHINE HOSTCXX HOSTCXXFLAGS LDFLAGS_MODULE CHECK -export CHECKFLAGS +export CHECKFLAGS KLIBCARCHDIR export CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS LDFLAGS export CFLAGS CFLAGS_KER...

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at:

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *