audio/cdparanoia broken on -CURRENT, and probably on 9.0
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
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
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
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
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
On Thu, 6 Oct 2011 08:43:31 + (GMT) "Thomas Mueller" 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 > > 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
> 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
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 > 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.147&r2=1.148&f=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
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
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"
