Phil,
I've now added -lpolymain to polyml.pc.in so that should handle your
specific problem. Can you check it? I'd be happy if you could produce
an improved version of this. It's not something I use or have any
familiarity with.
Regards,
David
On 19/12/2017 21:47, Phil Clayton wrote:
David,
I think I would expect `pkg-config --libs polyml` to provide the linker
flags required to create an executable, i.e. I wouldn't expect to have
to specify -lpolymain additionally. I can't think of any other use
cases of pkg-config because Poly/ML can't be used to produce a library.
Phil,
I'm not exactly clear how pkg-config is supposed to be used. It's
certainly possible to add -lpolymain explicitly to the libraries in
polyml.pc.
David
On 17/12/2017 21:57, Phil Clayton wrote:
David,
On Fedora 25, polyc still appears to work for shared poly with this
change.
On 15/12/2017 18:41, Makarius wrote:
On 15/12/17 17:46, David Matthews wrote:
On 15/12/2017 16:15, Makarius wrote:
* The polyc script cannot handle directory names with spaces, e.g. the
main "prefix".
I guess it would need some extra quotation. Do you want to propose a fix?
See the
David,
On Fedora 25, polyc still appears to work for shared poly with this
change. However, there is an issue for pkg-config because the libs
section in polyml.pc no longer includes the flag -lpolymain causing a
link error:
/usr/lib/gcc/x86_64-redhat-linux/6.4.1/../../../../lib64/crt1.o:
On 15/12/2017 18:41, Makarius wrote:
On 15/12/17 17:46, David Matthews wrote:
On 15/12/2017 16:15, Makarius wrote:
* The polyc script cannot handle directory names with spaces, e.g. the
main "prefix".
I guess it would need some extra quotation. Do you want to propose a fix?
See the
On 15/12/2017 16:15, Makarius wrote:
On 12/12/17 14:14, David Matthews wrote:
The polyc script has been developed mainly to simplify the linking of an
exported ML function and in particular to try to capture the libraries
that need to be included. I've been having another look at this because
There seems to be a problem with building it as a shared library in
FreeBSD. It seems to work fine with
./configure --disable-shared
David
On 15/12/2017 12:58, Kostirya wrote:
It is broken. I think this is because of the inconsistency of the
options: -nostdlib and -lstdc++.
libtool: link:
On 12/12/17 14:14, David Matthews wrote:
> The polyc script has been developed mainly to simplify the linking of an
> exported ML function and in particular to try to capture the libraries
> that need to be included. I've been having another look at this because
> of an issue that was reported a
23/09/15 03:11, Michael Norrish wrote:
Or is there another way of getting what I need? I'd like to dispense with
explicit calls in our own code to PolyML.export, and then needing to call the
linker, but we do want to be able to build heaps in this way, layer by layer.
Have you looked at
Hi Phil,
I've changed configure so that FFI_LIBS gets added to LIBS within the
configure script. This should avoid the need to add it explicitly in
other places. Let me know if there are problems.
David
On 23/03/2015 23:45, Phil Clayton wrote:
Hi David,
15/10/13 17:50, David Matthews
Hi David,
Thanks - I've tried building an application with r1985 in the following
configurations and pkg-config is working now:
static, non-system libffi
static, system libffi
shared, non-system libffi
shared, system libffi
Phil
24/03/15 12:01, David Matthews wrote:
Hi Phil,
I've
On 6 May 2014, at 12:56, David Matthews david.matth...@prolingua.co.uk wrote:
Hi Rob,
I've been away and I'm now just trying to catch up.
On 23/04/2014 17:13, Rob Arthan wrote:
I have a couple of comments and a query about polyc (which seemed
particularly attractive
on Cygwin, where
Hi Rob,
I've been away and I'm now just trying to catch up.
On 23/04/2014 17:13, Rob Arthan wrote:
I have a couple of comments and a query about polyc (which seemed particularly
attractive
on Cygwin, where there seems to be quite a long list of libraries you need to
know
about if you are
Hi Rob,
23/04/14 17:13, Rob Arthan wrote:
The query relates to the fact that polyc doesn’t do anything with
LD_RUN_PATH
(or DYLD_LIBRARY_PATH on Mac OS). Am I right in thinking that libpolyml
will now always be statically linked so that you no longer to need to
tell the
dynamic linker where to
On Wed, 23 Apr 2014, Rob Arthan wrote:
The query relates to the fact that polyc doesn’t do anything with
LD_RUN_PATH (or DYLD_LIBRARY_PATH on Mac OS). Am I right in thinking
that libpolyml will now always be statically linked so that you no
longer to need to tell the dynamic linker where to
Am 11.10.2013 15:42, schrieb David Matthews:
On 11/10/2013 14:17, René Neumann wrote:
Am 11.10.2013 15:12, schrieb Ramana Kumar:
(Ie, what I want: if is_script then main() else () )
If your main : unit - unit (which perhaps it must be?), then main() is
equivalent to the if expression above,
(Ie, what I want: if is_script then main() else () )
If your main : unit - unit (which perhaps it must be?), then main() is
equivalent to the if expression above, modulo side-effects.
Thanks,
René
--
René Neumann
Institut für Informatik (I7)
Technische Universität München
Boltzmannstr.
Am 11.10.2013 15:12, schrieb Ramana Kumar:
(Ie, what I want: if is_script then main() else () )
If your main : unit - unit (which perhaps it must be?), then main() is
equivalent to the if expression above, modulo side-effects.
There is a misunderstanding here: I need the main to be run with
On 11/10/2013 14:17, René Neumann wrote:
Am 11.10.2013 15:12, schrieb Ramana Kumar:
(Ie, what I want: if is_script then main() else () )
If your main : unit - unit (which perhaps it must be?), then main() is
equivalent to the if expression above, modulo side-effects.
There is a
20 matches
Mail list logo
