On Sun, 24 May 2009, Jan Engelhardt wrote:
It seems like what is needed is C# support in libtool. This should be
discussed on the libtool list.[...]
It's about time GNU comes up with a Mono compiler, similar to gcj.
Then you can have real .so files :)
I think that one of the points of C# is
On Sunday 2009-05-24 19:35, Bob Friesenhahn wrote:
> On Sun, 24 May 2009, Andreas Otto wrote:
>>
>> I want to create an language binding for a "C" libraray
>>
>> this mean I have as input an file called "csmsgque.cs"
>> and get as output an "csmsgque.dll" on unix
>
> It seems like what i
On Sun, 24 May 2009, Andreas Otto wrote:
I want to create an language binding for a "C" libraray
this mean I have as input an file called "csmsgque.cs"
and get as output an "csmsgque.dll" on unix
It seems like what is needed is C# support in libtool. This should be
discusse
Hi,
I want to create an language binding for a "C" libraray
this mean I have as input an file called "csmsgque.cs"
and get as output an "csmsgque.dll" on unix
My current makefile looks like:
=
.dll.cs:
mkdir .libs
Jan Engelhardt writes:
>>needs to use $CC/$CXX anyway.
>
> CCLD/CXXLD.
Which default to $CC/$CXX anyway.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Since I posted about this issue last week, and since GraphicsMagick
has been using a version.sh script with computed version numbers since
late 2002, you can be sure that there is strong support from me for
this proposal. Thanks for describing the issues so succinctly.
Version number and pack
You could use the -m32 compiler argument to ensure the creation of a
32bit binary
Greetings ...
On Sat, 2009-05-23 at 12:49 -0600, John Calcote wrote:
> Hi everyone,
>
> I was wondering what the procedure was for cross-compiling 32-bit apps
> on a 64-bin Linux system? Do you need special libra
On Sun, 24 May 2009, Ralf Wildenhues wrote:
Yes, it is attached. Thank goodness it is so compressable.
Thanks. Can you post the output of the following, done in an empty
directory:
I don't know if you still need this, but this is the output:
echo .foo .
.foo .
echo .foo.log .log.
.foo.log
On Sun, 24 May 2009, Jan Engelhardt wrote:
Bruno wrote:
The -m64 flag is the default on bi-arch Linux systems.
-m64 is the default on where it has been configured so. Just because
your shiny x86_64 install does that, does not mean it is universal.
Oftentimes RISCs, and sparc64 is usually one o
On Sunday 2009-05-24 16:25, Andreas Schwab wrote:
>Bruno Haible writes:
>
>> - The -m64 flag is the default on bi-arch Linux systems.
>
>This is wrong.
>
>> - The -m32 flag has to be passed as part of both CC / CXX and LDFLAGS.
>
>That should not be necessaray, since any command that uses $LD
Hint: ALL my packages derive the version number at
configure time by reading an external file, e.g.
VERSION, xxxrpm.spec or the version repository. Everything
else is being hacked around whatever new pecularities
some autoconf/automake release may have. Whatever lifts
the requirement on hacking is
Bruno Haible writes:
> - The -m32 flag has to be passed as part of both CC / CXX and LDFLAGS.
That should not be necessaray, since any command that uses $LDFLAGS
needs to use $CC/$CXX anyway.
> - The -m64 flag is the default on bi-arch Linux systems.
This is wrong.
Andreas.
--
Andreas S
I've been able to reproduce this issue on GNU/Linux with GNU make 3.80.
Committing this fix (will push out soon).
An easy workaround for this issue is to ensure that the TESTS variable
never contains trailing white space, i.e., the last test should be used
unconditionally on every system.
Thanks
Hello Bruno, Bob,
* Bruno Haible wrote on Sun, May 24, 2009 at 01:12:02PM CEST:
> > - The `silent-rules' option enables Linux kernel-style silent build output.
> >This option requires the widely supported but non-POSIX `make' feature
> >of recursive variable expansion,
>
> We are talking
On Sun, 24 May 2009, Bruno Haible wrote:
- The `silent-rules' option enables Linux kernel-style silent build output.
This option requires the widely supported but non-POSIX `make' feature
of recursive variable expansion,
We are talking about constructs like this:
== Makefile ==
sorry, hit the send key too early.
* Ralf Wildenhues wrote on Sun, May 24, 2009 at 03:20:04PM CEST:
> IRIX make barfs if the inner macro expansion is used without $() or ${}
> even for one-character macros. IOW, IRIX make barfs over $(foo$V) but
> copes with $(foo$(V)).
There are also some make
> what the procedure was for cross-compiling 32-bit apps on a 64-bin Linux
> system?
You need a bi-arch system, that is, one that has the system libraries both in a
64-bit variant and in a 32-bit variant (typically in /lib64 and /lib,
respectively).
For compiling in 32-bit mode, I use
./conf
> - The `silent-rules' option enables Linux kernel-style silent build output.
>This option requires the widely supported but non-POSIX `make' feature
>of recursive variable expansion,
We are talking about constructs like this:
== Makefile ==
all :
echo $(XY_V)
XY_V = $(X
18 matches
Mail list logo
