FreeBSD unmaintained ports which are currently marked broken

2011-10-07 Thread linimon
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   audio/fmit
broken because: does not configure
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/fmit-0.99.2.log
 (_Sep__8_01:25:02_UTC_2011)
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20110718073617/fmit-0.97.7_6.log
 (_Jul_31_06:20:01_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=fmit


portname:   audio/linux-shoutcast
broken because: unfetchable; website rearranged
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-shoutcast


portname:   audio/shoutcast
broken because: unfetchable; website rearranged
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=shoutcast


portname:   chinese/scim-chewing
broken because: does not configure
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=scim-chewing


portname:   databases/kpogre
broken because: does not compile
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20110914141638/kpogre-1.8.2_3.log
 (_Sep_17_09:27:37_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=kpogre


portname:   databases/xbase
broken because: Does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=xbase


portname:   deskutils/gemcal
broken because: Does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=gemcal


portname:   deskutils/mhc
broken because: Does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=mhc


portname:   deskutils/org-mode.el6
broken because: Does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=org-mode.el6


portname:   devel/erlang-thrift
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=erlang-thrift


portname:   devel/fampp
broken because: FAM system mismatch: gamin is installed, while desired
FAM system is fam
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=fampp


portname:   devel/gccxml
broken because: does not compile
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/gccxml-0.6.0.log
 (_Sep__7_21:41:48_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gccxml


portname:   devel/gcvs
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gcvs


portname:   devel/linux-js
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-js


portname:   devel/linuxthreads
broken because: 

FreeBSD ports which are currently marked broken

2011-10-07 Thread linimon
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   archivers/dact
broken because: needs to be upgraded to lzo2 according to ports/156954
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=dact


portname:   audio/aacplusenc
broken because: unfetchable
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20110927213040/aacplusenc-0.17.1.log
 (_Jul__8_13:10:29_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=aacplusenc


portname:   audio/aureal-kmod
broken because: doesn't build on RELENG_8
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=aureal-kmod


portname:   audio/fmit
broken because: does not configure
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/fmit-0.99.2.log
 (_Sep__8_01:25:02_UTC_2011)
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20110718073617/fmit-0.97.7_6.log
 (_Jul_31_06:20:01_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=fmit


portname:   audio/gstreamer-plugins-flite
broken because: Doesn't work due to link problem in audio/flite
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gstreamer-plugins-flite


portname:   audio/linux-shoutcast
broken because: unfetchable; website rearranged
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-shoutcast


portname:   audio/muine
broken because: does not compile
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20110923204408/muine-0.8.11_7.log
 (_Sep_24_09:19:54_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=muine


portname:   audio/rubyripper
broken because: does not package
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/rubyripper-0.6.0_1.log
 (_Sep__7_22:32:07_UTC_2011)
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20110918085203/rubyripper-0.6.0_1.log
 (_Sep_20_23:32:51_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=rubyripper


portname:   audio/shoutcast
broken because: unfetchable; website rearranged
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=shoutcast


portname:   benchmarks/polygraph
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph


portname:   benchmarks/polygraph31
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31


portname:   cad/salome-gui
broken because: does not compile
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20110923204408/salome-gui-5.1.4_3.log
 (_Sep_24_23:44:04_UTC_2011)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-gui


portname:   chinese/cxterm
broken because: 

FreeBSD unmaintained ports which are currently scheduled for deletion

2011-10-07 Thread linimon
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/bsdar
description:BSD-licensed replacement of the ar utility
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: part of the base system
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=bsdar


portname:   astro/gkrellsun
description:A Gkrellm-Plugin that displays the local sun rise and
sun set times
maintainer: po...@freebsd.org
deprecated because: Abandonware
expiration date:2011-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astroportname=gkrellsun


portname:   astro/weatherget
description:Command-line weather reporting tool
maintainer: po...@freebsd.org
deprecated because: Broken b/c of weather.com new licensing rules not
agreed by author
expiration date:2011-11-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astroportname=weatherget


portname:   astro/xrmap
description:Map portions of the earth from a given
longitude/latitude
maintainer: po...@freebsd.org
deprecated because: No more distfiles
expiration date:2011-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=astroportname=xrmap


portname:   audio/gkrellmss
description:A plugin for GKrellM with a VU meter showing
left/right channel audio
maintainer: po...@freebsd.org
deprecated because: Abandonware
expiration date:2011-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gkrellmss


portname:   audio/gnapster
description:GNOME client for the online mp3 community called
napster
maintainer: po...@freebsd.org
deprecated because: Abandonware
expiration date:2011-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gnapster


portname:   audio/linux-shoutcast
description:Nullsoft's streaming audio server (Linux binary port)
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable; website rearranged
expiration date:2011-10-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-shoutcast


portname:   audio/midimountain
description:MIDI sequencer
maintainer: po...@freebsd.org
deprecated because: Abandonware
expiration date:2011-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=midimountain


portname:   audio/py-taglib
description:Python bindings for the taglib audio file tagging
library
maintainer: po...@freebsd.org
deprecated because: Only compatible with Python 2.4. Please use
audio/py-tagpy instead
expiration date:2011-12-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-taglib


portname:   audio/shoutcast
description:Nullsoft's streaming audio server (binary port)
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: unfetchable; website rearranged
expiration date:2011-10-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=shoutcast


portname:   converters/py-cjkcodecs
description:Python Unicode Codecs for Chinese, Japanese and Korean
encodings
maintainer: po...@freebsd.org
deprecated because: Integrated into every python version in the tree
expiration date:2011-11-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=convertersportname=py-cjkcodecs


portname:   databases/postgresql-plpython
description:A module for using Python to write SQL functions
maintainer: 

FreeBSD ports which are currently marked forbidden

2011-10-07 Thread linimon
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   archivers/pecl-phar
forbidden because:  Vulnerable since 2011-01-13,

http://portaudit.freebsd.org/da3d381b-0ee6-11e0-becc-0022156e8794.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=pecl-phar


portname:   databases/gnats
forbidden because:  Security issues
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gnats


portname:   databases/mysql323-client
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql323-client


portname:   databases/mysql323-scripts
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql323-scripts


portname:   databases/mysql323-server
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql323-server


portname:   databases/mysql40-client
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql40-client


portname:   databases/mysql40-scripts
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql40-scripts


portname:   databases/mysql40-server
forbidden because:  Vulnerable since 2006-10-29,

http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=mysql40-server


portname:   devel/libsoup22
forbidden because:  Vulnerable since 2011-07-28,

http://portaudit.freebsd.org/30cb4522-b94d-11e0-8182-485d60cb5385.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libsoup22


portname:   dns/bind9-sdb-ldap
forbidden because:  Vulnerable since 2011-06-04,

http://portaudit.freebsd.org/1e1421f0-8d6f-11e0-89b4-001ec9578670.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=bind9-sdb-ldap


portname:   dns/bind9-sdb-postgresql
forbidden because:  Vulnerable since 2011-06-04,

http://portaudit.freebsd.org/1e1421f0-8d6f-11e0-89b4-001ec9578670.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=dnsportname=bind9-sdb-postgresql


portname:   ftp/wgetpro
forbidden because:  Vulnerable since 2004-12-14,

http://portaudit.freebsd.org/06f142ff-4df3-11d9-a9e7-0001020eed82.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=ftpportname=wgetpro


portname:   games/quake2forge
forbidden because:  Vulnerable since 2005-01-21,

http://portaudit.freebsd.org/2c25e762-6bb9-11d9-93db-000a95bc6fae.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=gamesportname=quake2forge


portname:   graphics/linux-tiff
forbidden because:  Vulnerable since 2004-10-13,

http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff


portname:   japanese/mutt
forbidden because:  Vulnerable since 2007-07-29,

http://portaudit.freebsd.org/863f95d3-3df1-11dc-b3d3-0016179b2dd5.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=mutt


portname:   net-mgmt/nagios2
forbidden because: 

audio/cdparanoia broken on -CURRENT, and probably on 9.0

2011-10-07 Thread b. f.
Just a note to say that recent changes on -CURRENT (r225950, meaning
that it is probably broken on 9.0 after r226067) have broken
audio/cdparanoia, and it should be fixed or marked as BROKEN there.  I
haven't filed a PR, or attempted to patch it yet -- I think that it
would be worthwhile to look into moving to 10.2, which has a large
number of improvements, although suffering from some Linuxisms.

Regards,
b.


===   cdparanoia-3.9.8_9 depends on executable: gmake - found
===  Configuring for cdparanoia-3.9.8_9
creating cache ./config.cache
checking host system type... Invalid configuration
`amd64-portbld-freebsd9.9': machine `amd64-portbld' not recognized

checking for ranlib... ranlib
checking for ar... ar
checking for install... /usr/bin/install -c -o root -g wheel
checking how to run the C preprocessor... cpp
checking for ANSI C header files... yes
checking size of short... 2
checking size of int... 4
checking size of long... 8
checking size of long long... 8
checking for int16_t... yes
checking for int32_t... yes
checking for u_int16_t... yes
checking for u_int32_t... yes
checking for linux/sbpcd.h... no
checking for linux/ucdrom.h... no
checking whether gmake sets ${MAKE}... yes
checking for working const... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating interface/Makefile
creating paranoia/Makefile
===  Building for cdparanoia-3.9.8_9
cd interface  gmake all
gmake[1]: Entering directory
`/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake libcdda_interface.a CFLAGS=-O -O2 -pipe -march=athlon64
-fno-strict-aliasing
gmake[2]: Entering directory
`/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c scan_devices.c
cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c common_interface.c
cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c cooked_interface.c
cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c interface.c
cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c scsi_interface.c
scsi_interface.c: In function 'handle_scsi_cmd':
scsi_interface.c:370: error: 'struct scsi_sense_data' has no member
named 'flags'
scsi_interface.c:381: error: 'struct scsi_sense_data' has no member
named 'add_sense_code'
scsi_interface.c:382: error: 'struct scsi_sense_data' has no member
named 'add_sense_code_qual'
scsi_interface.c: In function 'scsi_read_map':
scsi_interface.c:967: error: 'struct scsi_sense_data' has no member
named 'flags'
scsi_interface.c:968: error: 'struct scsi_sense_data' has no member
named 'add_sense_code'
scsi_interface.c:969: error: 'struct scsi_sense_data' has no member
named 'add_sense_code_qual'
gmake[2]: *** [scsi_interface.o] Error 1
gmake[2]: Leaving directory
`/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
gmake: *** [all] Error 2
*** Error code 1

Stop in /home/u1/pwrk/ports/audio/cdparanoia.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


[HEADSUP]: ports feature freeze starts soon

2011-10-07 Thread Erwin Lansing
In preparation for 9.0 the ports tree will be in feature freeze
after release candidate 1 (RC2)is released, currently planned for
October 17.

If you have any commits with high impact planned, get them in the tree
before then and if they require an experimental build, have a request
for one in portmgr hands within the next few days.

Note that this again will be a feature freeze and not a full freeze.
Normal upgrade, new ports, and changes that only affect other branches
will be allowed without prior approval but with the extra
Feature safe: yes tag in the commit message.  Any commit that is sweeping,
i.e. touches a large number of ports, infrastructural changes, commts to
ports with unusually high number of dependencies, and any other commit
that requires the rebuilding of many packages will not be allowed
without prior explicit approval from portmgr after that date.

-erwin

-- 
Erwin Lansing   http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0

2011-10-07 Thread Kenneth D. Merry
On Fri, Oct 07, 2011 at 06:11:13 -0600, Kenneth D. Merry wrote:
 On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote:
  Just a note to say that recent changes on -CURRENT (r225950, meaning
  that it is probably broken on 9.0 after r226067) have broken
  audio/cdparanoia, and it should be fixed or marked as BROKEN there.  I
  haven't filed a PR, or attempted to patch it yet -- I think that it
  would be worthwhile to look into moving to 10.2, which has a large
  number of improvements, although suffering from some Linuxisms.
 
 This will be easy to patch, using one of two methods:
 
  - change struct scsi_sense_data to struct scsi_sense_data_fixed
 or, better yet:
  - use scsi_extract_sense_len(), which will work for fixed or descriptor
sense.

I should have also mentioned that this should be dependent on CAM_VERSION
= 0x16.

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0

2011-10-07 Thread Kenneth D. Merry
On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote:
 Just a note to say that recent changes on -CURRENT (r225950, meaning
 that it is probably broken on 9.0 after r226067) have broken
 audio/cdparanoia, and it should be fixed or marked as BROKEN there.  I
 haven't filed a PR, or attempted to patch it yet -- I think that it
 would be worthwhile to look into moving to 10.2, which has a large
 number of improvements, although suffering from some Linuxisms.

This will be easy to patch, using one of two methods:

 - change struct scsi_sense_data to struct scsi_sense_data_fixed
or, better yet:
 - use scsi_extract_sense_len(), which will work for fixed or descriptor
   sense.

 Regards,
 b.
 
 
 ===   cdparanoia-3.9.8_9 depends on executable: gmake - found
 ===  Configuring for cdparanoia-3.9.8_9
 creating cache ./config.cache
 checking host system type... Invalid configuration
 `amd64-portbld-freebsd9.9': machine `amd64-portbld' not recognized
 
 checking for ranlib... ranlib
 checking for ar... ar
 checking for install... /usr/bin/install -c -o root -g wheel
 checking how to run the C preprocessor... cpp
 checking for ANSI C header files... yes
 checking size of short... 2
 checking size of int... 4
 checking size of long... 8
 checking size of long long... 8
 checking for int16_t... yes
 checking for int32_t... yes
 checking for u_int16_t... yes
 checking for u_int32_t... yes
 checking for linux/sbpcd.h... no
 checking for linux/ucdrom.h... no
 checking whether gmake sets ${MAKE}... yes
 checking for working const... yes
 updating cache ./config.cache
 creating ./config.status
 creating Makefile
 creating interface/Makefile
 creating paranoia/Makefile
 ===  Building for cdparanoia-3.9.8_9
 cd interface  gmake all
 gmake[1]: Entering directory
 `/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
 gmake libcdda_interface.a CFLAGS=-O -O2 -pipe -march=athlon64
 -fno-strict-aliasing
 gmake[2]: Entering directory
 `/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
 cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c scan_devices.c
 cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c common_interface.c
 cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c cooked_interface.c
 cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c interface.c
 cc -O -O2 -pipe -march=athlon64 -fno-strict-aliasing -c scsi_interface.c
 scsi_interface.c: In function 'handle_scsi_cmd':
 scsi_interface.c:370: error: 'struct scsi_sense_data' has no member
 named 'flags'
 scsi_interface.c:381: error: 'struct scsi_sense_data' has no member
 named 'add_sense_code'
 scsi_interface.c:382: error: 'struct scsi_sense_data' has no member
 named 'add_sense_code_qual'
 scsi_interface.c: In function 'scsi_read_map':
 scsi_interface.c:967: error: 'struct scsi_sense_data' has no member
 named 'flags'
 scsi_interface.c:968: error: 'struct scsi_sense_data' has no member
 named 'add_sense_code'
 scsi_interface.c:969: error: 'struct scsi_sense_data' has no member
 named 'add_sense_code_qual'
 gmake[2]: *** [scsi_interface.o] Error 1
 gmake[2]: Leaving directory
 `/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
 gmake[1]: *** [all] Error 2
 gmake[1]: Leaving directory
 `/tmp/home/u1/pwrk/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface'
 gmake: *** [all] Error 2
 *** Error code 1
 
 Stop in /home/u1/pwrk/ports/audio/cdparanoia.

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: security/cfs

2011-10-07 Thread Rene Ladan
Op 06-10-2011 21:39, Doug Barton schreef:
 On 10/06/2011 05:24, Kostik Belousov wrote:
 So, after the all discussions, security/cfs was silently removed.

I plead guilty.

 Right, because the EXPIRATION_DATE arrived and all the reasons for
 removing it were still valid.
 
 I really don't need to explain to you that the files are still in the
 attic, and that if you want to fix it and bring it back nothing is
 stopping you, do I? :)
 
Exactly what I was thinking, but something stopped me from sending such
a message. Thanks Doug :)

Notes to self:
(1) read ports@ archives before considering removing a port, even if
it's orphaned, forbidden, and broken.
(2) While doing (1) after the fact, our ports@ troll seems to be in good
health (you know who you are).

René
-- 
http://www.rene-ladan.nl:8080/

GPG fingerprint = ADBC ECCD EB5F A6B4 549F  600D 8C9E 647A E564 2BFC
(subkeys.pgp.net)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: devel/cross-gcc and cross-binutils: how to set TGTARCH and TGTABI

2011-10-07 Thread Stanislav Sedov
On Thu, 6 Oct 2011 08:43:31 + (GMT)
Thomas Mueller mueller6...@bellsouth.net mentioned:

  From $PORTSDIR/devel/cross-binutils:
  
  GNU binutils for cross-target application development.
  
  Prerequisite for the GCC cross-compiling environment.
  
  Use TGTARCH switch to select target architecture, and TGTABI to select ABI.
  E.g. the following command will build binutils for rtems on sparc:
  % make TGTARCH=sparc TGTABI=rtems
  
  If you encounter any problems building/using/installing this port, please
  make me know. It would help to improve this port in feature.
 
 -- Stanislav Sedov s...@freebsd.org
 
 My question is how to set TGTARCH and TGTABI, that is not documented; I 
 looked at the web sites.
 
 Would TGTARCH be i386 or amd64, if I want to build for those platforms?
 
 What about TGTABI?  I don't know the proper code words, would want to compile 
 for Linux and possibly NetBSD.
 
 Maybe I need to make fetch followed by make extract and look inside?
 

Hi!

You cannot use this port to build toolchaing for compiling Linux and
NetBSD applications.  This port creates toolchain using the newlib
libc library, which is used by some embedded operating systems (e.g.
rtems, ecos).  It can also be used to build bare-metal standalone
applications.  Linux on the other hand is using glibc and NetBSD their
own libc implementation, so this toolchain would not work.

-- 
Stanislav Sedov
ST4096-RIPE

()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


audio/cdparanoia broken on -CURRENT, and probably on 9.0

2011-10-07 Thread grarpamp
 I think that it would be worthwhile to look into moving to 10.2,
 which has a large number of improvements, although suffering
 from some Linuxisms.

My efforts at an update failed due to my own failings :)
So just a ditto on the suggestion to move to 10.2 and
avoiding BROKEN. You may also want to look over their
r32289 and mailing list. Either way, some of us with
larger rip projects would luv u, heh :)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: cvs commit: ports/security/cyrus-sasl2 Makefile ports/security/cyrus-sasl2/files patch-plugins::gssapi.c

2011-10-07 Thread Doug Barton
In case anyone wants to take this on, this port fails to install on 10.0
because it uses its own version of libtool. I took a quick look but
there wasn't a solution obvious enough for me. :)


Doug


On 10/07/2011 09:15, Hajimu UMEMOTO wrote:
 ume 2011-10-07 16:15:47 UTC
 
   FreeBSD ports repository
 
   Modified files:
 security/cyrus-sasl2 Makefile 
   Added files:
 security/cyrus-sasl2/files patch-plugins::gssapi.c 
   Log:
   Fix GSSAPI client crash, NULL ptr dereference.
   
   Submitted by:   Phil Pennock cyrus-sasl-phil__at__spodhuis.org
   Obtained from:  
 http://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2011-October/002358.html
   
   Revision  ChangesPath
   1.148 +1 -1  ports/security/cyrus-sasl2/Makefile
   1.5   +22 -0 
 ports/security/cyrus-sasl2/files/patch-plugins::gssapi.c (new)
 
 http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/security/cyrus-sasl2/Makefile.diff?r1=1.147r2=1.148f=h
 http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/security/cyrus-sasl2/files/patch-plugins::gssapi.c
 



-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: FreeBSD unmaintained ports which are currently scheduled for deletion

2011-10-07 Thread perryh
lini...@freebsd.org wrote:

 portname:   net-mgmt/portmon
 deprecated because: No more public distfiles

I was able to fetch it earlier today:

$ ( cd /usr/ports/net-mgmt/portmon  make fetch-recursive )
=== Fetching all distfiles for portmon-2.0 and dependencies
===  Vulnerability check disabled, database not found
===  License check disabled, port has not defined LICENSE
= portmon-2.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
= Attempting to fetch from http://voodoo.bawue.com/download/.
portmon-2.0.tar.gz100% of  104 kB   71 kBps
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: lang/chicken, fails to package, needs MAKE_JOBS_UNSAFE

2011-10-07 Thread Doug Barton
On 10/05/2011 15:19, Vitaly Magerya wrote:
 Doug Barton wrote:
 Trying to create a package for lang/chicken today, it fails to build at
 all with FORCE_MAKE_JOBS, so it needs MAKE_JOBS_UNSAFE= true in the
 Makefile.
 
 True.

Do you mind if I go ahead and add that sooner rather than later?

 Also, once it got built, it failed to package:

 ===  Building package for chicken-4.7.0
 tar: lib/chicken/6/modules.db: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256
 *** Error code 1

 Stop in /usr/ports/lang/chicken.
 
 Seems to work for me on 8.2-RELEASE amd64.
 Can you send me your build/install/package logs?
 I'll try to reproduce the problem.

Sure, here you go:

http://people.freebsd.org/~dougb/chicken-build.log

FYI, I did some more testing and it only fails on i386. I confirmed your
experience that it works fine on 8-amd64.


Thanks,

Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org