On 11-Nov-08, at 6:16 AM, Andy Wingo wrote:
Hi,
I posted a message to bug-libtool that hasn't gotten a response:
http://lists.gnu.org/archive/html/bug-libtool/2008-11/msg00012.html
In short, "libtool --tag=CC --mode=link gcc ... /path/to/libfoo.la"
does
not do the right thing on Mac OS
On 7-Nov-08, at 12:47 PM, Maynard Johnson wrote:
Peter,
I installed the same distro on a 32-bit Intel machine today and got
the same problem. So my hunch that this was a 64bit-only problem
was wrong. To restate the question . . . When only a libbfd.a is
available for linking (i.e., no l
Hello,
i just tried to run the "Hello World" example c++ project in Kdevelop
as i got the output below.
Can anyone support me please and tell me what i did wrong?
If you need more information, please tell me.
Thanks in advance.
Jan
../libtool: line 832: X--tag=CXX: command not found
../libtoo
Hello Jan,
* Jan Leimbach wrote on Tue, Nov 11, 2008 at 10:22:10PM CET:
>
> i just tried to run the "Hello World" example c++ project in Kdevelop
> as i got the output below.
>
> Can anyone support me please and tell me what i did wrong?
You are mixing an ltmain.sh file from Libtool 1.5.x with
Hallo Ralf,
danke für Deine schnelle Antwort.
Da ich recht neu in der Programmierung unter Linux bin, wird mich Deine
Antwort sicher ein paar Tage beschäftigt halten =)
Wünsche Dir einen schönen Abend...
Grüße
Jan
On Tue, Nov 11, 2008 at 10:37 PM, Ralf Wildenhues <[EMAIL PROTECTED]>wrote:
> H
Hi Ralf,
On Tue, Nov 11, 2008 at 1:37 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>
> The macro files may have been copied into your package with 'libtoolize
> --install', or 'aclocal --install', or their contents copied into the
> aclocal.m4 file from aclocal. All of this may have been caused
Hello Dan,
* Dan Nicholson wrote on Tue, Nov 11, 2008 at 10:46:59PM CET:
> On Tue, Nov 11, 2008 at 1:37 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> >
> > The macro files may have been copied into your package with 'libtoolize
> > --install', or 'aclocal --install', or their contents copied in
On Tue, Nov 11, 2008 at 1:49 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello Dan,
>
> * Dan Nicholson wrote on Tue, Nov 11, 2008 at 10:46:59PM CET:
>> On Tue, Nov 11, 2008 at 1:37 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>> >
>> > The macro files may have been copied into your package
Hi,
I posted a message to bug-libtool that hasn't gotten a response:
http://lists.gnu.org/archive/html/bug-libtool/2008-11/msg00012.html
In short, "libtool --tag=CC --mode=link gcc ... /path/to/libfoo.la" does
not do the right thing on Mac OS with libtool 2.2.6a. Can I get
confirmation of th
This is exactly the place, where using Gentoo pays off.
You learn some very unsual things, while you do.
The problem here is KDevelop. It's using autotools
in a such hacky way, that the only sane way to fix it,
is to manually set things up.
It adds a dir, with a lot of old m4 macros, that autore
* Rafał Mużyło wrote on Wed, Nov 12, 2008 at 03:10:36AM CET:
>
> The problem here is KDevelop. It's using autotools
> in a such hacky way, that the only sane way to fix it,
> is to manually set things up.
>
> It adds a dir, with a lot of old m4 macros, that autoreconf
> detects but libtoolize doe
Rafał Mużyło wrote:
The problem here is KDevelop. It's using autotools
in a such hacky way, that the only sane way to fix it,
is to manually set things up.
Is there a good reason not to ship the autotools with
a script to build a template directory? (This probably
belongs on the autoconf list
12 matches
Mail list logo
