[SOLVED] Problem compiling kernel for an Arch install on USB pendrive

I've installed Arch linux to a USB pendrive and I'm building a kernel for my specific hardware (Acer Aspire One) so as there is no kernel26.img file needed.
I've used gothicknight's custom kernel but it doesn't work for me as it doesn't recognise my USB stick (/dev/sdb). Instead, it just recognises the SSD (/dev/sda). I believe the standard Arch kernel uses a "hook" called "usb" in order to work from a USB stick - at least that's how I've got the current (default) Archlinux kernel working.
I'm not that skilled at linux and am still quite new to kernel compilation (I've done it once or twice before and, yes, I've read the ArchWiki articles - both of them). Can anyone tell me what I should do to get things working on a USB stick install?
Kind regards
Last edited by Shagbag (2008-09-30 20:27:49)

Solved it. I didn't need to recompile. I just needed to add 'rootdelay=5' as a kernel boot parameter.

Similar Messages

[SOLVED] error compiling kernel 2.6.29

Hi,
Due to having the DVD-S card mentioned here
http://www.linuxtv.org/pipermail/linux- … 23265.html
I am trying to compile kernel 2.6.29.6 with the above mentioned patch but get an error:
include/sound/soc-dai.h: At top level:
include/sound/soc-dai.h:224:25: error: duplicate member ‘codec’
sound/soc/soc-core.c: In function ‘snd_soc_init_card’:
sound/soc/soc-core.c:1360:18: warning: variable ‘ac97’ set but not used
[-Wunused-but-set-variable]
make[2]: *** [sound/soc/soc-core.o] Error 1
make[1]: *** [sound/soc] Error 2
make: *** [sound] Error 2
bash: vim include/sound/soc-dai.h
/* DAI runtime info */
struct snd_pcm_runtime *runtime;
struct snd_soc_codec *codec;
unsigned int active;
unsigned char pop_wait:1;
void *dma_data;
/* DAI private data */
void *private_data;
/* parent codec/platform */
union {
struct snd_soc_codec *codec;
struct snd_soc_platform *platform;
Note:
I found a solution:
http://mailman.alsa-project.org/piperma … 16949.html
Last edited by casacristo (2011-10-19 07:46:01)

I've solved the issue, infact there was a problem with the patch. Now I am able to compile the kernel.
Thanks anyway!

Compiling Kernel for 24 CPU threads

I've been looking around but can't find an answer to this yet. How can I compile a x86_64 kernel for 24 CPUs? By default in the x86_64 config is set to CONFIG_NR_CPUS=16.
Thanks in advance!

Use ABS to do it (see the wiki) or use a pre-made kernel from the AUR. See kernel26-ck from my sig for example. Just enable the menuconfig option and you can customize the entire thing if you wish.

[Solved] Problems compiling a kernel on Archlinux

Hi all, some days ago I wanted to compile a kernel on my system, and everything was fine but I have a simple problem.
Compile the kernel in the traditional manner, but no logo create the ramdisk image.
https://wiki.archlinux.org/index.php/Ke … raditional
Example:
cp -v arch/x86/boot/bzImage /boot/vmlinuz-NewKernel
And:
mkinitcpio -k NewKernel -g /boot/initramfs-NewKernel.img
But I get this error:
Error: unable to locate module directory for NewKernel.
What am I doing wrong?
PD:Sorry for my English
Last edited by Linpandro (2012-10-03 13:50:43)

This:
mkinitcpio -k NewKernel -g /boot/initramfs-NewKernel.img
Should be this:
mkinitcpio -k 3.x.x-RCn-NewKernel -g /boot/initramfs-NewKernel.img
To clarify, the wiki tells you to run this:
# mkinitcpio -k FullKernelName -g /boot/initramfs-YourKernelName.img
If you need any modules loaded in order to mount the root filesystem, build a ramdisk (most users need this). The -k parameter accepts the kernel version and appended string you set in menuconfig and is used to locate the corresponding modules directory in '/usr/lib/modules':
If you used the sources for, say, 3.5.4, "FullKernelName" would be 3.5.4-NewKernel.
If you're not sure about what the "FullKernelName" should be, simply check which directory was created after running modules_install
ls -l /lib/modules
This should show you something like this:
[stefan@archsteef scrub]$ ls -l /lib/modules/
total 8
drwxr-xr-x 3 root root 4096 Sep 30 01:30 3.5.4-1-ARCH
drwxr-xr-x 2 root root 4096 Sep 30 01:30 extramodules-3.5-ARCH
drwxr-xr-x 2 root root 4096 Oct 1 03:25 3.5.4-NewKernel
The directory name is the full name of your kernel and can be used after the -k flag.
p.s. this is all assuming that you used make menuconfig to set the local version name to "NewKernel"
Last edited by stefanwilkens (2012-10-03 08:15:26)

[ SOLVED ] Partition Sizes For New Arch Install ?

Hi All
I have just picked up a new 250gb HDD and i'm going to do a clean install of arch & openbox and would like to know what people would suggest for various partition sizes ?
/root
/swap
etc
I have 4gb ram so not sure if swap is a required !
Many Thanks
Last edited by whitetimer (2010-11-15 09:58:47)

+1 on KlavKalashj's advice!
When the installer warns you about there not being a /boot partition either(besides the swap), then just select ignore, it's no problem at all!
If you do want a swap partiton(and don't hibernate), then I would say max 1gb imho.
For an Openbox based install, then I would say 10GB is more than enough(mine's 5, although with a tiling WM: Musca).
I don't keep the cache forever increasing, but empty it at times where I know everything is OK. Also, there's scripts available which cleans the cache up, like e.g. only keeping one revision back of each package.
Last edited by mhertz (2010-11-15 09:47:18)

Compiled kernel module fails to install

A few moments ago finished compiling my own kernel, but still I can not boot with the new kernel.
When installing modules:
make modules_install
I get this:
Warning: you may need to install module-init-tools
The kernel was compiled in the traditional manner, and I get no error with mkinitcpio:
----> mkinitcpio -k 3.2.9 New -g /boot/initramfs-New.img
==> Starting build: 3.2.9
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
-> Running build hook: [fglrx]
Building fglrx module for 3.2.9 kernel ...
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-New.img
==> Image generation successful
I have the entry in grub and I can enter without problem, but there comes a point where you do not start:
Waiting 10 seconds for device /dev/sda4 ...
ERROR: Unable to find root device '/dev/sda4'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
And if my partition /root is /dev/sda4,I found a topic like this, but even I can not fix the problem:
https://bbs.archlinux.org/viewtopic.php?id=135851

I compiled the kernel old version that I have problems with the battery life on the newer versions.
The battery only lasts me one hour, but that is another problem.
fdisk:
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificador del disco: 0x5d8c0991
Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sda1 * 2048 409599 203776 7 HPFS/NTFS/exFAT
/dev/sda2 409600 147210239 73400320 7 HPFS/NTFS/exFAT
/dev/sda3 147219660 862304939 357542640 5 Extendida
/dev/sda4 * 862304940 976773167 57234114 83 Linux
/dev/sda5 147219723 859477499 356128888+ 7 HPFS/NTFS/exFAT
/dev/sda6 859477563 862304939 1413688+ 82 Linux swap / Solaris
/lib/modules:
drwxr-xr-x 4 root root 4096 oct 3 20:40 3.2.9
drwxr-xr-x 3 root root 4096 oct 3 08:55 3.5.4-1-ARCH
drwxr-xr-x 2 root root 4096 oct 3 08:55 extramodules-3.5-ARCH
/boot:
drwxr-xr-x 6 root root 4096 oct 3 06:20 grub
-rw-r--r-- 1 root root 12612222 oct 3 08:55 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 3098536 oct 3 08:55 initramfs-linux.img
-rw-r--r-- 1 root root 2016551 oct 3 20:40 initramfs-New.img
-rw-r--r-- 1 root root 2081862 oct 3 19:37 System.map-New
-rw-r--r-- 1 root root 3444736 sep 15 00:15 vmlinuz-linux
-rw-r--r-- 1 root root 4434400 oct 3 19:35 vmlinuz-New
I install grub-legacy of AUR, but I have to change to syslinux.
For now this is my menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,3)
kernel /boot/vmlinuz-linux root=/dev/sda4 nomodeset vga=773 ro
initrd /boot/initramfs-linux.img
# (0) Arch Linux
title Arch Linux NK
root (hd0,3)
kernel /boot/vmlinuz-New root=/dev/sda4 nomodeset ro
initrd /boot/initramfs-New.img

[solved]Problem compiling alsa from source

I'm trying to install alsa-driver-1.0.18a from source because I need to compile it with snd-virtuoso. So I run "./configure --with-cards=virtuoso --with-sequencer=yes" then when I run "make" I get this at the end of it.
make -C /lib/modules/2.6.27-ARCH/build SUBDIRS=/usr/src/alsa/alsa-driver-1.0.18a CPP="gcc -E" CC="gcc" modules
make[1]: Entering directory `/usr/src/linux-2.6.27-ARCH'
CC [M] /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.o
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:282:1: warning: "GFP_DMA32" redefined
In file included from include/linux/kmod.h:22,
from include/linux/module.h:13,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:57,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/gfp.h:105:1: warning: this is the location of the previous definition
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:831: error: static declaration of 'jiffies_to_msecs' follows non-static declaration
include/linux/jiffies.h:286: error: previous declaration of 'jiffies_to_msecs' was here
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:850: error: static declaration of 'msecs_to_jiffies' follows non-static declaration
include/linux/jiffies.h:288: error: previous declaration of 'msecs_to_jiffies' was here
In file included from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:948,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/pci.h:627: error: expected identifier or '(' before numeric constant
In file included from include/asm/pci.h:4,
from include/linux/pci.h:989,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:948,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/linux/mm.h:261: error: conflicting types for 'snd_compat_vmalloc_to_page'
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:752: error: previous declaration of 'snd_compat_vmalloc_to_page' was here
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h: In function 'snd_pci_orig_save_state':
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1197: error: too many arguments to function 'pci_save_state'
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h: In function 'snd_pci_orig_restore_state':
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1201: error: too many arguments to function 'pci_restore_state'
In file included from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
/usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:1598:1: warning: "page_to_pfn" redefined
In file included from include/asm/page.h:196,
from include/asm/pda.h:8,
from include/asm/current.h:19,
from include/asm/processor.h:15,
from include/linux/prefetch.h:14,
from include/linux/list.h:6,
from include/linux/module.h:9,
from /usr/src/alsa/alsa-driver-1.0.18a/include/adriver.h:57,
from /usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:25:
include/asm-generic/memory_model.h:78:1: warning: this is the location of the previous definition
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c: In function 'snd_compat_vmalloc_to_page':
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:44: error: implicit declaration of function 'VMALLOC_VMADDR'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:49: error: incompatible type for argument 1 of 'pud_val'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:50: error: implicit declaration of function 'pte_offset'
/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.c:50: warning: assignment makes pointer from integer without a cast
make[3]: *** [/usr/src/alsa/alsa-driver-1.0.18a/acore/memory_wrapper.o] Error 1
make[2]: *** [/usr/src/alsa/alsa-driver-1.0.18a/acore] Error 2
make[1]: *** [_module_/usr/src/alsa/alsa-driver-1.0.18a] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.27-ARCH'
make: *** [compile] Error 2
edit: I tried compiling it on another computer and it was able too...not sure why mine wont. Although I do seem to remember possibly forgetting to uninstall it before making it again (after kernel upgrade)...I've tried multiple times to compile so far. Is there someway I can get a list of things to delete to manually remove all remnants of a previous install of alsa-driver?
Last edited by Gauvenator (2008-12-13 19:48:11)

Ok I ended up compiling the kernel from source for something else, so I tried compiling the alsa driver from source and it worked...maybe something was leftover in the previous kernel source directory that was causing problems.

[Solved] Error compiling kernel 2.6.36.2 patched with MOSIX

Hi, I'm a new user in this forum!
I'm trying to compile manually the kernel version with MOSIX-2.29.0.1 for computer clustering. But When I try to compile it with make command there is an error:
In file included from arch/x86/kernel/signal.c:17:0:
include/linux/tracehook.h: In function ‘tracehook_unsafe_exec’:
include/linux/tracehook.h:164:40: error: ‘struct task_struct’ has no member named ‘mflags’
arch/x86/kernel/signal.c: In function ‘do_notify_resume’:
arch/x86/kernel/signal.c:884:44: error: ‘struct task_struct’ has no member named ‘parent_waiting’
make[2]: *** [arch/x86/kernel/signal.o] Error 1
make[1]: *** [arch/x86/kernel] Error 2
make: *** [arch/x86] Error 2
I have launched make menuconfig and I have configured the kernel in this way:
Configure the following option:
CONFIG_FUSE_FS
File systems ---> FUSE (Filesystem in Userspace) support
CONFIG_SYSVIPC
General setup ---> System V IPC
But make sure that the following is NOT CONFIGURED:
CONFIG_HEADERS_CHECK"
'Kernel hacking' ---> 'Run 'make headers_check' when building vmlinux'
What is the problem?
Last edited by andychaser (2011-02-17 12:37:50)

I've solved the issue, infact there was a problem with the patch. Now I am able to compile the kernel.
Thanks anyway!

Compile kernel 2.4 arch

Hi guys, I need to compile manually the kernel 2.4 on archlinux. I need to do that for an university course I'm following. I did that several time with version 2.6 on gentoo, but now with version 2.4 on arch I got a problem: it seems I'm missing "genksyms" (I don't know exactly what it is). Can you tell me how to find and install it? Any other suggestion to deal with the compile process of kernel 2.4?? Thanks

.:B:. wrote:
Raffo wrote:
.:B:. wrote:
Are you aware that there are certain intricacies involved in building a 2.4 kernel on a system that is tuned for a 2.6 kernel?
Does the word 'toolchain' mean anything to you without having to resort to google? If not, how about 'glibc'?
I.e. do you know what you are trying to accomplish?
I believe it's better to give informations in a post instead of writing questions to someone who's looking for a solution to his problem. However, I know that there can be differences, but since I never used the kernel 2.4 I don't know about the consequences. Again, it would have been better for me to learn something from your post.
While it might not be what you were looking for, there is some very constructive material in my post. My questions - when answered - would have allowed you to put your own question in perspective.
I did not say that I wouldn't try to answer to your questions, but I just believe that yours is not the way to help an user. Asking to "google it" is not very kind to me. However I can find all the other informations I need by myself, obviously, I was just talking about the way you answered. Sorry for the OT, this OT ends here, for me.
If you refuse to do that, that's your choice. I'm trying to make you think about the ramifications of your little project.
People who say or think complicated things are easy usually don't know anything about it .
I'm not refusing to do that

[Solved]Error compiling kernel from abs

Hello Everyone,
I've hit a wall trying to compile the kernel from the abs. I get this error message:
patching file fs/fat/inode.c
Hunk #1 succeeded at 800 (offset 74 lines).
HOSTCC scripts/basic/fixdep
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[2]: *** [scripts/basic/fixdep] Error 126
make[1]: *** [scripts_basic] Error 2
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_32.h
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_64.h
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make: *** Waiting for unfinished jobs....
HOSTCC scripts/basic/fixdep
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_x32.h
SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[1]: *** [scripts/basic/fixdep] Error 126
make: *** [scripts_basic] Error 2
==> ERROR: A failure occurred in build().
Aborting...
While trying to figure this out I came across this post: https://bbs.archlinux.org/viewtopic.php?id=99089 and have tried the solutions presented. I did end up having to change my fstab to include defaults,
/dev/sda3 /home ext4 defaults,exec,rw,relatime,data=ordered 0 2
and the permissions on scripts/basic/fixdep are: -rwxr-xr-x which i think it correct.
Unfortunately, the problem still exists and I don't know how to continue trouble shooting. Can someone point me in a direction to troubleshoot this?
Last edited by magyarm (2012-12-20 01:55:00)

magyarm wrote:So now, I need to figure out a good way to handle multiple compilers on my system to prevent this from happening again. If anyone has any tips I would love to hear them.
Set up a file that you source from bash to prepend the cross compiler to your path, that would only be active for that shell, and when you're done just close it. Means you only activate the cross compiler when you need it.

[solved] Problems compiling hydrogen

I'm trying to compile hydrogen version 0.9.4, so I can use Qt4. I made a PKGBUILD by editing the PKGBUILD of ABS and following the instructions of this page
It compiles everything ok, but the problem is when running 'make install', I guess. I'm compiling it using makepkg, so I don't know why I'm having problems with permissions denied. These are the relevant error messages:
cd gui/ && make -f Makefile install
make[1]: Entering directory `/home/andre/tmp/hydrogen/src/hydrogen-build/gui'
install -m 755 -p "../hydrogen" "/usr/bin/hydrogen"
install: cannot create regular file `/usr/bin/hydrogen': Permission denied
make[1]: [install_target] Error 1 (ignored)
strip "/usr/bin/hydrogen"
strip: '/usr/bin/hydrogen': No such file
make[1]: [install_target] Error 1 (ignored)
mkdir: cannot create directory `/usr//share/hydrogen': Permission denied
make[1]: *** [install_documentation] Error 1
make[1]: Leaving directory `/home/andre/tmp/hydrogen/src/hydrogen-build/gui'
make: *** [sub-gui-install_subtargets] Error 2
Even with the two errors, it finishes making the package, but it only has the /usr/share dir in it, there's no /usr/lib or /usr/bin.
Here's the PKGBUILD:
pkgname=hydrogen-qt4
pkgver=248
pkgrel=1
pkgdesc="An advanced drum machine/pattern editor with midi support for GNU/Linux"
url="http://www.hydrogen-music.org/"
arch=(i686 x86_64)
license=('GPL')
depends=('qt' 'liblrdf' 'jack-audio-connection-kit>=0.102.20-2')
makedepends=('subversion' 'lash' 'libtar')
provides=('hydrogen')
conflicts=('hydrogen')
install=hydrogen.install
source=(hydrogen.desktop)
md5sums=('8d6eacef58aa22cdba97485f9bdbb4b3')
options=('!makeflags')
_svntrunk=http://hydrogen-music.org/svn/trunk
_svnmod=hydrogen
build() {
cd ${startdir}/src
msg "Connecting to $_svnmod SVN server...."
svn co $_svntrunk $_svnmod
[ -d ./$_svnmod-build ] && rm -fr ./$_svnmod-build
cp -r ./$_svnmod ./$_svnmod-build
cd ./$_svnmod-build
msg "SVN checkout done or server timeout"
msg "Starting make..."
prefix=/usr/ ./configure || return 1
make || return 1
make DESTDIR=${startdir}/pkg install
install -D -m644 ${startdir}/src/hydrogen.desktop \
${startdir}/pkg/usr/share/applications/hydrogen.desktop
mkdir ${startdir}/pkg/usr/share/pixmaps
cd ${startdir}/pkg/usr/share/pixmaps
ln -s ../hydrogen/data/img/gray/icon.svg ./hydrogen.svg
ln -s ../hydrogen/data/img/gray/icon64.png ./hydrogen.png
The line "prefix=/usr/ ./configure" is correct, if you use --prefix=/usr/ after ./configure, configure will ignore it.
What is wrong with it?
Thanks
Last edited by andre.ramaciotti (2008-07-17 00:31:10)

you should keep:
prefix=/usr/ ./configure
because path given to the configure script can be hard-coded in the apps.
instead use:
make prefix=${startdir}/usr/pkg install
It's strange that the usual ./configure --prefix=/usr doesn't work. I haven't checked the sources BTW.

[SOLVED] Problem compiling Suitesparse: hidden symbol `__powidf2'

Hi guys, hope this is the right section to post this problem. I'm trying to compile (and install) Suitesparse but everytime i obtain this strange error i have never seen before...any idea to solve it?Thanks
cholmod_super_numeric.c:(.text+0x117d): undefined reference to `dsyrk_'
cholmod_super_numeric.c:(.text+0x125c): undefined reference to `dgemm_'
cholmod_super_numeric.c:(.text+0x184d): undefined reference to `dtrsm_'
cholmod_super_numeric.c:(.text+0x2401): undefined reference to `zherk_'
cholmod_super_numeric.c:(.text+0x24e5): undefined reference to `zgemm_'
cholmod_super_numeric.c:(.text+0x2a08): undefined reference to `ztrsm_'
cholmod_super_numeric.c:(.text+0x35c1): undefined reference to `zherk_'
cholmod_super_numeric.c:(.text+0x36a5): undefined reference to `zgemm_'
cholmod_super_numeric.c:(.text+0x3c17): undefined reference to `ztrsm_'
../Lib/libcholmod.a(cholmod_super_solve.o): In function `cholmod_super_ltsolve':
cholmod_super_solve.c:(.text+0x715): undefined reference to `zgemm_'
cholmod_super_solve.c:(.text+0x7b2): undefined reference to `ztrsm_'
cholmod_super_solve.c:(.text+0xa37): undefined reference to `zgemv_'
cholmod_super_solve.c:(.text+0xaa1): undefined reference to `ztrsv_'
cholmod_super_solve.c:(.text+0xde7): undefined reference to `dgemm_'
cholmod_super_solve.c:(.text+0xe7b): undefined reference to `dtrsm_'
cholmod_super_solve.c:(.text+0x10c8): undefined reference to `dgemv_'
cholmod_super_solve.c:(.text+0x112c): undefined reference to `dtrsv_'
../Lib/libcholmod.a(cholmod_super_solve.o): In function `cholmod_super_lsolve':
cholmod_super_solve.c:(.text+0x182c): undefined reference to `ztrsm_'
cholmod_super_solve.c:(.text+0x18fc): undefined reference to `zgemm_'
cholmod_super_solve.c:(.text+0x1a46): undefined reference to `ztrsm_'
cholmod_super_solve.c:(.text+0x1bea): undefined reference to `ztrsv_'
cholmod_super_solve.c:(.text+0x1c94): undefined reference to `zgemv_'
cholmod_super_solve.c:(.text+0x1fb5): undefined reference to `dtrsm_'
cholmod_super_solve.c:(.text+0x2080): undefined reference to `dgemm_'
cholmod_super_solve.c:(.text+0x219b): undefined reference to `dtrsm_'
cholmod_super_solve.c:(.text+0x231f): undefined reference to `dtrsv_'
cholmod_super_solve.c:(.text+0x23c6): undefined reference to `dgemv_'
/usr/bin/ld: cholmod_demo: hidden symbol `__powidf2' in /usr/lib/gcc/x86_64-unknown-linux-gnu/4.3.2/libgcc.a(_powidf2.o) is referenced by DSO
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld returned 1 exit status
make[1]: *** [cholmod_demo] Error 1
Last edited by Demind (2008-09-15 11:09:07)

Garns wrote:Does your atlas package contain libblas.a or does the blas library have another name? I scanned the atlas makefile and I couldn't find a reference to libblas.a, only libf77blas.a and libcblas.a. Are the libs installed to /usr/libs/ or to some subdir? If one of this is the case you might have to edit UFconfig/UFconfig.mk accordingly.
Sorry this problem is so frustrating that i have pasted the wrong error...actually i had a UFconfig/UFconfig.mk edited and that gave me the same problem, I don't have libblas.a on my system but the reason is that this is substitued by libatlas.a!
I paste here the "final" result:
make[2]: Leaving directory `/home/marco/Desktop/SuiteSparse/CCOLAMD'
gcc -O3 -fexceptions -m64 -o cholmod_demo -I../Include -I../../UFconfig cholmod_demo.c ../Lib/libcholmod.a ../../AMD/Lib/libamd.a ../../COLAMD/Lib/libcolamd.a ../../CCOLAMD/Lib/libccolamd.a ../../CAMD/Lib/libcamd.a ../../metis-4.0/libmetis.a -llapack -lgfortran -lgfortran -lpthread -Lusr/lib -lf77blas -latlas -lm
/usr/bin/ld: cholmod_demo: hidden symbol `__powidf2' in /usr/lib/gcc/x86_64-unknown-linux-gnu/4.3.2/libgcc.a(_powidf2.o) is referenced by DSO
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld returned 1 exit status
make[1]: *** [cholmod_demo] Error 1
Obviously the "undefined reference" statements are gone but the main problem, the hidden symbol, is always there...and now i'm sure this is the error i hope to solve, the first one (and i apologize for that) was a build with wrong flag...
And when i wrote about a possible gcc version problem was because this line says:
/usr/bin/ld: cholmod_demo: hidden symbol `__powidf2' in /usr/lib/gcc/x86_64-unknown-linux-gnu/4.3.2/libgcc.a(_powidf2.o) is referenced by DSO
what do you think about it?
p.s. i can compile UMFPACK without problems...the whole Suite on the contrary gives me this

[Solved] Problem using kdebindings for ruby

As a weekend project I was going to look into using ruby as language for developing KDE plasma widgets.
I have kdebindings-ruby 4.6.0-1 along with the required kdebindings-smoke 4.6.0-1.
When trying:
require "plasma_applet"
I get the error:
LoadError: libsmokebase.so.3: cannot open shared object file: No such file or directory - /usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/plasma_applet.so
However when checking the directory
/usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/
32K plasma_applet.so
shows up clear as day.
So what gives? I haved tried to find an answer here on the forums and on google but perhaps my google foo is too weak.
Thanks
Edit: With some more google foo I found this: https://github.com/pcapriotti/kaya/issu … ed#issue/3
Where this statement is made:
Kdebindings-smoke does not provide anymore libsmokebase.so.3, either in chakra-Linux or Arch Linux, was available in kde 4.5.5 but no in 4.6.0
Does this need to be submitted as a bug?
Last edited by ilpianista (2011-02-25 13:22:49)

Hi, i know this is solved but i have similar problem with kdebindings-qtruby 4.7.0-1
i start irb. and when i type require "Qt"
irb(main):003:0> require "Qt"
LoadError: libsmokebase.so.3: cannot open shared object file: No such file or directory - /usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/qtruby4.so
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from /usr/lib/ruby/site_ruby/1.9.1/Qt.rb:1:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from (irb):3
from /usr/bin/irb:12:in `<main>'
same when i try require "qtruby4" or somethink like this.
but file /usr/lib/ruby/site_ruby/1.9.1/x86_64-linux/qtruby4.so exist

[SOLVED] Problems in permissions for accessing files

Hi everyone
let's say I want to copy a folder to /etc/
the problems is my user can't copy files anywhere other then it's home it doesn't even have access to any file or folder other then home.
on the other hand I can use root to view and copy or access but the files that root creates or copies are only for root , I mean other groups or users can't access them .
I tried changing permissions on files ( chmod , chown) but sometimes it takes a lot of time .
can you tell me how I can give my own user those permissions ?(permission of copying file to a folder like /etc/ or creating a file in there )
is there a way to change root's default setting so when i create something with root that file or folder be accessible for others automatically ?!
sorry if my questions are dumb
--N3mo
Last edited by N3mo (2012-11-16 16:49:43)

You can indeed do that. I have no intention of telling you how.
What you are trying to do is dangerous and, frankly, idiotic. I am sure that you are no idiot but your strategy is idiotic. (Smart people often do dumb things.)
If you insist on doing this, you can do it. But you should learn about the security system you are disregarding so that you know the risks. If you do that, you will know how to run those risks if you wish.
What packages are you downloading? Do you mean pacman's cache? Why do you want your user to have write access there?
Note that apart from the general idiocy of this strategy, it will also prevent some programmes from working at all because some of them check for sane permissions and refuse to run if they find the permissions are insane.
I don't even understand why you want to change root's settings. If you are working as root anyway, why do you also want your user to have access?
You can keep themes etc. in your home directory in appropriate places. Then you have complete control of them. You should not be adding additional themes to the system's collection except by installing packages with pacman.
Please learn about the way that the file structure, permissions and access controls are supposed to work and the protection that they offer you. (From yourself as well as other people.)

[solved] Problem compiling ConTeXt code

I'd like to start learning ConTeXt and I've just tried to compile a simple hello world:
\starttext
Hello world.
\stoptext
when compiling with texexec I get this output:
mtxrun | kpse fallback with progname 'context' initialized in 0.02 seconds/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': /usr/share/texmf-dist/scripts/context/ruby/base/switch.rb:501: invalid multibyte escape: /\xFF/ (SyntaxError)
from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
from /usr/share/texmf-dist/scripts/context/ruby/texexec.rb:11:in `<main>'
I have ruby and all texlive packags installed except texlive-lang*. Searching for an answer I found an old discussion on the forum (2008) where it was suggested to run
luatools --generate
before using texexec, but this lead me to another error:
mtxrun | unknown script 'base.lua' or 'mtx-base.lua'
Am I missing some package-stuff necessary to compile ConTeXt code?
edit: looks like I was reading an obsolete guide. It is now reccomended to compile code with "context <filename>", which works fine.
Last edited by Box0 (2013-04-15 09:18:52)

Hi there,
I tried
g++ mclient.cpp -llibboost_filesystem -llibboost_program_options -llibboost_system -llibboost_thread -o tutorial
and received
/usr/bin/ld: cannot find -llibboost_filesystem
/usr/bin/ld: cannot find -llibboost_program_options
/usr/bin/ld: cannot find -llibboost_system
/usr/bin/ld: cannot find -llibboost_thread
collect2: error: ld returned 1 exit status

[SOLVED] Problem compiling kernel for an Arch install on USB pendrive

Similar Messages

Maybe you are looking for