Skip to contentSkip to conversation

uml wouldn't link/compile with UDF

DISCUSSION Konstantin V. Gavrilenko 2 participants 2 messages Apr 13, 2005

lore
Share & tools
lore
#0 lore raw

linux-2.6.11.6.6

The uml wouldn't compile when the
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

The error output is:

  LD      lib/zlib_deflate/built-in.o
  LD      lib/zlib_inflate/built-in.o
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1

/usr/lib/libc.a(mktime.o)(.rodata+0x0): multiple definition of `__mon_yday' fs/built-in.o(.rodata+0x3380): first defined here
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm: '.tmp_vmlinux1': No such file
/bin/bash: line 1: 11859 Exit 1 nm -n .tmp_vmlinux1
11860 Segmentation fault | scripts/kallsyms >.tmp_kallsyms1.S
make: *** [.tmp_kallsyms1.S] Error 139

usetting the UDF options solves the issue.

Signature · 14 lines
Respectfully,
Konstantin V. Gavrilenko

Arhont Ltd - Information Security

web:    http://www.arhont.com
	http://www.wi-foo.com
e-mail: [email protected]

tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141

PGP: Key ID - 0x4F3608F7
PGP: Server - keyserver.pgp.com
#1 lore raw
Quoted 11 lines · Konstantin V. Gavrilenko

linux-2.6.11.6.6

The uml wouldn't compile when the
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

The error output is:

/usr/lib/libc.a(mktime.o)(.rodata+0x0): multiple definition of `__mon_yday' fs/built-in.o(.rodata+0x3380): first defined here

A symbol conflict between the kernel and libc. Not the first, and probably not the last. See the errno and sigprocmask flags in UML for a kludge for this sort of problem. A real solution is still lacking.

Jeff