This was an awesome explanation. Useful.
However, now I have another issue with kdelibs, also involving an *.la
file: libartskde.la, that I cannot find on my machine. I'll start
another topic, I guess.
Thank you.
AlanOn 12/4/05, Richard Fish <[EMAIL PROTECTED]
> wrote:
On 12/3/05, Alan E. Da
On 12/3/05, Alan E. Davis <[EMAIL PROTECTED]> wrote:
> I'd like to understand how this works. Is there any documentation of all
> this?
The full documentation is "info libtool". Although it is targeted for
application developers, it might be useful to browse. But I'll try to
give a concise expl
I'd like to understand how this works. Is there any documentation
of all this? Meanwhile, as I understand it, because I installed
from a live cd, the libstdc++ libs were i386-pc-linux-gnu
architecture. I used packages from the 2005.1 packages CD, so
perhaps that is where they came from.
I've be
Richard:
After running the command you kindly provided, the emerge -uDv world is proceeding ok. Thank you profusely.
After running the grep command, the following spewed forth from the console:
electrolux # grep libstdc++.la /usr/lib/*la | grep -v "3.4.4/libstdc++.la"
/usr/lib/libdb_cxx-4.2.la:
On 12/3/05, Alan E. Davis <[EMAIL PROTECTED]> wrote:
> So I don't know what was the "old version" to call fix_libtool_files.sh on.
> I know or can find out versions that are currently installed. Is there
> somewhere for me to find out which versions I need to run this script on?
The gcc directo
In spite of the excellent explanation, I am still at sea with this
issue. I apologize if "top-posting" is an etiquette
issue. Then I suppose I ought to trim this message down.
More down there V.On 12/4/05,
Richard Fish <
[EMAIL PROTECTED]> wrote:
It is because the .la file for whatever librari
Thank you for the clear explanation.
AlanOn 12/4/05, Richard Fish <[EMAIL PROTECTED]> wrote:
On 12/3/05, Alan E. Davis <[EMAIL PROTECTED]> wrote:> That's bizaare. I don't know yet whether it worked. It is a bit worrisome> to have to remember what version of a program WAS installed, to configure
On 12/3/05, Alan E. Davis <[EMAIL PROTECTED]> wrote:
> That's bizaare. I don't know yet whether it worked. It is a bit worrisome
> to have to remember what version of a program WAS installed, to configure it
> for the here and now. Let's see whether it worked. I was more concerned it
> is looki
I usually do a emerge -p to see what is currently
installed. Like this:
> [EMAIL PROTECTED] / # emerge -pv openoffice
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies ...done!
> [ebuild R ] app-office/openoffice-2.0.0 +curl -eds* +gnome +gtk
> +java +kde
That's bizaare. I don't know yet whether it worked. It is a
bit worrisome to have to remember what version of a program WAS
installed, to configure it for the here and now. Let's see
whether it worked. I was more concerned it is looking for
i386-pc-linux-gnu. Was that because the compiler had
Alan E. Davis wrote:
> The following error reflects one that has happened several times
> recently with some different ebuilds. On my system is found
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la
>
> What steps can I take to complete the emerge of gnome-vfs that has
> stopped with
11 matches
Mail list logo
