Bug 41845

Summary: /usr/ports/audio/libmikmod fails to compile
Product: Ports & Packages Reporter: Byron L. Hicks <bhicks>
Component: Individual Port(s)Assignee: freebsd-ports (Nobody) <ports>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Byron L. Hicks 2002-08-21 15:10:01 UTC
Making /usr/ports/audio/libmikmod fails with the following:

==>  Building for libmikmod-esound-3.1.10
make  all-recursive
Making all in drivers
Making all in include
Making all in libmikmod
/bin/csh ../libtool --silent --mode=compile cc -DHAVE_CONFIG_H -O -pipe  -D_THREAD_SAFE -I/usr/local/include -finline-functions -funroll-loops -ffast-math -Wall -D_REENTRANT -Dunix -I../include -I.. -I../include -DMIKMOD_H=../include/mikmod.h -c ../drivers/drv_AF.c
Xsed=sed -e s/^X//: Command not found.
Missing }.
*** Error code 1

Stop in /bloodhound3/usr/ports/audio/libmikmod/work/libmikmod-3.1.10/libmikmod.
*** Error code 1

Stop in /bloodhound3/usr/ports/audio/libmikmod/work/libmikmod-3.1.10.
*** Error code 1

Stop in /bloodhound3/usr/ports/audio/libmikmod/work/libmikmod-3.1.10.
*** Error code 1

Stop in /bloodhound3/usr/ports/audio/libmikmod.

Fix: 

unknown
How-To-Repeat: Simply run make from /usr/ports/audio/libmikmod
Comment 1 bjohnson 2002-08-21 21:51:07 UTC
It's because you're using csh as your shell. It's trying to set the
variable Xsed using "Xsed=". Csh and tcsh don't understand that kind of
syntax. The scripts determine your shell from the SHELL environment
variable, so just make sure it's set correctly. Run bash or sh and then
type:

export SHELL=/usr/local/bin/bash

or

export SHELL=/bin/sh

or wherever your shell is.

That should work. Although, if the libtool script is dependent on a Bourne
shell, the configuration script for libmikmod should really specify
/bin/sh instead of just grabbing your SHELL and hoping it's Bourne (for
the few of us out there who still use C shells on occasion).

- Brad Johnson
Comment 2 Byron L. Hicks 2002-08-21 21:56:41 UTC
I don't know if you are the maintainer, if so, bash should be listed as a
requirement on this particular port.

--
Byron L. Hicks
Network Engineer
NMSU ICT

On Wed, 21 Aug 2002, Brad Johnson wrote:

> It's because you're using csh as your shell. It's trying to set the
> variable Xsed using "Xsed=". Csh and tcsh don't understand that kind of
> syntax. The scripts determine your shell from the SHELL environment
> variable, so just make sure it's set correctly. Run bash or sh and then
> type:
>
> export SHELL=/usr/local/bin/bash
>
> or
>
> export SHELL=/bin/sh
>
> or wherever your shell is.
>
> That should work. Although, if the libtool script is dependent on a Bourne
> shell, the configuration script for libmikmod should really specify
> /bin/sh instead of just grabbing your SHELL and hoping it's Bourne (for
> the few of us out there who still use C shells on occasion).
>
> - Brad Johnson
>
Comment 3 bjohnson 2002-08-21 22:26:49 UTC
Nope... according to the Makefile ports@FreeBSD.org is the maintainer and
mharo@area51.fremont.ca.us is the creator. I'm just a fellow BSDuser who
ran into the same problem. But I agree with your suggestion.

- Brad Johnson

On Wed, 21 Aug 2002, Byron L. Hicks wrote:

> I don't know if you are the maintainer, if so, bash should be listed as a
> requirement on this particular port.
> 
> --
> Byron L. Hicks
> Network Engineer
> NMSU ICT
> 
> On Wed, 21 Aug 2002, Brad Johnson wrote:
> 
> > It's because you're using csh as your shell. It's trying to set the
> > variable Xsed using "Xsed=". Csh and tcsh don't understand that kind of
> > syntax. The scripts determine your shell from the SHELL environment
> > variable, so just make sure it's set correctly. Run bash or sh and then
> > type:
> >
> > export SHELL=/usr/local/bin/bash
> >
> > or
> >
> > export SHELL=/bin/sh
> >
> > or wherever your shell is.
> >
> > That should work. Although, if the libtool script is dependent on a Bourne
> > shell, the configuration script for libmikmod should really specify
> > /bin/sh instead of just grabbing your SHELL and hoping it's Bourne (for
> > the few of us out there who still use C shells on occasion).
> >
> > - Brad Johnson
> >
>
Comment 4 Joe Marcus Clarke freebsd_committer freebsd_triage 2002-08-22 05:48:57 UTC
State Changed
From-To: open->closed

The problem should be fixed now with the re-addition of gmake.