Ciao Stefano!
Le 2 juil. 2012 à 09:44, Stefano Lattarini a écrit :
Hi Akim,
On 07/02/2012 09:20 AM, Akim Demaille wrote:
Le 30 juin 2012 à 23:11, Stefano Lattarini a écrit :
Its tests are hopelessly failing now, it is complex to debug (and I'm
too ignorant about its aims and its
Hi Akim,
On 07/02/2012 09:20 AM, Akim Demaille wrote:
Le 30 juin 2012 à 23:11, Stefano Lattarini a écrit :
Its tests are hopelessly failing now, it is complex to debug (and I'm
too ignorant about its aims and its implementation to do so), and anyway
it should probably be rewritten to take
Its tests are hopelessly failing now, it is complex to debug (and I'm
too ignorant about its aims and its implementation to do so), and anyway
it should probably be rewritten to take better advantage of GNU make and
Automake-NG features. So let's drop it for now, to avoid slowing down
the
I just came across the multilib section of the automake manual:
http://www.gnu.org/software/automake/manual/automake.html#Multilibs
How can I find the status on this? How experimental is experimental?
of the multilib support. Sorry I can't help you
with that at all.
Cheers,
Ralf
Hello,
On Fri, Sep 22, 2006 at 10:54:20PM +0800, Tzu-Chien Chiu wrote:
2006/9/22, Stepan Kasal [EMAIL PROTECTED]:
But this does not mean tha BUILD_CC has to be set!
If BUILD_CC is empty, this just makes CC empty. AC_PROG_CC then does
its work. (The variable CC overrides the test only if it
Hello,
On Thu, Sep 21, 2006 at 04:34:35PM +0200, Ralf Corsepius wrote:
On Thu, 2006-09-21 at 21:36 +0800, Tzu-Chien Chiu wrote:
I've read configure.ac and Makefile.am of texinfo. Here is how it works.
[...]
I'm afraid you have not understood the trick.
Perhaps you could try to cross-compile
2006/9/22, Stepan Kasal [EMAIL PROTECTED]:
But this does not mean tha BUILD_CC has to be set!
If BUILD_CC is empty, this just makes CC empty. AC_PROG_CC then does
its work. (The variable CC overrides the test only if it is nonempty.)
1. I understand, but under which circumstances native
On Tue, 2006-08-08 at 20:18 +0800, Tzu-Chien Chiu wrote:
Hello, Ralf.
I found gcc and newlib don't use AM_ENABLE_MULTILIB, instead
TARGET_SUBDIR is set.
Pardon, they (and binutils) use it.
AM_ENABLE_MULTILIB is used in library subdir configure scripts
(*/configure.[ac|in]), not inside of
Hello,
Ralf Corsepius has answered the question about AM_ENABLE_MULTILIB,
and then, on Thu, Sep 21, 2006 at 09:52:25AM +0200, he wrote:
I need to build *both* the native and the cross-compiled library
at the same time (one-time configure script and make), rather than
*either one* of
Thank you. You're right. It has nothing to do with multilib.
I've read configure.ac and Makefile.am of texinfo. Here is how it works.
When cross-compiling, the same configure script is run twice for all
sub-directories of source directory. Makefile.am, however, selectively only
builds some or
On Thu, 2006-09-21 at 21:36 +0800, Tzu-Chien Chiu wrote:
Thank you. You're right. It has nothing to do with multilib.
I've read configure.ac and Makefile.am of texinfo.
I am not familiar with texinfo's sources
Here is how it works.
When cross-compiling, the same configure script is run
Hello Tzu-Chien,
* Tzu-Chien Chiu wrote on Tue, Aug 08, 2006 at 11:37:41AM CEST:
I need to build a native library and a cross-compiled libarary from
the same set of source files, but I don't find any method to specify
per-target compiler.
I read the manual and guessed that
Hello, Ralf.
I found gcc and newlib don't use AM_ENABLE_MULTILIB, instead
TARGET_SUBDIR is set.
ChangeLog (gcc 3.4.4):
Thu Jun 19 14:16:42 1997 Brendan Kehoe [EMAIL PROTECTED]
* configure.in: Don't set ENABLE_MULTILIB, so we'll be passing
--enable-multilib down to subdirs;
Hello,
On Tue, Aug 08, 2006 at 08:18:32PM +0800, Tzu-Chien Chiu wrote:
I need to build *both* the native and the cross-compiled library
at the same time (one-time configure script and make), rather than
*either one* of them.
FWIIW, the Texinfo configure does this: if a cross compile build is
15 matches
Mail list logo