Re: [Chicken-users] Bugs in documentation and Mac OS X 10.6.8 executable generation broken

2011-12-05 Thread Watson Ladd
On Mon, Dec 5, 2011 at 9:22 AM, Mario Domenech Goulart
 wrote:
> Hi Watson,
>
> On Mon, 5 Dec 2011 08:52:06 -0600 Watson Ladd  wrote:
>
>> csi has it for making scripts run. This could simply be a case of me
>> assuming that the interpreter and compiler took similar options, which
>> is likely. So now i see what happens: csc takes the -ss switch and
>> interprets it as -s, which causes the result.
>>
>> So what is the correct way to compile an SRFI-22 compliant script to
>> an executable?
>
> I'm not sure I understand your question.  Usually it's just a matter of
>
>    $ csc your-program.scm
>
> A binary executable file called `your-program' will be generated.

So that works: I get an executable. But the executable does nothing
but take up time when run. I've got a SRFI-22 compliant script: that
is I want the executable to evaluate (main argslist) where argslist is
a list containing strings corresponding to the entries of the argv
vector. The interpreter has a flag for this: the compiler doesn't seem
to. Do I need to put in a toplevel expression, and if so, which one?
Thanks for taking the time to answer my questions: I'm reasonably
experienced with scheme, but recently needed to turn some scheme into
something that can run on systems with only a C compiler.
>
>
> Best wishes.
> Mario
> --
> http://parenteses.org/mario

Sincerely,
Watson Ladd



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Bugs in documentation and Mac OS X 10.6.8 executable generation broken

2011-12-05 Thread Watson Ladd
csi has it for making scripts run. This could simply be a case of me
assuming that the interpreter and compiler took similar options, which
is likely. So now i see what happens: csc takes the -ss switch and
interprets it as -s, which causes the result.

So what is the correct way to compile an SRFI-22 compliant script to
an executable?
Sincerely,
Watson Ladd

On Mon, Dec 5, 2011 at 4:50 AM, Christian Kellermann
 wrote:
> Hello Watson,
>
> * Watson Ladd  [111205 11:32]:
>
>> man csc suggests sending bug reports to chicken-janit...@nongnu.org. I
>> did so, and received a message back indicating it was bounced as I was
>> not a subscriber. i
>
>> csc has no comprehensive listing of options. And
>> lastly, the bug that started this entire exercise, on Mac OS X csc -ss
>> generates a Mach O bundle, not an executable.
>
> csc -h produces this list for me, a detailed description might be
> found in the manual or on the online copy: http://api.call-cc.org/doc/csc
>
> From your description I am not able to guess what you want to do.
>
> To generate a "normal" executable with chicken from a scheme file
> called "foo.scm" one would call csc like this:
>
> $ csc foo.scm
>
> to generate a binary "foo".
>
> The -s switch is used to generate shared objects, usually used when
> compiling modules as extensions. See
> http://api.call-cc.org/doc/chicken/eggs for details on those.
>
> I am not sure where you got the "-ss" switch from, where did you
> find that and what did you intend to do?
>
> Kind regards,
>
> Christian
>
> --
> Who can (make) the muddy water (clear)? Let it be still, and it will
> gradually become clear. Who can secure the condition of rest? Let
> movement go on, and the condition of rest will gradually arise.
>  -- Lao Tse.



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


[Chicken-users] Bugs in documentation and Mac OS X 10.6.8 executable generation broken

2011-12-05 Thread Watson Ladd
Dear Chicken Users,
man csc suggests sending bug reports to chicken-janit...@nongnu.org. I
did so, and received a message back indicating it was bounced as I was
not a subscriber. csc has no comprehensive listing of options. And
lastly, the bug that started this entire exercise, on Mac OS X csc -ss
generates a Mach O bundle, not an executable.
Sincerely,
Watson Ladd

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users