Alexandre Oliva <[EMAIL PROTECTED]> writes:
> The only way to do it so that it works with both autoconf 2.13 and
> CVS autoconf, without triggering the warning in CVS autoconf, is
> this (from CVS automake's missing.m4):
>
> am_backtick='`'
> AC_MSG_WARN([${am_backtick}$VAR' ...])
Ok, I see
| On Oct 11, 2000, Morten Eriksen <[EMAIL PROTECTED]> wrote:
| > Autoconf straight out of CVS will complain about "backquotes and
| > doublequotes should not be backslashed" when expanding the macro code
| > of _LT_AC_LTCONFIG_HACK libtool.m4.
|
| The problem is that CVS autoconf changes the way
On Oct 12, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> This is s heavy :( As I proposed to Pavel, I'm OK with moving this
> warning from `syntax' to `obsolete' for 2.50, and move it back to
> `syntax' in 2.51 or later.
Probably later :-)
> This way, every body is happy. ?
I'm definit
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> I'm definitely in favor of this change.
OK< I consider this an OK and will apply the change directly.
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/li
Libtoolers,
Here's a fix submitted by our QNX engineer to get our product
(Berkeley DB) to work with QNX dynamic libraries. Without this patch,
libtool conservatively builds only static archives.
Apparently QNX uses GNU ld, so the fix is straightforward.
Thank you for reviewing this and incorpo
Alexandre Oliva wrote:
> ...
> - it makes it harder for someone who finds a problem in ltmain to
> attempt to fix it, since they get (in the final package) someone even
> farther from the original sources
As it stands, they only see the same script they see now.
If they propose a fix, I do not th
On Oct 12, 2000, Bruce Korb <[EMAIL PROTECTED]> wrote:
> If they propose a fix, I do not think it very hard to determine
> which of the lt_*.def files contains the original text.
> The pieces are mostly separated by a " mode$" pattern. :-)
It sounds like we have a volunteer :-) :-)
> 2) Ship b
Alexandre Oliva wrote:
> I doubt it's that much pay back. Also, you have to bear in mind that
> default behaviors of libtool change depending on macros called in
> configure.in and arguments given to configure. So a pre-compiled
> libtool can't be used in general.
As I have the hack configured
On Thu, Oct 12, 2000 at 12:38:11PM +0200, Morten Eriksen wrote:
>
> BTW, I noticed something which looks a bit strange to me. Beginning at
> approximately line 2180 of libtool.m4 (from the head CVS branch),
> there are a lot of shell variables which are set up. But some of them
> are just set to
On Oct 12, 2000, Bruce Korb <[EMAIL PROTECTED]> wrote:
> What branch should I specify?
multi-language-branch
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliv
Alexandre Oliva wrote:
> > Each of these would have an implementation in both C and Bourne shell
> > that would produce identical results.
>
> This will be excellent.
>
> But I guess we should start from the multi-language branch of libtool,
Done. See:
ftp://linuxave.net/pub/ltmain.tgz
___
11 matches
Mail list logo
