On Sun, Sep 04, 2005 at 12:11:08PM +0300, Ilja Honkonen wrote:
>
> No it did not, I noticed this when Groff wouldn't configure complaining that
> it couldn't compile c++ programs. There were no gcc or c++ or even cc in
> /usr/bin. Very strange, but everyting worked after I installed gcc.
> Should
c-linux-gnu/3.4.3/../../../../i686-pc-linux-gnu/bin/ld:
> > cannot find -lstdc++
> > collect2: ld returned 1 exit status
> > make[1]: *** [demo] Error 1
> > make[1]: Leaving directory make[1]: Leaving directory
> > `/sources/ncurses-5.4/c++\'
> > make: *** [a
M.Canales.es wrote:
El Domingo, 4 de Septiembre de 2005 10:49, Chris Staub escribió:
I don't think that's a problem with the fact that you stopped and
restarted - if libstdc++ does not exist in /usr/lib then you forgot to
install the c++ compiler in chap. 6. Does /usr/bin/gcc e
El Domingo, 4 de Septiembre de 2005 10:49, Chris Staub escribió:
> I don't think that's a problem with the fact that you stopped and
> restarted - if libstdc++ does not exist in /usr/lib then you forgot to
> install the c++ compiler in chap. 6. Does /usr/bin/gcc exist?
I thin
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/devices.html
I fixed the above error by adding this to chapter 6.6:
ln -s /tools/lib/libstdc++.{so,.6} /usr/lib
I have no idea if this is the correct fix, or if the problem was somewhere
else. There was no libstdc++* in /mnt/lfs/ or its subdirectories w
/view/stable/chapter06/devices.html
I fixed the above error by adding this to chapter 6.6:
ln -s /tools/lib/libstdc++.{so,.6} /usr/lib
I have no idea if this is the correct fix, or if the problem was somewhere
else. There was no libstdc++* in /mnt/lfs/ or its subdirectories when I got
to 6.21.
T
Tushar Teredesai wrote:
Does anyone know why these libtool files are useful? I have been
deleting all the .la files without any problems.
I *guess* for libs in /usr/lib they are 'hood ornaments'.
ymmv
--
David Jensen
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www
3.Binutils-2.16
> after 'make tooldir=/usr install'
> sed -i "s:^\(dep.*=\).*:\1' -liberty':" /usr/lib/libbfd.la
>
> 6.14. GCC-3.4.4
> after 'make install'
> sed -i "s:^\(dep.*=\).*:\1' -lm -lc -lgcc_s':" \
>
-liberty':" /usr/lib/libbfd.la
6.14. GCC-3.4.4
after 'make install'
sed -i "s:^\(dep.*=\).*:\1' -lm -lc -lgcc_s':" \
/usr/lib/libstdc++.la /usr/lib/libsupc++.la
All .la's are now nice and clean and I find no problems, I'm happy.
To me
Matthew Burgess wrote:
David Jensen wrote:
I noticed on linking a gtkmm app that the gcc source directory is
listed as a library directory. e.g.
(snip)
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tools
David Jensen wrote:
I noticed on linking a gtkmm app that the gcc source directory is listed
as a library directory. e.g.
(snip)
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tools/build/gcc-build/gcc
This is
I noticed on linking a gtkmm app that the gcc source directory is listed
as a library directory. e.g.
(snip)
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src
-L/tools/build/gcc-build/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tools/build/gcc-build/gcc
(/snip)
I build in /tools
12 matches
Mail list logo
