I'm new to Linux and this Forum, but not new to computers. That said I have a lot to learn.

I'm running PCLinuxOS. On an HP p7-1254. The computer has a Pegatron 2ACF Ver 1.03 motherboard, a quad core AMD A6-3620 cpu (Which is a 64 bit processor executing the X86-64 instruction set) and 8GB of memory.

I downloaded the latest Linux Kernel source (4.1.0) and followed the cookbook for generating a new kernel. The generation worked and I'm able to run with the kernel. However, when I checked the config file I found that the kernel was for a 32 bit machine. I then checked all previous kernels as generated by Synaptic and they were also 32 bit kernels. I then went back and in a new directory untared the distro and ran menuconfig. The only item I changed was the first one which was to generate a 64 Bit Kernel. I then tried to make the kernel and got the following:

---------------------------------------------------------------------

[root@localhost linux-4.1]# make && make modules_install && install
HOSTCC scripts/kconfig/conf.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
#
# configuration written to .config
#
arch/x86/Makefile:114: stack-protector enabled but compiler support broken
Makefile:664: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_32_ia32.h
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_64_x32.h
SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_64.h
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
HOSTCC arch/x86/tools/relocs_32.o
HOSTCC arch/x86/tools/relocs_64.o
HOSTCC arch/x86/tools/relocs_common.o
HOSTLD arch/x86/tools/relocs
CHK include/config/kernel.release
UPD include/config/kernel.release
WRAP arch/x86/include/generated/asm/clkdev.h
WRAP arch/x86/include/generated/asm/cputime.h
WRAP arch/x86/include/generated/asm/dma-contiguous.h
WRAP arch/x86/include/generated/asm/early_ioremap.h
WRAP arch/x86/include/generated/asm/mcs_spinlock.h
WRAP arch/x86/include/generated/asm/scatterlist.h
CHK include/generated/uapi/linux/version.h
UPD include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
CC kernel/bounds.s
kernel/bounds.c:1:0: error: code model ‘kernel’ not supported in the 32 bit mode
/*
^
kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in
Kbuild:43: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 1
Makefile:989: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2

--------------------------------------------------------------------

Why is this happening and can anyone help?

Thanks

Jay

Just for my info, which output do you get when running...
?
(p.s.: and "file /usr/bin/gcc"?)

Simple google found this as first hit. Seems to cover your query.
But things are always changing - if you still have problems after that, run this and post the result

In response to Pearlseattle:

-----------------------------------------------------------------

[root@localhost ~]# file /bin/bash
/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=d15a53e08f627374f47136eaae758d0f8a89a9b4, stripped
[root@localhost ~]# file /usr/bin/gcc
/usr/bin/gcc: symbolic link to `/etc/alternatives/gcc'

------------------------------------------------------------------

In response to syg00:

The link you provided was the first thing I tried. It failed in a manner much like the failure described.

The system seems to add boot locations to grub. So backup of the kernel isn't a problem. I'll just boot an old working kernel.

Response to the command provided for the 32 bit config file that worked:

-------------------------------------------------------------------------------

[root@localhost boot]# grep "64" config-4.1.0 | grep -vE "(=m|^#)"
CONFIG_X86_CMPXCHG64=y
CONFIG_NR_CPUS=64
CONFIG_HIGHMEM64G=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_X86_RESERVE_LOW=64
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_AGP_AMD64=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_CFAG12864B_RATE=20
CONFIG_XZ_DEC_IA64=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y

-----------------------------------------------------------------------------------------------

This is the output from the 64 bit config file that produced the output provided in the first message.

-----------------------------------------------------------------------------------------------

[root@localhost linux-4.1]# grep "64" .config | grep -vE "(=m|^#)"
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_X86_64_SMP=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_NR_CPUS=64
CONFIG_X86_ESPFIX64=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_X86_RESERVE_LOW=64
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_AGP_AMD64=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_CFAG12864B_RATE=20
CONFIG_XZ_DEC_IA64=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y

--------------------------------------------------------------------------------------------

Thanks for any help.

The config looks sane.
You will need a 64-bit toolchain - I'm guessing the gcc is 32-bit also. Try this instead

syg00:

The files are different, although the last half dozen or so entries are the same.

That said the answer to the gcc question is:

-----------------------------------------------------------------------------------------

[cooperjay@localhost ~]$ file $(which gcc)
/usr/bin/gcc: symbolic link to `/etc/alternatives/gcc'

-----------------------------------------------------------------------------------------

so try: file $(readlink /etc/alternatives/gcc)

You are currently running a 32-bit Linux, which means you can only use a 32-bit gcc.

There are 32-bit builds of gcc that can be used to compile for 64-bit. But I don't know how you would obtain/install such in PCLinuxOS. (That doesn't mean it is difficult, just that I don't know PCLinuxOS).

I suspect you would be better off starting over with a 64-bit install of Linux before (or instead of) trying to compile your own kernel. That does not mean that is your only choice, just that compiling a 64-bit kernel on a 32-bit Linux is unusual enough that you will find few people here able to guide you through the details.

1 members found this post helpful.

pan64 as per your request:

--------------------------------------------------------------------------------------

[cooperjay@localhost ~]$ file $(readlink /etc/alternatives/gcc)
/usr/bin/gcc-4.9.2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=996f67273da0baf8c22bd909f7c67bc0fa61424f, stripped

-----------------------------------------------------------------------------------------

johnsfile:

You mention starting with a 64 bit install of linux. I'm new to the community, but would have thought that the kernels needed to be built to the specific target machines, that's why I tried to compile my own kernel. Better yet do you know where I can obtain a 64 bit install of Linux?

Thanks

No. There is virtually zero difference between x64 CPUs and the default kernel compile (even if you compile yourself on your target machine) is for the common features of all x64 CPUs.

Most Linux distributions have either only 64bit or both 32bit and 64bit.

Just pay attention to the details listed on the download page of whatever distribution you choose.

You can create a cross-toolchain from source yourself. First create a cross-binutils targeting x86_64 and then a cross-gcc for x86-64 using the cross-binutils.

Do a websearch for more info. If you can't get it done post the problem here.

If above seems difficult best would be to install a 64bit distro as advised above.

johnsfile and veerain: Like I said at the start, I'm new to Linux and without a lot more research and experience compiling my own kernel with my own tool set seems a far reach.

I'd like to load just the kernel but the distro contains everything. So I'll offload the data acquired and reload everything. That's probably the easiest and best thing I can do.

Thanks to all who provided help. I'm getting what I came for, which was knowledge of Linux. Thanks again.

You might think that. But even after building the kernel, that would have been a much worse can of worms than you imagine. Installing a 64 bit kernel into a 32-bit installed Linux is doable, but not simple.

Correct.