a) About the sysconfdir, I defined it in .spec relative to _prefix, that
previosly I definet relative to l_prefix. Does the order of definitions
in the .spec is taken in account ?
b) objdump
I've never used objdump and don't know his purpose. Here are the outputs, if
they are meaningfull to you:
[EMAIL PROTECTED] alexb]$ type objdump
objdump is hashed (/opkg/bin/objdump)
[EMAIL PROTECTED] alexb]$ objdump -i
BFD header file version 2.14 20030612
elf32-i386
(header little endian, data little endian)
i386
a.out-i386-linux
(header little endian, data little endian)
i386
efi-app-ia32
(header little endian, data little endian)
i386
elf32-little
(header little endian, data little endian)
i386
elf32-big
(header big endian, data big endian)
i386
srec
(header endianness unknown, data endianness unknown)
i386
symbolsrec
(header endianness unknown, data endianness unknown)
i386
tekhex
(header endianness unknown, data endianness unknown)
i386
binary
(header endianness unknown, data endianness unknown)
i386
ihex
(header endianness unknown, data endianness unknown)
i386
trad-core
(header endianness unknown, data endianness unknown)
elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little elf32-big
i386 elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little elf32-big
srec symbolsrec tekhex binary ihex trad-core
i386 srec symbolsrec tekhex binary ihex ---------
[EMAIL PROTECTED] authlib]$ pwd
/opkg/RPM/TMP/courier-imap-2.2.1/authlib
[EMAIL PROTECTED] authlib]$ objdump -p authdaemon
authdaemon: file format elf32-i386
Program Header:
PHDR off 0x00000034 vaddr 0x08048034 paddr 0x08048034 align 2**2
filesz 0x000000c0 memsz 0x000000c0 flags r-x
INTERP off 0x000000f4 vaddr 0x080480f4 paddr 0x080480f4 align 2**0
filesz 0x00000013 memsz 0x00000013 flags r--
LOAD off 0x00000000 vaddr 0x08048000 paddr 0x08048000 align 2**12
filesz 0x000034d6 memsz 0x000034d6 flags r-x
LOAD off 0x000034d8 vaddr 0x0804c4d8 paddr 0x0804c4d8 align 2**12
filesz 0x000001cc memsz 0x00004214 flags rw-
DYNAMIC off 0x00003500 vaddr 0x0804c500 paddr 0x0804c500 align 2**2
filesz 0x000000c8 memsz 0x000000c8 flags rw-
NOTE off 0x00000108 vaddr 0x08048108 paddr 0x08048108 align 2**2
filesz 0x00000020 memsz 0x00000020 flags r--
Dynamic Section:
NEEDED libc.so.6
INIT 0x8048954
FINI 0x804a670
HASH 0x8048128
STRTAB 0x80485ac
SYMTAB 0x804828c
STRSZ 0x194
SYMENT 0x10
DEBUG 0x0
PLTGOT 0x804c5dc
PLTRELSZ 0x170
PLTREL 0x11
JMPREL 0x80487e4
REL 0x80487d4
RELSZ 0x10
RELENT 0x8
VERNEED 0x80487a4
VERNEEDNUM 0x1
VERSYM 0x8048740
Version References:
required from libc.so.6:
0x0d696911 0x00 03 GLIBC_2.1
0x0d696910 0x00 02 GLIBC_2.0
Cópia Michael Schloh von Bennewitz <[EMAIL PROTECTED]>:
> On Fri, Dec 12, 2003, [EMAIL PROTECTED] wrote:
> > I got rpm -bb SRC/courier-imap/courier-imap.spec to build all rpm
> >
> > The only strange message I reconized during compilation/packaging
> was:
> >
> > Finding Requires: (using /opkg/lib/openpkg/find-requires)...
> > objdump:
> /opkg/RPM/TMP/courier-imap-2.2.1-root/etc/init.d/courier-imap: File
> format not recognized
> > objdump:
>
/opkg/RPM/TMP/courier-imap-2.2.1-root/opkg/lib/courier-imap/libexec/authlib/authdaemond:
> File format not recognized
> > [...]
> >
> > How should I interpred this ?
> >
> I think you should interpret this as a failure. Have you tried running
> objdump? What doesn objdump -i indicate, or objdump -p authdaemond?
>
> > I also don't understand why I got some files (see build info below) in
> the
> > directory /etc and not /opkg/etc as I set in the .spec
> >
> > %define _prefix %{l_prefix}/lib/courier-imap
> > %define _sysconfdir %{_prefix}/etc
> > %define _mandir %{_prefix}/man
> >
> I have two guesses. First, maybe you failed to specify the system
> config
> directory to the configure script (often --sysconfdir=...). Second,
> maybe
> the configure script is broken or doesn't allow you to change the
> system
> configuration directory. In the latter case, you will have to find the
> places in the source files where the path is hard coded. Correct the
> hard
> coded pathnames using shtool subst or sed, just like is done in the
> package
> 'dss' quite a lot.
>
> > Does my courier-imap.spec and src.rpm are for some interest for the
> OpenPKG
> > project. I would like to be helpfull in any way for this great
> project.
> >
> Yes, it would be very nice to have courier-imap. Once your happy with
> your
> results, please contribute it and I'll test it out on all the other
> platforms.
>
> Regards,
> Michael
>
> --
> [EMAIL PROTECTED]
> Development Team, Operations Northern Europe
> Cable & Wireless Telecommunications Services GmbH
>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
