On Mon, Dec 15, 2003, [EMAIL PROTECTED] wrote: > C�pia Michael Schloh von Bennewitz <[EMAIL PROTECTED]>: >> On Mon, Dec 15, 2003, [EMAIL PROTECTED] wrote: >>> 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 ? >>> >> When you build the courier-imap without OpenPKG, then how do you make >> it install its config files in your selected config file path (for >> example /tmp/test/)? Whatever your answer is to this question, do the >> same thing in the spec file. >> > I never build courier-imap by executing directly configure. Previously > I build it with rpm -bb just using the .spec acompaning the source. > In the last rpm -bb log I checked that --syconfdir=/opkg/lib/courier-imap/etc > where pased, so it may be in an other part of the .spec where I missed to > prepend the %l_prefix > Okay, so I understand that config files that you want in /opkg/lib/courier-imap/etc are being installed to /etc. I assume that courier-imap is a package that uses an autoconf-based configure script to create its makefile, and that you are correctly passing the arguments to the configure script for the system config directory.
Now if your question is 'why aren't the config files installed in the right
place', then my guess is that the configure script is broken. If this is
true, then you might have to debug it and correct the broken parts by using
substitution logic (shtool subst or sed) in your spec file.
It might also be that your install logic is wrong (see %install section in
your spec file). I don't think that's true however, because then all of your
installation paths would be wrong.
I find it strange that Bill's spec file would install these config files to
the correct location, but your's doesn't. Why this difference?
>> So try both '/usr/bin/objdump -i' and '/cw/bin/objdump' and compare
>> the results. Same thing with '/usr/bin/objdump -p authdaemond' and
>> '/cw/bin/objdump -p authdaemond'.
>
>Both {/usr/bin|/opkg/usr/bin}objdump -i/-p authdaemon seam to produce the
>same result yet, so I suspect the there should by a working path error
>while building the package, or something else ??
>
Are there other objdump commands on your system? Remember that one objdump
could not read the file format of the 'authdaemond' binary. At least that is
what you reported. Is this still happening when you build courier-imap, does
this happen when you build Bill's package, and does this happen when you
build any other OpenPKG package?
Regards,
Michael
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe
Cable & Wireless Telecommunications Services GmbH
pgp00000.pgp
Description: PGP signature
