freeBSD chicken port

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

freeBSD chicken port

Duke Normandin
Hi all ..

Just installed freeBSD on an old AMD Athlon box. My first *nix love
works like a hot damn. :)

Installed freeBSD pkg Chicken5-5.2.0 - no problems.
However, getting it run afterwards took me 1/2 hour.
I tried:
chicken; man 1 chicken; csi; man 1 csi; csc etc etc
NO JOY!
Until out of frustration, I tried chicken5; csi5; man 1 csi5 etc

JOY!!

I was lucky to trip over that solution! Can that be fixed for
the next poor slob that tries to run Chicken on freeBSD?
I take it that there is a new freeBSD Chicken port maintainer?

Thanks!
--
Duke

Reply | Threaded
Open this post in threaded view
|

Re: freeBSD chicken port

paul wisehart
On Thu, Jan 14, 2021 at 07:11:36PM -0700, Duke Normandin wrote:
> ...
> However, getting it run afterwards took me 1/2 hour.
> I tried:
> chicken; man 1 chicken; csi; man 1 csi; csc etc etc
> NO JOY!
> Until out of frustration, I tried chicken5; csi5; man 1 csi5 etc

Hi!,
Next time try this:
pkg info | grep -i chicken
> chicken5-5.2.0                 Scheme-to-C compiler

Now you know it's called chicken5, so do this:
pkg info -l chicken5

chicken5-5.2.0:
        /usr/local/bin/chicken-do5
        /usr/local/bin/chicken-install5
        /usr/local/bin/chicken-profile5
        /usr/local/bin/chicken-status5
        /usr/local/bin/chicken-uninstall5
        /usr/local/bin/chicken5
        /usr/local/bin/csc5
        /usr/local/bin/csi5
        /usr/local/include/chicken5/chicken-config.h
        /usr/local/include/chicken5/chicken.h
        /usr/local/lib/chicken5/11/chicken.base.import.so
        /usr/local/lib/chicken5/11/chicken.bitwise.import.so
        /usr/local/lib/chicken5/11/chicken.blob.import.so
        /usr/local/lib/chicken5/11/chicken.compiler.user-pass.import.so
        /usr/local/lib/chicken5/11/chicken.condition.import.so
<snipped>

You can see the binaries in /usr/local/bin.
chicken5 csc5 and csi5.
You can generalize begin using most FreeBSD packages.


Reply | Threaded
Open this post in threaded view
|

Re: freeBSD chicken port

Duke Normandin
On Thu, 14 Jan 2021 22:31:28 -0500
Paul Wisehart wrote:

[snip]

> You can see the binaries in /usr/local/bin.
> chicken5 csc5 and csi5.
> You can generalize begin using most FreeBSD packages.

I discovered all of that already! But WHY change from csc and csi
to csc5 and csi5? So next next Chicken upgrade will be csc6 and
csi6? Why this complication? Thanks for your input!
--
Duke

Reply | Threaded
Open this post in threaded view
|

Re: freeBSD chicken port

Peter Bex
On Thu, Jan 14, 2021 at 08:42:04PM -0700, Duke Normandin wrote:
> > You can see the binaries in /usr/local/bin.
> > chicken5 csc5 and csi5.
> > You can generalize begin using most FreeBSD packages.
>
> I discovered all of that already! But WHY change from csc and csi
> to csc5 and csi5? So next next Chicken upgrade will be csc6 and
> csi6? Why this complication? Thanks for your input!

Presumably they did this so you can install CHICKEN 4 and 5 alongside.
This is also commonly done by package maintainers for Python 2 and 3,
Perl 4 and 5, and Ruby as well I think.

Given that this is Ports, maybe there's an option you can set during
build to not do that?

Cheers,
Peter

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: freeBSD chicken port

paul wisehart
In reply to this post by Duke Normandin
On Thu, Jan 14, 2021 at 08:42:04PM -0700, Duke Normandin wrote:

> On Thu, 14 Jan 2021 22:31:28 -0500
> Paul Wisehart wrote:
>
> [snip]
>
> > You can see the binaries in /usr/local/bin.
> > chicken5 csc5 and csi5.
> > You can generalize begin using most FreeBSD packages.
>
> I discovered all of that already! But WHY change from csc and csi
> to csc5 and csi5? So next next Chicken upgrade will be csc6 and
> csi6? Why this complication? Thanks for your input!

The real answer would be from the FreeBSD package maintainer.
My point with finding out the binaries is I was trying to
"teach you to fish".  This is very typical to have different
names for binaries, especially if there are diff versions
installed simultaneously.

If develop good first princicples this stuff won't phaze you,
and you won't care what the names are.