Bug 75193

Summary: asterisk build on 5.3: work around tr bug (VI_ZERO)
Product: Ports & Packages Reporter: Stuart Barkley <stuartb>
Component: Individual Port(s)Assignee: Maxim Sobolev <sobomax>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff
none
patch-editline_makelist none

Description Stuart Barkley 2004-12-17 17:40:23 UTC 
Building net/asterisk on FreeBSD 5.3-RELEASE fails with error:

map.c:682: error: `VI_ZERO' undeclared here (not in a function)

How-To-Repeat: cd /usr/ports/net/asterisk
make
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2004-12-17 23:02:43 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->	 sobomax

Over to maintainer
Comment 2 Maxim Sobolev 2005-01-09 10:36:37 UTC 
I can't reproduce the problem. Are you sure that it is not elsewhere?

-Maxim
Comment 3 Volker Stolz freebsd_committer freebsd_triage 2005-04-14 14:28:01 UTC 
State Changed
From-To: open->feedback

Ping submitter a last time for feedback
Comment 4 Stuart Barkley 2005-04-14 15:11:18 UTC 
I still see this problem with the latest ports version of net/asterisk
(1.0.7).

I believe it is actually a problem with /usr/bin/tr which the asterisk
build is triggering.

    % ls -l /usr/bin/tr
    -r-xr-xr-x  1 root  wheel  16552 Nov  4 20:26 /usr/bin/tr
    % md5  /usr/bin/tr
    MD5 (/usr/bin/tr) = a6f3311e6874911ca0cda8b8240517a3
    % echo abcxyz | /usr/bin/tr "[a-z]" "[A-Z]"
    ABCXY]
    % uname -a
    FreeBSD delphi-5.4gh.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Wed Mar  2 14:41:17 EST 2005     stuartb@delphi-5.4gh.net:/usr/src/sys/i386/compile/4GH  i386
    %

I'm building asterisk with:

    % make -DWITHOUT_H323

I have verified the tr command above fails on several different
installations of 5.3-RELEASE.  And previously verified that tr failed
on -STABLE and -CURRNET but don't have access to those build
enviroments at this moment.

Is it possible a different version of tr is being used by others?
Comment 5 Stuart Barkley 2005-04-14 15:44:44 UTC 
Opps, I found my problem.  I had

    LANG=en_US.ISO8859-1

set in my environment.  This changes the behavior of /usr/bin/tr as
indicated in tr(1) under COMPATIBILITY .
Comment 6 Sam Lawrance 2005-05-16 04:28:30 UTC 
The tr manpage suggests using

	tr "[:lower:]" "[:upper:]"

which works correctly in all locales, unlike "[a-z]" "[A-Z]".
Comment 7 Maxim Sobolev freebsd_committer freebsd_triage 2005-06-19 13:51:30 UTC 
State Changed
From-To: feedback->closed

Committed, thank you!