Re: OpenTTD
On Wed, Jun 22, 2011 at 10:33:14AM +0400, Ilya A. Arkhipov wrote: > Ok i rewrite patch and do with argument, and write patch to portlint ;) Wow, if you could write a patch to portlint that is would correctly suggest that MAINTAINER/COMMENT/LICENSE should be grouped together, and FOO_DEPENDS would be closed to USE_BAR knobs, I'd be very grateful! Just to make myself clear on this issue: COMMENT/LICENSE are general software information, FOO_DEPENDS and USE_BAR knobs both specify dependencies (that is, package-related stuff). I believe that it does not make sence to mix them, hence LICENSE should be defined before _DEPENDS, not after. ./danfe P.S. CCing -ports@ to get broader audience on this proposal. ___ 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: emulators/wine
Thank you very much for the info. I will give it a try. Bruce Mark Felder wrote: On Tue, 21 Jun 2011 16:03:48 -0500, Bruce Meier wrote: Does anyone know if there will ever be a wine64 port? The guy working on it is posting packages here: http://www.mediafire.com/wine_fbsd64 Feel free to install them -- they work very well. Regards, Mark ___ 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" ___ 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: emulators/wine
On Tue, 21 Jun 2011 16:03:48 -0500, Bruce Meier wrote: Does anyone know if there will ever be a wine64 port? The guy working on it is posting packages here: http://www.mediafire.com/wine_fbsd64 Feel free to install them -- they work very well. Regards, Mark ___ 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"
emulators/wine
Hi, Does anyone know if there will ever be a wine64 port? Thanks Bruce ___ 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: shells/ksh93 install fail
On Tue, Jun 21, 2011 at 01:23:51PM -0700, Doug Barton wrote: > On 6/21/2011 1:02 PM, jhell wrote: > > > > > > On Tue, Jun 21, 2011 at 12:48:57PM -0700, Doug Barton wrote: > >> An effort to upgrade to 20110208_1 is failing for me: > >> > >> ===> Installing for ksh93-20110208_1 > >> ===>Generating temporary packing list > >> ===> Checking if shells/ksh93 already installed > >> install -o root -g wheel -m 555 > >> /usr/local/tmp/usr/ports/shells/ksh93/work/bin/ksh /usr/local/bin/ksh93 > >> install: $WRKDIRPREFIX/usr/ports/shells/ksh93/work/bin/ksh: No such file > >> or directory > >> *** Error code 71 > >> > >> Is it possible that $WRKDIRPREFIX is the trigger? > >> > > > > I did not actually see that here on 8-STABLE/i386, just for the record. > > Thanks. At least one person on IRC said that it worked for them with or > without $WRKDIRPREFIX, so that's probably not it. What's odd is that > these package building systems have been working fine for hundreds of > ports for quite a while now, so I'm stumped. > How about your WRKDIRPREFIX var in make.conf ? I have mine set here to: WRKDIRPREFIX?=/usr/obj Also contained within an .if conditional for ports but that shouldnt matter. Though the difference of having something like ':=' '?=' '=' I don't think should make much of a difference unless something else strange is being set or happening elsewhere. Just a thought. ___ 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: shells/ksh93 install fail
On 6/21/2011 1:02 PM, jhell wrote: On Tue, Jun 21, 2011 at 12:48:57PM -0700, Doug Barton wrote: An effort to upgrade to 20110208_1 is failing for me: ===> Installing for ksh93-20110208_1 ===>Generating temporary packing list ===> Checking if shells/ksh93 already installed install -o root -g wheel -m 555 /usr/local/tmp/usr/ports/shells/ksh93/work/bin/ksh /usr/local/bin/ksh93 install: $WRKDIRPREFIX/usr/ports/shells/ksh93/work/bin/ksh: No such file or directory *** Error code 71 Is it possible that $WRKDIRPREFIX is the trigger? I did not actually see that here on 8-STABLE/i386, just for the record. Thanks. At least one person on IRC said that it worked for them with or without $WRKDIRPREFIX, so that's probably not it. What's odd is that these package building systems have been working fine for hundreds of ports for quite a while now, so I'm stumped. -- 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: shells/ksh93 install fail
On Tue, Jun 21, 2011 at 12:48:57PM -0700, Doug Barton wrote: > An effort to upgrade to 20110208_1 is failing for me: > > ===> Installing for ksh93-20110208_1 > ===> Generating temporary packing list > ===> Checking if shells/ksh93 already installed > install -o root -g wheel -m 555 > /usr/local/tmp/usr/ports/shells/ksh93/work/bin/ksh /usr/local/bin/ksh93 > install: $WRKDIRPREFIX/usr/ports/shells/ksh93/work/bin/ksh: No such file > or directory > *** Error code 71 > > Is it possible that $WRKDIRPREFIX is the trigger? > I did not actually see that here on 8-STABLE/i386, just for the record. ___ 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"
shells/ksh93 install fail
An effort to upgrade to 20110208_1 is failing for me: ===> Installing for ksh93-20110208_1 ===> Generating temporary packing list ===> Checking if shells/ksh93 already installed install -o root -g wheel -m 555 /usr/local/tmp/usr/ports/shells/ksh93/work/bin/ksh /usr/local/bin/ksh93 install: $WRKDIRPREFIX/usr/ports/shells/ksh93/work/bin/ksh: No such file or directory *** Error code 71 Is it possible that $WRKDIRPREFIX is the trigger? 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"
Re: PR ports/155331
On Tue, 21 Jun 2011 07:31:44 +0200 Simon Olofsson wrote: > Christopher, > > a nice tool to test your ports before submitting them is > ports-mgmt/porttools: > Just run `port test` and it'll run portlint and try to build you port > etc. You can then submit your port with `port submit`. Read the > manpage for all details. > > Simon > > ___ > 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" Thank you for your replies. I will clean up my proposed port and will report back when done (hopefully by next week). Cheers, -- Christopher J. Ruwe TZ GMT + 2 ___ 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: [ANNOUNCE]: clang compiling ports
Am 21.06.2011 12:43, schrieb Baptiste Daroussin:
> Just be aware that stable clang has some issue with the stable binutils,
> to fix this make sure to use binutils from ports.
>
> To be able to test on stable:
> export CC=clang
> export CXX=clang++
> PATH=/usr/local/bin:${PATH} make -C myport
> the ld from localbase is found first so clang uses it.
>
> currently from my testing everything that succeed compiling with this
> also succeed on current
> and everything that fail on current also fails this way.
Thanks, however, this misses one particular error case, namely,
hardwired compiler names such as cc, c89, c99, gcc -- because these
remain in PATH. Possibly we can just create a dummy directory and stuff
all gcc-related tool names as hard links to [/usr]/bin/false in there
and stuff that early in the path, too, so you see if a port uses gcc.
For instance, the security/openvpn plugins did that.
___
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: [ANNOUNCE]: clang compiling ports
On Tue, 21 Jun 2011 12:39:18 +0200, Matthias Andree wrote:
Am 21.06.2011 12:29, schrieb Alex Dupre:
Matthias Andree ha scritto:
I have patches for my ports, can I send them to anyone to test
them?
Do something similar to this:
Thanks for the instructions, but currently I haven't a -current
ready
for testing, this is the reason of my question :-)
Are the faults you're fixing specific to -CURRENT, like affecting
features or changes specific to 9-CURRENT?
If not, try -STABLE in the way I've proposed -- you need to do that
twice:
1 - before your fixes and see if the problem reproduces; and
2 - if it does, try again after your fixes -- if your fixes solve the
problem on -STABLE, that will likely work with -CURRENT too.
HTH
___
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"
Just be aware that stable clang has some issue with the stable
binutils, to fix this make sure to use binutils from ports.
To be able to test on stable:
export CC=clang
export CXX=clang++
PATH=/usr/local/bin:${PATH} make -C myport
the ld from localbase is found first so clang uses it.
currently from my testing everything that succeed compiling with this
also succeed on current
and everything that fail on current also fails this way.
regards,
Bapt
___
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: [ANNOUNCE]: clang compiling ports
Am 21.06.2011 12:29, schrieb Alex Dupre: > Matthias Andree ha scritto: >>> I have patches for my ports, can I send them to anyone to test them? >> >> Do something similar to this: > > Thanks for the instructions, but currently I haven't a -current ready > for testing, this is the reason of my question :-) Are the faults you're fixing specific to -CURRENT, like affecting features or changes specific to 9-CURRENT? If not, try -STABLE in the way I've proposed -- you need to do that twice: 1 - before your fixes and see if the problem reproduces; and 2 - if it does, try again after your fixes -- if your fixes solve the problem on -STABLE, that will likely work with -CURRENT too. HTH ___ 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: [ANNOUNCE]: clang compiling ports
Matthias Andree ha scritto: I have patches for my ports, can I send them to anyone to test them? Do something similar to this: Thanks for the instructions, but currently I haven't a -current ready for testing, this is the reason of my question :-) -- Alex Dupre ___ 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: [ANNOUNCE]: clang compiling ports
Am 21.06.2011 12:15, schrieb Alex Dupre: > Roman Divacky ha scritto: >> It would be great if you could skim over the list to see if some of >> the ports >> you maintain are broken and possibly try to fix them. > > I have patches for my ports, can I send them to anyone to test them? > Do something similar to this: 1. install port-tools and portlint unless you already have them 2. move gcc out of the way: cd /usr/bin for i in cc c89 c99 gcc g++ ; do mv $i $i.off done 3. test your port(s): cd /usr/ports/some/port port test -- CC=clang CXX=clang++ 4. move gcc back into place: cd /usr/bin for i in cc c89 c99 gcc g++ ; do mv $i.off $i done It's not exactly what 9-exp has been trying (and will miss, for instance, header differences that trip up clang), but close enough for many ports. HTH ___ 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: [ANNOUNCE]: clang compiling ports
Roman Divacky ha scritto: It would be great if you could skim over the list to see if some of the ports you maintain are broken and possibly try to fix them. I have patches for my ports, can I send them to anyone to test them? -- Alex Dupre ___ 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: [ANNOUNCE]: clang compiling ports
On Tue, Jun 21, 2011 at 8:41 AM, Alexander Leidinger wrote: > Quoting Mark Linimon (from Mon, 20 Jun 2011 18:21:26 > -0500): > >> On Mon, Jun 20, 2011 at 05:37:53PM +0200, Roman Divacky wrote: >>> >>> Flz@ just ran an exp-build with CC=clang and CXX=clang++. The results can >>> be >>> seen here: >>> >>> http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/ >> >> A permanent URL to this run is: >> >> >> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/ >> >> That will stick around even if we use amd64-9-exp for something else. > > It may be beneficial for such kind of exp runs to have a list which is > sorted by number of affected ports. Fixed now. Florent ___ 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: [ANNOUNCE]: clang compiling ports
On Mon, 20 Jun 2011 17:37:53 +0200, Roman Divacky wrote: Hi! Flz@ just run an exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/ A lot of these failures are trivial to fix (ie. not respecting CC setting, etc.) and prevent a lot of other ports from building. It would be great if you could skim over the list to see if some of the ports you maintain are broken and possibly try to fix them. A small introduction into the Clang+Ports can be read at: http://wiki.freebsd.org/PortsAndClang. Please focus on the biggest offenders (ie. ports that prevent the most other ports from building). Thank you for helping us! Roman Divacky I have tried to fix most of my ports, I now have a problem which seem to appear quite often : local symbol 5: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EE13orphanOrCloneEiRi' from udata.o local symbol 6: discarded in section `.text._ZNK6icu_4813UnicodeStringeqERKS0_' from messagepattern.o local symbol 7: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EED1Ev' from locutil.o [...] local symbol 96: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EE12releaseArrayEv' from servrbf.o local symbol 97: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EE12aliasInsteadEPci' from servrbf.o local symbol 98: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EE6resizeEii' from servrbf.o local symbol 99: discarded in section `.text._ZN6icu_4815MaybeStackArrayIcLi40EE13orphanOrCloneEiRi' from servrbf.o clang++: error: linker command failed with exit code 1 (use -v to see invocation) To test I'm using CC=clang CXX=clang++ on a FreeBSD8-stable box (1 week old) using clang from ports: 2.9. does anyone have a clue for that? Am I doing something wrong? regards, Bapt ___ 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"
[CFT] Likewise-open preliminary port
Hi everyone, Over the past few weeks, I've been working on a Likewise-open [1] port and am starting to get something useable. Technically speaking, the port builds fine on x86 and amd64 platforms (gcc- only ATM) and is able to use libraries from the ports tree instead of the ones bundled in the source tarball. Basic functionality has been tested : with a local account database (SQLite), I was able to retrieve account information through nsswitch as well as authenticate a user on sshd through PAM. The CIFS server also works : a local Likewise user is able to connect to it. Anyway, I am not a Likewise expert and there are still several -important- tests to perform : - Try to join an Active Directory server and use it as an authentication source, instead of the local SQLite DB - Play with client-side commands (lwio-copy, lwio-fuse-mount) ; I could not get them work (see below) but I may have missed something - Try advanced CIFS server configurations Here are also remaining tasks that have to be done before the port can hit the tree : - Write a rc.d startup script (probably a wrapper to the provided init.d scripts) - Fix build with clang - Try to build with Heimdal (?) I would be pleased to get feedback from you... any help or comment is welcome ! -- Now, for those interested, here is a quick setup HOWTO : 0) Getting the port : * The port can be downloaded here : http://people.freebsd.org/~martymac/ports/likewise-open-6.2.0.r59706-port.tgz Un-tar it into /usr/ports/net : # tar xz -C /usr/ports/net -f likewise-open-6.2.0.r59706-port.tgz 1) Building *** Likewise-open has only been tested with MIT Kerberos (security/krb5). You will need to specify KRB5_HOME when building this dependency to have the port set a correct rpath, thus avoid loading base-system Heimdal libraries at runtime and getting a mixed MIT/Heimdal Kerberos environment, which would lead to unstable behaviour. The best way to do this is either to add : KRB5_HOME=/usr/local in your /etc/make.conf file, or build the likewise-open port this way : # make KRB5_HOME=/usr/local install clean It should build without errors. 2) Configuring ** Once installed, the first thing to do is to initialize the Likewise registry : # /usr/local/etc/likewise-open/init.d/lwsmd start # for file in /usr/local/etc/likewise-open/*.reg; do /usr/local/bin/lwregshell upgrade $file; done # /usr/local/etc/likewise-open/init.d/lwsmd stop The second thing to do is to check your hostname(1) is resolvable through getaddrinfo(3). You can do this by adding an appropriate record to your DNS server or a line in /etc/hosts. Finally, configure the gss library by copying the provided mech file into /usr/local/etc/gss/mech : # cp /usr/local/etc/likewise-open/gss/mech /usr/local/etc/gss/mech That should be all needed (for basic testing). 3) Starting up : As no FreeBSD rc script is provided (yet), you'll have to use common scripts provided to start Likewise up. They work fine on FreeBSD : # /usr/local/etc/likewise-open/init.d/lwsmd start # /usr/local/bin/lwsm start eventlog # /usr/local/bin/lwsm start srvsvc You can check that each service is running with the following command : # /usr/local/bin/lwsm list 4) Testing : Once everything is running, let's configure nsswitch : # /usr/local/bin/domainjoin-cli configure --enable nsswitch This command will modify your /etc/nsswitch.conf file and add the lsass module. You might want to make a backup of this file before testing the command. The lsass module will delegate user and group identification to Likewise. Then, you can try adding a user to Likewise's local SQLite account database : # lw-add-user --home /home/test1 --shell /bin/sh test1 # lw-mod-user --enable-user --set-password 'abcd' test1 and create a home for him : # mkdir /home/test1 # chown 2000:1800 /home/test1 Then you can check this user is recognized through nsswitch : # id LAPTOP\\test1 uid=2000(LAPTOP\test1) gid=1800(LAPTOP\Likewise Users) groups=1800(LAPTOP\Likewise Users) # id 2000 uid=2000(LAPTOP\test1) gid=1800(LAPTOP\Likewise Users) groups=1800(LAPTOP\Likewise Users) # getent passwd [...] LAPTOP\Administrator:x:1500:1800::/:/bin/sh LAPTOP\Guest:x:1501:1800::/tmp:/bin/sh LAPTOP\test1:x:2000:1800::/home/test1:/bin/sh You can then check that he is able to connect to the 'c$' CIFS share : $ smbclient -U 'LAPTOP\test1' '//127.0.0.1/c$' Now we can test authentication through PAM by enabling the pam module : # /usr/local/bin/domainjoin-cli configure --enable pam This command will modify your PAM (/etc/pam.d/*) configuration files. You may also back them up first. Then you can try to authenticate through ssh, which should work : $ ssh 'LAPTOP\test1@127.0.0.1' You can then disable the PAM module by running : # /usr/local/bin/domainjoin-cli configure --disable pam or by manually reverting your PAM configuration files. 5) What does not work : *
Re: gcc-clang issue
Am 21.06.2011 01:00, schrieb Koop Mast: > Hey, could you try this patch? I try the USE_CSTD=gnu89 trick if I get > symbol troubles when linking. This is because clang defaults to gnu99 > while gcc still defaults to gnu89. From what I remember the inline > keyword has different meanings between the two, or how you use it > atleast. Someone explained it to my last year but I can't remember all > the gory details about it. > > http://people.freebsd.org/~kwm/e2fsprogs-clang.diff Gorgeous, works and passes self-tests (on RELENG_8 at least). Committed, dank je wel! ___ 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: [ANNOUNCE]: clang compiling ports
Quoting Mark Linimon (from Mon, 20 Jun 2011 18:21:26 -0500): On Mon, Jun 20, 2011 at 05:37:53PM +0200, Roman Divacky wrote: Flz@ just ran an exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/ A permanent URL to this run is: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/ That will stick around even if we use amd64-9-exp for something else. It may be beneficial for such kind of exp runs to have a list which is sorted by number of affected ports. Bye, Alexander. -- So... did you ever wonder, do garbage men take showers before they go to work? http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ 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"
