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:
Davi
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.
Eve
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. However
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 in
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: In
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 in
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 included change: my very first c
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
o
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: c+
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 w
It is broken. I think this is because of the inconsistency of the
options: -nostdlib and -lstdc++.
libtool: link: c++ -fPIC -DPIC -shared -nostdlib /usr/lib/crti.o
/usr/lib/crtbeginS.o .libs/arb.o .libs/basicio.o .libs/bitmap.o
.libs/check_objects.o .libs/diagnostics.o .libs/errors.o
.libs/expor
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 while back. Up till now the linking
step has
12 matches
Mail list logo
