Re: lang/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 10:55 PM, Scot Hetzel wrote: > On Wed, Mar 17, 2010 at 10:45 PM, Adam Vande More > wrote: > > On Wed, Mar 17, 2010 at 10:38 PM, Jason Garrett > wrote: > > > >> CC'ing port maintainer > >> > >> Here is the commit for timeb.h being deprecated and adding the #warning > >> > >> http://www.mail-archive.com/svn-src-...@freebsd.org/msg20965.html > >> > >> Solutions are to either use a replacement for timeb.h (unknown by me > >> at this point), quit using timeb.h (not sure how guile depends on > >> this), or omit the -Werror from > >> /usr/ports/lang/guile/work/guile-1.8.6/Makefile and > >> /usr/ports/lang/guile-1.8.6/libguile/Makefile. > >> > >> Maintainer, please direct on how to proceed. As it sits without > >> modification the port is broken, even with -Wno-error set in > >> /etc/make.conf. > >> > > > > I'm not sure about that. The no-error stuff I believe is a CURRENT > thing, > > at least when running betas and stuff you'll run into the warnings as > errors > > thing. The port builds fine on other branches and I suspect would > continue > > to build on CURRENT if you got rid of whatever controlling the compile > > setting. Nevertheless, it seems the port should be fixed to use > sys/time.h > > and gettimeofday(2) instead. Just the way it looks to me, I'm no expert > > here. > > > The port only uses sys/timeb.h in libguile/stime.c, and only to > include the header when HAVE_SYS_TIMEB_H is defined, removing > sys/timeb.h from the header include check in configure.in allows the > port to build on a recent CURRENT. > > Scot > -- Adam Vande More ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 22:55, Scot Hetzel wrote: > On Wed, Mar 17, 2010 at 10:45 PM, Adam Vande More > wrote: >> On Wed, Mar 17, 2010 at 10:38 PM, Jason Garrett wrote: >> >>> CC'ing port maintainer >>> >>> Here is the commit for timeb.h being deprecated and adding the #warning >>> >>> http://www.mail-archive.com/svn-src-...@freebsd.org/msg20965.html >>> >>> Solutions are to either use a replacement for timeb.h (unknown by me >>> at this point), quit using timeb.h (not sure how guile depends on >>> this), or omit the -Werror from >>> /usr/ports/lang/guile/work/guile-1.8.6/Makefile and >>> /usr/ports/lang/guile-1.8.6/libguile/Makefile. >>> >>> Maintainer, please direct on how to proceed. As it sits without >>> modification the port is broken, even with -Wno-error set in >>> /etc/make.conf. >>> >> >> I'm not sure about that. The no-error stuff I believe is a CURRENT thing, >> at least when running betas and stuff you'll run into the warnings as errors >> thing. The port builds fine on other branches and I suspect would continue >> to build on CURRENT if you got rid of whatever controlling the compile >> setting. Nevertheless, it seems the port should be fixed to use sys/time.h >> and gettimeofday(2) instead. Just the way it looks to me, I'm no expert >> here. >> > The port only uses sys/timeb.h in libguile/stime.c, and only to > include the header when HAVE_SYS_TIMEB_H is defined, removing > sys/timeb.h from the header include check in configure.in allows the > port to build on a recent CURRENT. > > Scot > Thank you for your response, I learn more each time I post to these lists! ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 10:45 PM, Adam Vande More wrote: > On Wed, Mar 17, 2010 at 10:38 PM, Jason Garrett wrote: > >> CC'ing port maintainer >> >> Here is the commit for timeb.h being deprecated and adding the #warning >> >> http://www.mail-archive.com/svn-src-...@freebsd.org/msg20965.html >> >> Solutions are to either use a replacement for timeb.h (unknown by me >> at this point), quit using timeb.h (not sure how guile depends on >> this), or omit the -Werror from >> /usr/ports/lang/guile/work/guile-1.8.6/Makefile and >> /usr/ports/lang/guile-1.8.6/libguile/Makefile. >> >> Maintainer, please direct on how to proceed. As it sits without >> modification the port is broken, even with -Wno-error set in >> /etc/make.conf. >> > > I'm not sure about that. The no-error stuff I believe is a CURRENT thing, > at least when running betas and stuff you'll run into the warnings as errors > thing. The port builds fine on other branches and I suspect would continue > to build on CURRENT if you got rid of whatever controlling the compile > setting. Nevertheless, it seems the port should be fixed to use sys/time.h > and gettimeofday(2) instead. Just the way it looks to me, I'm no expert > here. > The port only uses sys/timeb.h in libguile/stime.c, and only to include the header when HAVE_SYS_TIMEB_H is defined, removing sys/timeb.h from the header include check in configure.in allows the port to build on a recent CURRENT. Scot ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 9:35 PM, Jason Garrett wrote: > The port now compiles. > > I could submit a patch omitting this, but is that the RIGHT fix? The correct fix is to remove the sys/timeb.h from the list of headers to check for in the configure.in script See PR 144845 http://www.freebsd.org/cgi/query-pr.cgi?pr=144845 Scot ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 10:38 PM, Jason Garrett wrote: > CC'ing port maintainer > > Here is the commit for timeb.h being deprecated and adding the #warning > > http://www.mail-archive.com/svn-src-...@freebsd.org/msg20965.html > > Solutions are to either use a replacement for timeb.h (unknown by me > at this point), quit using timeb.h (not sure how guile depends on > this), or omit the -Werror from > /usr/ports/lang/guile/work/guile-1.8.6/Makefile and > /usr/ports/lang/guile-1.8.6/libguile/Makefile. > > Maintainer, please direct on how to proceed. As it sits without > modification the port is broken, even with -Wno-error set in > /etc/make.conf. > I'm not sure about that. The no-error stuff I believe is a CURRENT thing, at least when running betas and stuff you'll run into the warnings as errors thing. The port builds fine on other branches and I suspect would continue to build on CURRENT if you got rid of whatever controlling the compile setting. Nevertheless, it seems the port should be fixed to use sys/time.h and gettimeofday(2) instead. Just the way it looks to me, I'm no expert here. -- Adam Vande More ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 21:35, Jason Garrett wrote: > On Wed, Mar 17, 2010 at 21:30, Jason Garrett wrote: >> On Wed, Mar 17, 2010 at 21:26, Jason Garrett wrote: >>> On Wed, Mar 17, 2010 at 21:06, Chuck Swiger wrote: On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: > This must be set by default as I have set no other flags in > /etc/make.conf or otherwise. How would I go about un-setting this? > -Wno-error? Yes, that should do it: touch /etc/make.conf && echo "CFLAGS += -Wno-error" >> /etc/make.conf Please note that I'm inferring from the compiler treating a #warning as an error; if you show more of the actual compilation line, the list might be better able to understand what the compiler flags were and where they might have been set. Regards, -- -Chuck >>> >>> I set -Wno-error as suggested, it is present during compile but the >>> -Werror is still set at the end. I also found where -Werror is set. >>> First I need to enable sshd on the machine and get a good copy paste, >>> more to come! >>> >> >> Here is the error with 2 lines on top of it, see where -Wno-error and >> -Werror are both set? >> >> ./guile-snarf -o stacks.x stacks.c -DHAVE_CONFIG_H -I.. -I.. -I.. >> -I/usr/local/include -O2 -pipe -Wno-error -march=nocona >> -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror >> ./guile-snarf -o stime.x stime.c -DHAVE_CONFIG_H -I.. -I.. -I.. >> -I/usr/local/include -O2 -pipe -Wno-error -march=nocona >> -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror >> In file included from stime.c:76: >> /usr/include/sys/timeb.h:42:2: error: #warning "this file includes >> which is deprecated" >> gmake[2]: *** [stime.x] Error 1 >> gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' >> gmake[1]: *** [all-recursive] Error 1 >> gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6' >> gmake: *** [all] Error 2 >> *** Error code 1 >> >> Stop in /usr/ports/lang/guile. >> > > work/guile-1.8.6/Makefile and > work/guile-1.8.6/libguile/Makefile both staically set -Werror > > The port now compiles. > > I could submit a patch omitting this, but is that the RIGHT fix? > CC'ing port maintainer Here is the commit for timeb.h being deprecated and adding the #warning http://www.mail-archive.com/svn-src-...@freebsd.org/msg20965.html Solutions are to either use a replacement for timeb.h (unknown by me at this point), quit using timeb.h (not sure how guile depends on this), or omit the -Werror from /usr/ports/lang/guile/work/guile-1.8.6/Makefile and /usr/ports/lang/guile-1.8.6/libguile/Makefile. Maintainer, please direct on how to proceed. As it sits without modification the port is broken, even with -Wno-error set in /etc/make.conf. ___ 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/guile fails to build on amd64 / 9-CURRENT
On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: > This must be set by default as I have set no other flags in > /etc/make.conf or otherwise. How would I go about un-setting this? > -Wno-error? Yes, that should do it: touch /etc/make.conf && echo "CFLAGS += -Wno-error" >> /etc/make.conf Please note that I'm inferring from the compiler treating a #warning as an error; if you show more of the actual compilation line, the list might be better able to understand what the compiler flags were and where they might have been set. Regards, -- -Chuck ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 21:30, Jason Garrett wrote: > On Wed, Mar 17, 2010 at 21:26, Jason Garrett wrote: >> On Wed, Mar 17, 2010 at 21:06, Chuck Swiger wrote: >>> On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: This must be set by default as I have set no other flags in /etc/make.conf or otherwise. How would I go about un-setting this? -Wno-error? >>> >>> Yes, that should do it: >>> >>> touch /etc/make.conf && echo "CFLAGS += -Wno-error" >> /etc/make.conf >>> >>> Please note that I'm inferring from the compiler treating a #warning as an >>> error; if you show more of the actual compilation line, the list might be >>> better able to understand what the compiler flags were and where they might >>> have been set. >>> >>> Regards, >>> -- >>> -Chuck >>> >>> >> >> I set -Wno-error as suggested, it is present during compile but the >> -Werror is still set at the end. I also found where -Werror is set. >> First I need to enable sshd on the machine and get a good copy paste, >> more to come! >> > > Here is the error with 2 lines on top of it, see where -Wno-error and > -Werror are both set? > > ./guile-snarf -o stacks.x stacks.c -DHAVE_CONFIG_H -I.. -I.. -I.. > -I/usr/local/include -O2 -pipe -Wno-error -march=nocona > -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror > ./guile-snarf -o stime.x stime.c -DHAVE_CONFIG_H -I.. -I.. -I.. > -I/usr/local/include -O2 -pipe -Wno-error -march=nocona > -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror > In file included from stime.c:76: > /usr/include/sys/timeb.h:42:2: error: #warning "this file includes > which is deprecated" > gmake[2]: *** [stime.x] Error 1 > gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/lang/guile. > work/guile-1.8.6/Makefile and work/guile-1.8.6/libguile/Makefile both staically set -Werror The port now compiles. I could submit a patch omitting this, but is that the RIGHT fix? ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 21:26, Jason Garrett wrote: > On Wed, Mar 17, 2010 at 21:06, Chuck Swiger wrote: >> On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: >>> This must be set by default as I have set no other flags in >>> /etc/make.conf or otherwise. How would I go about un-setting this? >>> -Wno-error? >> >> Yes, that should do it: >> >> touch /etc/make.conf && echo "CFLAGS += -Wno-error" >> /etc/make.conf >> >> Please note that I'm inferring from the compiler treating a #warning as an >> error; if you show more of the actual compilation line, the list might be >> better able to understand what the compiler flags were and where they might >> have been set. >> >> Regards, >> -- >> -Chuck >> >> > > I set -Wno-error as suggested, it is present during compile but the > -Werror is still set at the end. I also found where -Werror is set. > First I need to enable sshd on the machine and get a good copy paste, > more to come! > Here is the error with 2 lines on top of it, see where -Wno-error and -Werror are both set? ./guile-snarf -o stacks.x stacks.c -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 -pipe -Wno-error -march=nocona -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror ./guile-snarf -o stime.x stime.c -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 -pipe -Wno-error -march=nocona -fno-strict-aliasing -Wall -Wmissing-prototypes -Werror In file included from stime.c:76: /usr/include/sys/timeb.h:42:2: error: #warning "this file includes which is deprecated" gmake[2]: *** [stime.x] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/lang/guile. ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 21:06, Chuck Swiger wrote: > On Mar 17, 2010, at 7:00 PM, Jason Garrett wrote: >> This must be set by default as I have set no other flags in >> /etc/make.conf or otherwise. How would I go about un-setting this? >> -Wno-error? > > Yes, that should do it: > > touch /etc/make.conf && echo "CFLAGS += -Wno-error" >> /etc/make.conf > > Please note that I'm inferring from the compiler treating a #warning as an > error; if you show more of the actual compilation line, the list might be > better able to understand what the compiler flags were and where they might > have been set. > > Regards, > -- > -Chuck > > I set -Wno-error as suggested, it is present during compile but the -Werror is still set at the end. I also found where -Werror is set. First I need to enable sshd on the machine and get a good copy paste, more to come! ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 20:49, Chuck Swiger wrote: > Hi-- > > On Mar 17, 2010, at 6:35 PM, Jason Garrett wrote: >> I can't believe that no one running 9-CURRENT also didn't build gnome2 >> and found this problem? Shall I submit a PR? > > You appear to be compiling with -Werror set. Consider changing that, > otherwise submitting a PR with the fix would certainly be helpful. > > Regards, > -- > -Chuck > > This must be set by default as I have set no other flags in /etc/make.conf or otherwise. How would I go about un-setting this? -Wno-error? ___ 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/guile fails to build on amd64 / 9-CURRENT
Hi-- On Mar 17, 2010, at 6:35 PM, Jason Garrett wrote: > I can't believe that no one running 9-CURRENT also didn't build gnome2 > and found this problem? Shall I submit a PR? You appear to be compiling with -Werror set. Consider changing that, otherwise submitting a PR with the fix would certainly be helpful. Regards, -- -Chuck ___ 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/guile fails to build on amd64 / 9-CURRENT
On Wed, Mar 17, 2010 at 13:46, Jason Garrett wrote: > Please pardon, I am typing this from another computer while looking at > the screen it failed on (no Desktop Environment yet, this is failing > in the gome2 build). > > In file included from stime.c:76: > /usr/include/sys/timeb.h:42:2: error: #warning "this file includes > which is depreciated" > gmake[2] : ***[stime.x] Error 1 > gmake[2] : Leaving directory '/usr/ports/lang/guile/work/guile-1.8.6/libguile' > gmake[1] : *** [all-recursive] Error 1 > gmake[1] : Leaving directory '/usr/ports/lang/guile/work/guile-1.8.6' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/lang/guile > > Any suggestions? This has been building fine on all of my 8-STABLE > boxes (amd64). > I can't believe that no one running 9-CURRENT also didn't build gnome2 and found this problem? Shall I submit a PR? ___ 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: Ports Crash Report (hplip-3.9.8)
On Wed, 10 Mar 2010 20:12:06 +0530, USM Bish wrote:
>
>
> ...(lots snipped) ...
> checking for CRYPTO_free in -lcrypto... yes checking for snmp_timeout in
> -lnetsnmp... no checking for snmp_timeout in -lsnmp... no configure:
> error: cannot find net/ucd-snmp support (or --disable-network-build)
> ===> Script "configure" failed unexpectedly. Please report the problem
> to po...@freebsd.org [maintainer] and attach the
> "/usr/ports/print/hplip3/work/hplip-3.9.8/config.log" including the
> output of the failure of your make command. Also, it might be a good
> idea to provide
> an overview of all packages installed on your system (e.g. an `ls
> /var/db/pkg`).
> *** Error code 1
>
> Stop in /usr/ports/print/hplip3.
> *** Error code 1
>
>
See this: http://www.freebsd.org/cgi/query-pr.cgi?pr=144833
As a temporary workaround you can try adding this to make.conf:
.if ${.CURDIR:M/usr/ports/print/hplip3*}
# workaround ports/144833
CFLAGS+=-fstack-protector
.endif
___
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: correct location for third party /var files
On 17 Mar 2010 18:49:36 -
tmseck-li...@netcologne.de (Thomas-Martin Seck) wrote:
> * Dmitry Marakasov [gmane.os.freebsd.devel.ports]:
>
> > * Eitan Adler (eitanadlerl...@gmail.com) wrote:
> >
> >> Are third party tools supposed to use /usr/local/var or /var ?
> >
> > /var, absolutely. Everything that uses /usr/local/var or, even
> > worse, /usr/local/${PORTNAME} should be fixed.
>
> I beg to differ, especially your absolute posturing, but take this as
> the opinion of an aging fart.
>
> When I started maintaining ports in 2004, the (or at least my) goal
> was to avoid absolute paths in pkg-plist like the plague, that is why
> I do not bother to use something /var/cache/squid or /var/log/squid
> instead of PREFIX/squid/{logs,cache}. There is IMHO nothing wrong
> with storing variable data in $PREFIX/portname/ as long as this is
> sensibly done. $PREFIX/portname/var or $PREFIX/var/portname on the
> other hand is usually just a sign of sloppy porting and should be
> fixed.
>
> Trying to separate static and variable data and scattering said data
> across filesystems just for the sake of it or for arcane aesthetic
> reasons is - IMO - not really helpful for the user. The most important
> point is that you should never deviate to much from the directory
> layout that the software authors have in mind: users might have a
> hard time finding out where a certain directory that is mentioned in
> the documentation is actually located when the software is installed
> via FreeBSD ports (my current case in point: mail/sympa5).
Sorry to say, but you are very wrong.
There is nothing arcane about wanting to have about wanting to have
everything that's rw (as opposed to only r) on a separate file system.
Squid and sympa ports are wrong. So are a ton of www ports.
Just as an example, think of Nth jails which could nicely share via a
nullfs mount everything but the files that are either config or
variable from a "base" jail.
--
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Why do ports tree have two neon ports?
Why do the ports tree have two neon ports? The neon 0.29 is API and ABI backwards-compatible with 0.28.x and 0.27.x. Have two in the ports tree create a problems when one port want neon28 and another want 0.29 with no reason. Add more than one same libraries in the ports tree is a serious problem for us. I am requesting you to remove neon28 and have all ports to depend on neon29 after the freeze. Thanks, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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: [freebsd-ports] Pilot error or bash dependencies broken?
On Wed, 17 Mar 2010 10:20:37 -0700 Mike Winter wrote: > In spirit of a beginner's first question to 'freebsd-ports' please tell me > why bash depends on x11? > > in /etc/make.conf I had WITHOUT_X11=yes and I ended up needing Xvfb. This is > confusing to me. I get into a nasty loop of failed dependencies: > [snip list of X ports] This is very weird. The only thing which occurs to me is to try making it with WITHOUT_NLS=1 in the command line. --- Gary Jennejohn ___ 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: Java For Firefox
On 03/17/10 13:57, Jason Garrett wrote: > I am also interested. I believe that sun's java is up to Update 18 for > 1.6. Port shows Update 3. > > Also CC'ing freebsd-java into this. I don't do much code, but I am > willing to do everything I can to help out. I'm willing to test and file bug reports, as I'm not much of a coder myself. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
Re: [freebsd-ports] Pilot error or bash dependencies broken?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/2010 17:20:37, Mike Winter wrote: > in /etc/make.conf I had WITHOUT_X11=yes and I ended up needing Xvfb. This is > confusing to me. I get into a nasty loop of failed dependencies: > > make install -DWITHOUT_X11 bash > [snip] WITHOUT_X11 only applies to ports where X11 dependency is optional. Nothing happens for ports that have obligatory X11 dependencies. Yes, this is confusing, but it is too long established to change easily. > # this dependency chain is to my mind very wrong for bash, why? >> make missing bash > x11-servers/xorg-vfbserver > x11-fonts/xorg-fonts-miscbitmaps > x11-fonts/font-alias > devel/bison > graphics/dri > x11/libXinerama > x11/libxkbfile > x11-fonts/libXfont > x11-fonts/libfontenc > x11/libxkbui > x11/libXxf86misc > x11-toolkits/libXaw > x11-toolkits/libXmu > x11/libXpm > x11/pixman > devel/libpciaccess > graphics/libGL > x11-fonts/font-arabic-misc > x11-fonts/font-cursor-misc > x11-fonts/font-daewoo-misc > x11-fonts/font-dec-misc > x11-fonts/font-isas-misc > x11-fonts/font-jis-misc > x11-fonts/font-micro-misc > x11-fonts/font-misc-misc > x11-fonts/font-mutt-misc > x11-fonts/font-schumacher-misc > x11-fonts/font-sony-misc > x11-fonts/font-sun-misc > x11-fonts/encodings > x11-fonts/bdftopcf > x11-fonts/mkfontdir > x11-fonts/mkfontscale > print/freetype2 > x11/printproto > x11/libXp > misc/pciids > x11-fonts/font-util Hmmm... something seriously wrong there. bash dependencies on my machine (which is fully X11 enabled) are much simpler: % pkg_info -rx bash Information for bash-4.0.35: Depends on: Dependency: libiconv-1.13.1_1 Dependency: gettext-0.17_1 There are additionally build dependencies on m4, bison and libtool22 but none of those need X11 either. What is in your /etc/make.conf ? Wild-assed guess: you've got mention of something like USE_X11 in global scope. That's just plain wrong -- it has the effect of making *every* port depend on X11. In general, USE_FOO is for port maintainers to put into port specific Makefiles; WITH_FOO is for users to tweak behaviour on their machines. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuhMGEACgkQ8Mjk52CukIxluwCfQadajC2m2Be4BvGyKreQWdne ez8An2sKRL//PsRvCuHvdWAFcK2cjJGq =twzD -END PGP SIGNATURE- ___ 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"
lang/guile fails to build on amd64 / 9-CURRENT
Please pardon, I am typing this from another computer while looking at the screen it failed on (no Desktop Environment yet, this is failing in the gome2 build). In file included from stime.c:76: /usr/include/sys/timeb.h:42:2: error: #warning "this file includes which is depreciated" gmake[2] : ***[stime.x] Error 1 gmake[2] : Leaving directory '/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[1] : *** [all-recursive] Error 1 gmake[1] : Leaving directory '/usr/ports/lang/guile/work/guile-1.8.6' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/lang/guile Any suggestions? This has been building fine on all of my 8-STABLE boxes (amd64). ___ 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: Java For Firefox
On Fri, Mar 12, 2010 at 09:15, Programmer In Training wrote: > I don't know if I should also cc the maintainer for FF3.6, but I'm > posting here. Hopefully they'll see it. > > When will we have an updated Java for use in Firefox 3.6? I guess I > could downgrade back to 3.5 if absolutely necessary, but I'd rather not. > Though I imagine an upgraded java would mean I would have to recompile > OOo, too. ): > -- > Yours In Christ, > > PIT > Emails are not formal business letters, whatever businesses may want. > Original content copyright under the OWL http://owl.apotheon.org > Please do not CC me. If I'm posting to a list it is because I am subscribed. > > I am also interested. I believe that sun's java is up to Update 18 for 1.6. Port shows Update 3. Also CC'ing freebsd-java into this. I don't do much code, but I am willing to do everything I can to help out. ___ 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: correct location for third party /var files
* Dmitry Marakasov [gmane.os.freebsd.devel.ports]:
> * Eitan Adler (eitanadlerl...@gmail.com) wrote:
>
>> Are third party tools supposed to use /usr/local/var or /var ?
>
> /var, absolutely. Everything that uses /usr/local/var or, even worse,
> /usr/local/${PORTNAME} should be fixed.
I beg to differ, especially your absolute posturing, but take this as
the opinion of an aging fart.
When I started maintaining ports in 2004, the (or at least my) goal was
to avoid absolute paths in pkg-plist like the plague, that is why I do
not bother to use something /var/cache/squid or /var/log/squid instead
of PREFIX/squid/{logs,cache}. There is IMHO nothing wrong with storing
variable data in $PREFIX/portname/ as long as this is sensibly done.
$PREFIX/portname/var or $PREFIX/var/portname on the other hand is
usually just a sign of sloppy porting and should be fixed.
Trying to separate static and variable data and scattering said data
across filesystems just for the sake of it or for arcane aesthetic
reasons is - IMO - not really helpful for the user. The most important
point is that you should never deviate to much from the directory layout
that the software authors have in mind: users might have a hard time
finding out where a certain directory that is mentioned in the
documentation is actually located when the software is installed via
FreeBSD ports (my current case in point: mail/sympa5).
___
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] Pilot error or bash dependencies broken?
In spirit of a beginner's first question to 'freebsd-ports' please tell me why bash depends on x11? in /etc/make.conf I had WITHOUT_X11=yes and I ended up needing Xvfb. This is confusing to me. I get into a nasty loop of failed dependencies: make install -DWITHOUT_X11 bash [snip] ===> xorg-vfbserver-1.6.0,1 depends on executable: Xvfb - not found ===>Verifying install for Xvfb in /usr/ports/x11-servers/xorg-vfbserver ===> xorg-vfbserver-1.6.0,1 depends on executable: Xvfb - not found [snip many same lines] same result if I remove the WITHOUT_X11 from cmd-line and make.conf and try to make install Xvfb in x11-servers/xorg-vfbserver and the same result if I cd x11-servers; make install >pwd /usr/ports/shells/bash # this dependency chain is to my mind very wrong for bash, why? >make missing bash x11-servers/xorg-vfbserver x11-fonts/xorg-fonts-miscbitmaps x11-fonts/font-alias devel/bison graphics/dri x11/libXinerama x11/libxkbfile x11-fonts/libXfont x11-fonts/libfontenc x11/libxkbui x11/libXxf86misc x11-toolkits/libXaw x11-toolkits/libXmu x11/libXpm x11/pixman devel/libpciaccess graphics/libGL x11-fonts/font-arabic-misc x11-fonts/font-cursor-misc x11-fonts/font-daewoo-misc x11-fonts/font-dec-misc x11-fonts/font-isas-misc x11-fonts/font-jis-misc x11-fonts/font-micro-misc x11-fonts/font-misc-misc x11-fonts/font-mutt-misc x11-fonts/font-schumacher-misc x11-fonts/font-sony-misc x11-fonts/font-sun-misc x11-fonts/encodings x11-fonts/bdftopcf x11-fonts/mkfontdir x11-fonts/mkfontscale print/freetype2 x11/printproto x11/libXp misc/pciids x11-fonts/font-util ___ 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: Full Unicode Support for FreeBSD
OK ___ 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: ports/144760: sysutils/tmux: shell not working in tmux any more
On Wed, 17 Mar 2010 12:05:08 +0200 Andriy Gapon wrote: > on 17/03/2010 04:46 wen heping said the following: > > Hi, > > > >Would you test this patch ? > > If it works, I shall commit it. > > > > I think that it would be interesting/useful to understand in what respect > FreeBSD > kqueue is considered 'broken' by tmux code. > Actually it's the kqueue handling in devel/libevent, which is used by tmux, which considers our kequeue(2) implementation to be broken. The code in kqueue.c:kq_init() from libevent calls kevent() [kqueue(2)] with nchanges=1 and nevents=64. It assumes that kevent() will always return 1 on success. According to kqueue(2) kevent will return up to nevents on success. I'm not sure whether our kevent() should return 1 because nchanges=1 or not. So the question is whether kq_init() is making a bad assumption or not. In any case it seems that devel/libevent should be fixed, if necessary, rather than applying a bandaid to tmux. --- Gary Jennejohn ___ 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: Fwd: ports/144760: sysutils/tmux: shell not working in tmux any more
on 17/03/2010 04:46 wen heping said the following: > Hi, > >Would you test this patch ? > If it works, I shall commit it. > I think that it would be interesting/useful to understand in what respect FreeBSD kqueue is considered 'broken' by tmux code. -- Andriy Gapon ___ 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: Will downgrading from 9-CURRENT to 8-RELENG require anything more then a portmaster -Rafd?
2010/3/17 Aryeh M. Friedman : > See subject I think making a list of ports, deleting all ports, and installing them from scratch as described near the bottom of the portmaster manual page is more robust. There might be weird cases where the wrong libraries are used for linking. Rene ___ 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"
Will downgrading from 9-CURRENT to 8-RELENG require anything more then a portmaster -Rafd?
See subject ___ 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"
cross-gcc tgtarch=amd64 tgtabi=linux-gnu, no party
I'm trying to build devel/cross-gcc like this # make TGTARCH=amd64 TGTABI=linux-gnu only to have my dreams and aspirations crushed like this cc -O2 -pipe -fno-strict-aliasing -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W - Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual - Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno- long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -o xgcc gcc.o opts-common.o gcc-options.o gccspec.o \ intl.o prefix.o version.o ../libcpp/libcpp.a /usr/local/lib/libiconv.so -Wl,-rpath -Wl,/usr/local/lib ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a gcc.o(.rodata+0x1b38): undefined reference to `host_detect_local_cpu' gmake[2]: *** [xgcc] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/cross-gcc/work/build/gcc' gmake[1]: *** [all-gcc] Error 2 gmake[1]: Leaving directory `/usr/ports/devel/cross-gcc/work/build' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/devel/cross-gcc. *** Error code 1 Am I missing something? Interestingly I find no open bug reports whatsoever on cross-gcc ___ 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"
