On Tue, 22 Oct 2013 10:16:53 -0500
Bruce Dubbs <bruce.du...@gmail.com> wrote:

> Did the previous line appear to run OK?
> 
> /bin/sh ../libtool --tag=CC   --mode=link gcc  -g -O2  -version-info 
> 3:0:0 -static-libstdc++ -static-libgcc  -o libmpc.la -rpath /tools/lib 
> abs.lo acos.lo acosh.lo add.lo add_fr.lo add_si.lo add_ui.lo arg.lo 
> asin.lo asinh.lo atan.lo atanh.lo clear.lo cmp.lo cmp_si_si.lo conj.lo 
> cos.lo cosh.lo div_2si.lo div_2ui.lo div.lo div_fr.lo div_ui.lo exp.lo 
> fma.lo fr_div.lo fr_sub.lo get_prec2.lo get_prec.lo get_version.lo 
> get_x.lo imag.lo init2.lo init3.lo inp_str.lo log.lo log10.lo mem.lo 
> mul_2si.lo mul_2ui.lo mul.lo mul_fr.lo mul_i.lo mul_si.lo mul_ui.lo 
> neg.lo norm.lo out_str.lo pow.lo pow_fr.lo pow_ld.lo pow_d.lo pow_si.lo 
> pow_ui.lo pow_z.lo proj.lo real.lo urandom.lo set.lo set_prec.lo 
> set_str.lo set_x.lo set_x_x.lo sin.lo sin_cos.lo sinh.lo sqr.lo sqrt.lo 
> strtoc.lo sub.lo sub_fr.lo sub_ui.lo swap.lo tan.lo tanh.lo 
> uceil_log2.lo ui_div.lo ui_ui_sub.lo  -lmpfr -lgmp -lm
> 
> That's what produces libmpc.la
 
 /bin/sh ../libtool --tag=CC   --mode=link gcc  -g -O2  -version-info 3:0:0 
-static-libstdc++ -static-libgcc  -o libmpc.la -rpath /tools/lib abs.lo acos.lo 
acosh.lo add.lo add_fr.lo add_si.lo add_ui.lo arg.lo asin.lo asinh.lo atan.lo 
atanh.lo clear.lo cmp.lo cmp_si_si.lo conj.lo cos.lo cosh.lo div_2si.lo 
div_2ui.lo div.lo div_fr.lo div_ui.lo exp.lo fma.lo fr_div.lo fr_sub.lo 
get_prec2.lo get_prec.lo get_version.lo get_x.lo imag.lo init2.lo init3.lo 
inp_str.lo log.lo log10.lo mem.lo mul_2si.lo mul_2ui.lo mul.lo mul_fr.lo 
mul_i.lo mul_si.lo mul_ui.lo neg.lo norm.lo out_str.lo pow.lo pow_fr.lo 
pow_ld.lo pow_d.lo pow_si.lo pow_ui.lo pow_z.lo proj.lo real.lo urandom.lo 
set.lo set_prec.lo set_str.lo set_x.lo set_x_x.lo sin.lo sin_cos.lo sinh.lo 
sqr.lo sqrt.lo strtoc.lo sub.lo sub_fr.lo sub_ui.lo swap.lo tan.lo tanh.lo 
uceil_log2.lo ui_div.lo ui_ui_sub.lo  -lmpfr -lgmp -lm 
libtool: link: warning: library `/usr/lib64/libmpfr.la' was moved.

There is a warning on this line but no error. I notice though that it also 
references /usr/lib64. You are right: there must be something fundamentally 
wrong with my setup.

> > I have not installed this build because it was not done "by the book"
> > and I am afraid of polluting my tool chain. Can someone please tell me:
> > 1) If it is safe to install it?
> 
> I wouldn't do that. 
That's what I thought!
> 
> The proper way is to start over, double checking section 4.4.
> 
>    -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to