Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 76592 - net-mail/courier-imap-4.0.0 sed syntax errors in ./configure when checking for ld
Summary: net-mail/courier-imap-4.0.0 sed syntax errors in ./configure when checking f...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-03 20:07 UTC by Michael Crawford (ali3nx)
Modified: 2005-01-04 15:30 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Crawford (ali3nx) 2005-01-03 20:07:00 UTC
while installing net-mail/courier-imap-4.0.0 i noticed some sed errors reported from ./configure while checking for ld in every subsection of the configure. I'm using ccache so this doesn't apprear to be a big problem since cached ld is used if ld is not reported as fouund. This could be a problem for a new install of courier-imap and sane linking of courier-imap.

Reproducible: Always
Steps to Reproduce:
1. emerge =net-mail/courier-imap-4.0.0
2. observe configure while ./configure checks for the existance of ld
3. sedation reports ld no such file or directory with errors in condigure on lines 
   3336, 3433, 4670 and possibly other similar sed portions of configure

Actual Results:  
courier-imap completes configure successfully if ld is cached but reports ld as
"no such file or directory" most likely a simple fix for someone with sed experience



configure: loading cache
/var/tmp/portage/courier-authlib-0.52/work/courier-authlib-0.52/configuring.cache
checking for a BSD-compatible install... (cached) /bin/install -c
checking whether build environment is sane... yes
checking for gawk... (cached) gawk
checking whether make sets $(MAKE)... (cached) yes
checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... (cached) o
checking whether we are using the GNU C compiler... (cached) yes
checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... (cached) none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... (cached) gcc3
checking for a BSD-compatible install... /bin/install -c
checking whether ln -s works... yes
checking for perl5... (cached) /usr/bin/perl
checking for cat... /bin/cat
checking build system type... (cached) i686-pc-linux-gnu
checking host system type... (cached) i686-pc-linux-gnu
checking for a sed that does not truncate output... (cached)
checking for egrep... (cached) grep -E
checking for ld used by i686-pc-linux-gnu-gcc... ./configure: line 3433:
s%\\%/%g: No such file or directory
(cached) /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... (cached) yes
Comment 1 Dan A. Dickey 2005-01-04 10:11:05 UTC
I'm seeing this in net-libs/courier-authlib as well.
Any suggested workaround yet?
Is it a real problem?  I can't get courier-imapd-ssl to auth using MD5 yet.
I think the severity of this bug should be higher than trivial.
Comment 2 Tuan Van (RETIRED) gentoo-dev 2005-01-04 15:23:32 UTC
this is just a side affect of using configure cache. It doesn't cause any harm but I turned it off now to reduce "noise"

@ comment#1
I don't think this bug has anything to do with your issue. Anyway, the new ebuild commited without revision bump (I think it is trival). Please wait for an hour then sync/re-emerge as you wish.

Thanks, for reporting.
Comment 3 Dan A. Dickey 2005-01-04 15:30:02 UTC
Tuan,
you are correct - this had nothing to do with my problem.
Thanks for taking care of the noise though... :)

For the record; my problem turned out to be one of my
userdb not being moved or converted over to the new location
by the new ebuild.