[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] Always regenerate import libraries in setu

From: kooda
Subject: Re: [Chicken-hackers] [PATCH] Always regenerate import libraries in setup-mode
Date: Wed, 29 May 2019 11:39:11 +0200
User-agent: OtterMail

address@hidden wrote:
> > On 2019-05-07  7:45, Evan Hanson wrote:
> > > On 2019-05-06 13:04, address@hidden wrote:
> > > > I don't think that patch is right. If you emit import libraries from the
> > > > static builds, you will not be able to import modules from the evaluator
> > > > when the modules are statically linked, because the module registration
> > > > code is taken out.
> > > 
> > > Oh, of course, you're right. I suppose the bug is really that the build
> > > script tries to compile these files, then, and not that they aren't
> > > emitted?
> > 
> > No, that's not right either. It's a combination of the two: if they're
> > not emitted, there's no file to install and separate compilation is
> > impossible, but if they *are* emitted then they're removed from the
> > compiled artifacts and ipmort-in-eval fails (as you point out).
> > 
> > I wonder... For static-only extensions, do we perhaps need to add a call
> > to csc with "-analyze-only" just to produce the import libraries? And in
> > the meantime, should we "undocument" the static option for "linkage"
> > with something like the attached?
> I dunno, this somehow defeats the purpose of the linkage property.
> I think it is better to change the behaviour to do the right thing instead
> of defining an switch that has just a single option.

Should we fix this for 5.1?

In any case we should probably open a ticket to keep track of that issue.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]