Hi,

Well I took the same options ebuild  uses when it ran 
./configure, i used the same options again. Hence I
believe the use flags might be retained. I wouldn't
know until it is installed. A wild swing and try. I
just want to get over the compile error so that I  can
compile openldap which has a dependency on this
package. 

Thank you

regards
karan

--- Dave Nebinger <[EMAIL PROTECTED]> wrote:
> > I am trying to compile cyrus-sasl and during
> configure
> > i got the error that build options where changed
> in
> > CFLAGS even though they were not. the recommended
> at
> > the end of the script was to make distclean or rm
> > config.cache and try again
> > so i did that  and ran
> > 
> > ./configure with options below
> > make
> > touch .compiled  (in work directory) and then
> > 
> >  ebuild
> >
>
/usr/portage/dev-libs/cyrus-sasl/cyrus-sasl-2.1.20.ebuild
> > install
> > 
> > but that failed with error listed below.
> 
> I think if you interpreted the message as "either
> 'make distclean' or 'rm
> config.cache'" and only did the rm step, that was
> your downfall.
> 
> If you need to build it manually yet want the ebuild
> to manage it, I would
> probably try it in a couple of steps:
> 
> 1. ebuild [...]/cyrus-sasl-2.1.20.ebuild unpack
> 2. Go to the work directory and ./configure with
> your specific options
> 3. ebuild [...]/cyrus-sasl-2.1.20.ebuild install
> 
> Although I really can't understand why you would
> want to try to have portage
> manage a package that you're compiling yourself. 
> The next time a release is
> available and you emerge -uD world it would be
> replaced with one compiled
> without your specific flags.
> 
> If you want to manage sasl on your own (and I can
> understand why as I manage
> some packages outside of portage), just bite the
> bullet and do it; don't
> involve portage because it may come back to haunt
> you later on.
> 
> 
> 


                
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 
--
[email protected] mailing list

Reply via email to