Re: non-WWW calendar/diary software
> 2013-03-07 12:42, Wojciech Puchar skrev: > >anyone knows such a thing - with polish translation (or translations at > >all so i can translate)? preferably integrated with GNOME2, not a must, > >but DEFINITELY evolution bloatware. > > > >Something simple, just like gnote. > > > >I know davical+web browser and it works, but something that doesn't > >require browser would be much better. > > > > At a prompt type cal or ncal If you are not afraid of text user interfaces you also have deskutils/calcurse, with which you can do a bit more than cal or ncal. It has polish translation (unfinished so if you want to help), and the good point is that I am the author of the project and also the port maintainer so if you have issues you know who to ask ;) Regards, Frederic ___ 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: non-WWW calendar/diary software
2013-03-07 22:03, Wojciech Puchar skrev: I have not tried it, but how about the Lightning extension for Thunderbird? (It's an option in make config; I think it's on by default.) tried. if you like CPU always utilized - it is OK ;) Of course one want that. A turned off cpu is of no use. ___ 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: xbmc and poudriere compile error
2013/3/7 Mickaël Maillot > Hi, > > 2013/3/6 Wolfgang Riegler > >> Hi, >> >> I have problems compiling xbmc with poudriere-devel. >> >> Logfile says: >> DVDAudioCodecFFmpeg.cpp: In member function 'virtual int >> CDVDAudioCodecFFmpeg::Decode(BYTE*, int)': >> DVDAudioCodecFFmpeg.cpp:163: error: 'struct AVFrame' has no member named >> 'nb_samples' >> DVDAudioCodecFFmpeg.cpp: In member function 'void >> CDVDAudioCodecFFmpeg::ConvertToFloat()': >> DVDAudioCodecFFmpeg.cpp:208: error: 'struct AVFrame' has no member named >> 'nb_samples' >> gmake[1]: *** [DVDAudioCodecFFmpeg.o] Error 1 >> gmake: *** [xbmc/cores/dvdplayer/DVDCodecs/Audio/Audio.a] Error 2 >> *** [do-build] Error code 1 >> >> >> >> I tried several options, EXTERNAL_FFMPEG, NONFREE and LIBBLURAY on and >> off, but no changes. I also tried compiling without CCACHE >> >> Poudriere uses a FreeBSD 9.1-RELEASE AMD64 Jail. >> >> >> >> Any help is appreciated, thanks in advance. >> >> kind regards >> >> Wolfgang Riegler >> ___ >> 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" >> > > which ffmpeg port are installed ? i think multimedia/ffmpeg can conflict > with xbmc build. > Also: can you try my last patch from PR ports/175933 ? ___ 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: non-WWW calendar/diary software
2013-03-07 12:42, Wojciech Puchar skrev: anyone knows such a thing - with polish translation (or translations at all so i can translate)? preferably integrated with GNOME2, not a must, but DEFINITELY evolution bloatware. Something simple, just like gnote. I know davical+web browser and it works, but something that doesn't require browser would be much better. At a prompt type cal or ncal ___ 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: non-WWW calendar/diary software
El día Thursday, March 07, 2013 a las 10:06:40PM +0100, Wojciech Puchar escribió: > quite good at first glance. at least complete, but english only. > > i will do a translation if not seeing anything better I remember remotely that there are languages to be installed, maybe not in the ports... I used it already before in Linux matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ 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: fetchmail/sendmail: Domain of sender address does not exist
Date: Thu, 07 Mar 2013 20:07:45 +0100
From: Matthias Andree
To: freebsd-ports@freebsd.org
Subject: Re: fetchmail/sendmail: Domain of sender address does not exist
Cc: "fetchmail-us...@lists.berlios.de"
(Since freebsd-ports is a public list, too, I am
copying to fetchmail-users mailing list for future reference.
Note that the fetchmail lists only permit subscribers to post.)
Am 07.03.2013 16:12, schrieb Anton Shterenlikht:
> I see e.g.:
>
> fetchmail: IMAP> A0021 FETCH 14 RFC822.HEADER
> fetchmail: IMAP< * 14 FETCH (RFC822.HEADER {4833}
> reading message me...@epo.bris.ac.uk:14 of 14 (4833 header octets)
> fetchmail: SMTP> MAIL
FROM: BODY=8BITMIME SIZE=5930
> fetchmail: SMTP< 553 5.1.8
... Domain of sender address
fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
> fetchmail: SMTP error: 553 5.1.8
... Domain of sender address
fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
> fetchmail: SMTP> RSET
> fetchmail: SMTP< 250 2.0.0 Reset state
>
> fetchmail: IMAP< )
> fetchmail: IMAP< A0021 OK Completed (0.000 sec)
>
> not flushed
>
> I'm also confused by this section of fetchmail
> man page:
>
> *quote*
> SMTP/ESMTP ERROR HANDLING
>Besides the spam-blocking described above, fetchmail takes
special
>actions on the following SMTP/ESMTP error responses
> ...
>
>553 (invalid sending domain)
> Delete the message from the server. Don't even try
to send
> bounce-mail to the originator.
> *end quote*
>
> I do get error 553 here, but the emails are not
> deleted from the server. I tried running fetchmail
> dosens of times, but this email (and others, about 15
> in total), just wouldn't go away, and I cannot
> get those either.
>
> Maybe I should ask in fetchmail lists.
Indeed you should.
However, look for "softbounce" in the manual page, it is on by default
in fetchmail versions >= 6.3.10 and < 7.0.0 (not yet released) to avoid
mail loss.
--nosoftbounce on the command line, or "set no softbounce" early in the
.fetchmailrc will cause fetchmail to delete such messages (I should add
a pointer to that section).
I will add a pointer to these options to the quoted section, though, to
appear in v6.3.25.
HTH
Matthias
Thank you for the reply.
I've forgotten that I'm actually subscribed to fetchmail-users.
Anton
___
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: non-WWW calendar/diary software
I have not tried it, but how about the Lightning extension for Thunderbird? (It's an option in make config; I think it's on by default.) tried. if you like CPU always utilized - it is OK ;) -- Daniel Nebdal On Thu, Mar 7, 2013 at 12:42 PM, Wojciech Puchar wrote: anyone knows such a thing - with polish translation (or translations at all so i can translate)? preferably integrated with GNOME2, not a must, but DEFINITELY evolution bloatware. Something simple, just like gnote. I know davical+web browser and it works, but something that doesn't require browser would be much better. ___ 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: fetchmail/sendmail: Domain of sender address does not exist
(Since freebsd-ports is a public list, too, I am
copying to fetchmail-users mailing list for future reference.
Note that the fetchmail lists only permit subscribers to post.)
Am 07.03.2013 16:12, schrieb Anton Shterenlikht:
> I see e.g.:
>
> fetchmail: IMAP> A0021 FETCH 14 RFC822.HEADER
> fetchmail: IMAP< * 14 FETCH (RFC822.HEADER {4833}
> reading message me...@epo.bris.ac.uk:14 of 14 (4833 header octets)
> fetchmail: SMTP> MAIL FROM:
> BODY=8BITMIME SIZE=5930
> fetchmail: SMTP< 553 5.1.8
> ... Domain of sender
> address fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
> fetchmail: SMTP error: 553 5.1.8
> ... Domain of sender
> address fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
> fetchmail: SMTP> RSET
> fetchmail: SMTP< 250 2.0.0 Reset state
>
> fetchmail: IMAP< )
> fetchmail: IMAP< A0021 OK Completed (0.000 sec)
>
> not flushed
>
> I'm also confused by this section of fetchmail
> man page:
>
> *quote*
> SMTP/ESMTP ERROR HANDLING
>Besides the spam-blocking described above, fetchmail takes special
>actions on the following SMTP/ESMTP error responses
> ...
>
>553 (invalid sending domain)
> Delete the message from the server. Don't even try to send
> bounce-mail to the originator.
> *end quote*
>
> I do get error 553 here, but the emails are not
> deleted from the server. I tried running fetchmail
> dosens of times, but this email (and others, about 15
> in total), just wouldn't go away, and I cannot
> get those either.
>
> Maybe I should ask in fetchmail lists.
Indeed you should.
However, look for "softbounce" in the manual page, it is on by default
in fetchmail versions >= 6.3.10 and < 7.0.0 (not yet released) to avoid
mail loss.
--nosoftbounce on the command line, or "set no softbounce" early in the
.fetchmailrc will cause fetchmail to delete such messages (I should add
a pointer to that section).
I will add a pointer to these options to the quoted section, though, to
appear in v6.3.25.
HTH
Matthias
___
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: Call for test and review net/freerdp 1.0.2 (was: Re: please update net/freerdp)
I did it myself as nobody seems to be interested in updating freerdp. It is available on my redports repository. It looks fine but probably still has some point to improve. Please let me know if you find any problem on my port. https://svn.redports.org/meta/net/freerdp/ In the Makefile, OPTIONS_DEFAULT is spelled as "OPTIONS_DEFUALT". That probably needs to be fixed. -Kurt ___ 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"
Call for test and review net/freerdp 1.0.2 (was: Re: please update net/freerdp)
I did it myself as nobody seems to be interested in updating freerdp. It is available on my redports repository. It looks fine but probably still has some point to improve. Please let me know if you find any problem on my port. https://svn.redports.org/meta/net/freerdp/ Regards, PS: I tried to build it on redports but it just says "finished". What's going non redports? https://redports.org/buildarchive/20130307162600-4637/ 2013-02-28 10:44 meta wrote: Whould someone update net/freerdp? The latest release is 1.0.2. I asked maintainer to update in private email but no reply almost 5 months. -- `whois vmeta.jp | nkf -w` meta ___ 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: (unknown)
07.03.2013 17:38, Auld Besom: Firefox v19, built from a freshly-updated ports tree under xfce4 and 8.3 generic, crashes the moment I try to enter a url in the edit box. The situation seems to be getting worse with each release. 3.6.25 wouldn't let me log into disqus so that I could post at commondreams, but otherwise seemed to work correctly. v10, installed as a package, had the same problem plus others that I can't now remember, prompting me to upgrade to 17 v17 had the same problem, plus it would crash unexpectedly v18 had the same problem, plus it would crash unexpectedly and, seemingly, more frequently v19 probably has the same problem, but since it crashes when I try to type in a url, I can't be sure. The build (I just rebuilt it a few minutes ago) reported no errors, and running pkg_libchk also returned nothing. I wonder whether being pieced together from 133 components has any significance. Does `kldload sem` fixes anything for you? -- Sphinx of black quartz, judge my vow. ___ 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"
[no subject]
Firefox v19, built from a freshly-updated ports tree under xfce4 and 8.3 generic, crashes the moment I try to enter a url in the edit box. The situation seems to be getting worse with each release. 3.6.25 wouldn't let me log into disqus so that I could post at commondreams, but otherwise seemed to work correctly. v10, installed as a package, had the same problem plus others that I can't now remember, prompting me to upgrade to 17 v17 had the same problem, plus it would crash unexpectedly v18 had the same problem, plus it would crash unexpectedly and, seemingly, more frequently v19 probably has the same problem, but since it crashes when I try to type in a url, I can't be sure. The build (I just rebuilt it a few minutes ago) reported no errors, and running pkg_libchk also returned nothing. I wonder whether being pieced together from 133 components has any significance. ___ 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: fetchmail/sendmail: Domain of sender address does not exist
From free...@edvax.de Thu Mar 7 14:14:34 2013
On Thu, 7 Mar 2013 09:40:47 GMT, Anton Shterenlikht wrote:
> How do I set fetchmail and sendmail to fetch
> such emails?
Maybe it helps if you add the options "fetchall flush" to
your .fetchmailrc configuration file?
No that does not help.
I've had a similar
problem some years ago and I think this was the solution.
See "man fetchmail" for the corresponding command line
options (and you could probably add -v to see what's
actually going on).
I see e.g.:
fetchmail: IMAP> A0021 FETCH 14 RFC822.HEADER
fetchmail: IMAP< * 14 FETCH (RFC822.HEADER {4833}
reading message me...@epo.bris.ac.uk:14 of 14 (4833 header octets)
fetchmail: SMTP> MAIL FROM:
BODY=8BITMIME SIZE=5930
fetchmail: SMTP< 553 5.1.8
... Domain of sender address
fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
fetchmail: SMTP error: 553 5.1.8
... Domain of sender address
fsde_1e2ciclos@mrsevangelineschafers.localdomain does not exist
fetchmail: SMTP> RSET
fetchmail: SMTP< 250 2.0.0 Reset state
fetchmail: IMAP< )
fetchmail: IMAP< A0021 OK Completed (0.000 sec)
not flushed
I'm also confused by this section of fetchmail
man page:
*quote*
SMTP/ESMTP ERROR HANDLING
Besides the spam-blocking described above, fetchmail takes special
actions on the following SMTP/ESMTP error responses
...
553 (invalid sending domain)
Delete the message from the server. Don't even try to send
bounce-mail to the originator.
*end quote*
I do get error 553 here, but the emails are not
deleted from the server. I tried running fetchmail
dosens of times, but this email (and others, about 15
in total), just wouldn't go away, and I cannot
get those either.
Maybe I should ask in fetchmail lists.
Thanks
Anton
___
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: xbmc and poudriere compile error
Hi, 2013/3/6 Wolfgang Riegler > Hi, > > I have problems compiling xbmc with poudriere-devel. > > Logfile says: > DVDAudioCodecFFmpeg.cpp: In member function 'virtual int > CDVDAudioCodecFFmpeg::Decode(BYTE*, int)': > DVDAudioCodecFFmpeg.cpp:163: error: 'struct AVFrame' has no member named > 'nb_samples' > DVDAudioCodecFFmpeg.cpp: In member function 'void > CDVDAudioCodecFFmpeg::ConvertToFloat()': > DVDAudioCodecFFmpeg.cpp:208: error: 'struct AVFrame' has no member named > 'nb_samples' > gmake[1]: *** [DVDAudioCodecFFmpeg.o] Error 1 > gmake: *** [xbmc/cores/dvdplayer/DVDCodecs/Audio/Audio.a] Error 2 > *** [do-build] Error code 1 > > > > I tried several options, EXTERNAL_FFMPEG, NONFREE and LIBBLURAY on and > off, but no changes. I also tried compiling without CCACHE > > Poudriere uses a FreeBSD 9.1-RELEASE AMD64 Jail. > > > > Any help is appreciated, thanks in advance. > > kind regards > > Wolfgang Riegler > ___ > 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" > which ffmpeg port are installed ? i think multimedia/ffmpeg can conflict with xbmc build. ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ cad/leocad | 0.79.2 | 0.79.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ 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: non-WWW calendar/diary software
El día Thursday, March 07, 2013 a las 12:42:34PM +0100, Wojciech Puchar escribió: > anyone knows such a thing - with polish translation (or translations at > all so i can translate)? preferably integrated with GNOME2, not a must, > but DEFINITELY evolution bloatware. > > Something simple, just like gnote. > > I know davical+web browser and it works, but something that doesn't > require browser would be much better. There is plan-1.10.1 An X/Motif schedule planner with calendar in the ports; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ 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: non-WWW calendar/diary software
I have not tried it, but how about the Lightning extension for Thunderbird? (It's an option in make config; I think it's on by default.) -- Daniel Nebdal On Thu, Mar 7, 2013 at 12:42 PM, Wojciech Puchar wrote: > anyone knows such a thing - with polish translation (or translations at all > so i can translate)? preferably integrated with GNOME2, not a must, but > DEFINITELY evolution bloatware. > > Something simple, just like gnote. > > I know davical+web browser and it works, but something that doesn't require > browser would be much better. > > ___ > 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: [HEADS UP] FreeBSD Ports tree has been tagged with RELEASE_7_EOL
On 03/07/13 11:08, Jan Beich wrote:
> Thomas Abthorpe writes:
>
>> - We do not require committers/maintainers to support 7.x, although ports
>> will need to be marked as BROKEN/IGNORE if they do not build/run.
>
> Why not add an entry to UPDATING and teach portsnap(8) about EOLTIME?
>
> # a sample text based on freebsd-update(8)
> if [ ${EOLTIME} -lt ${NOWTIME} ]; then
> echo
> cat <<-EOF
> WARNING: `uname -sr` HAS PASSED ITS END-OF-LIFE DATE.
> Any ports issues discovered after `date -r ${EOLTIME}`
> specific to your version may not be corrected.
> EOF
> return 1
> fi
>
> For one, not reading UPDATING pretty much guarantees running into an
> issue at some point anyway compared to not reading ports-announce@ list.
Adding a similar warning to bsd.port.mk was propopsed on the
freebsd-emulation list, at
http://lists.freebsd.org/pipermail/freebsd-emulation/2013-March/010463.html
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"
non-WWW calendar/diary software
anyone knows such a thing - with polish translation (or translations at all so i can translate)? preferably integrated with GNOME2, not a must, but DEFINITELY evolution bloatware. Something simple, just like gnote. I know davical+web browser and it works, but something that doesn't require browser would be much better. ___ 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: [HEADS UP] FreeBSD Ports tree has been tagged with RELEASE_7_EOL
Thomas Abthorpe writes:
> - We do not require committers/maintainers to support 7.x, although ports
> will need to be marked as BROKEN/IGNORE if they do not build/run.
Why not add an entry to UPDATING and teach portsnap(8) about EOLTIME?
# a sample text based on freebsd-update(8)
if [ ${EOLTIME} -lt ${NOWTIME} ]; then
echo
cat <<-EOF
WARNING: `uname -sr` HAS PASSED ITS END-OF-LIFE DATE.
Any ports issues discovered after `date -r ${EOLTIME}`
specific to your version may not be corrected.
EOF
return 1
fi
For one, not reading UPDATING pretty much guarantees running into an
issue at some point anyway compared to not reading ports-announce@ list.
___
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: Dropbox on FreeBSD
On Wed, 06 Mar 2013 21:31:10 -0500 Lee Dilkie articulated: > On 3/6/2013 6:57 PM, Wojciech Puchar wrote: > >> Dropbox is a good service. You put files in a folder and it > >> automatically synchs them across multiple devices. > > > > someone else service? not mine - i mean dropbox server installed by > > me? > > > > just one another way to control people. > > Control people? How do they "control people"? Don't encourage him Lee. You will only receive convoluted verbiage for your trouble. Unfortunately, there is a small but vocal group that suffers from "Neophobia". There is no known cure. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: regression: lang/gcc47, gcc48 on amd64: configure: error: cannot compute suffix of object files: cannot compile
On 03/07/13 08:31, Anton Shterenlikht wrote: > > yep: > > ===>>> Upgrade of gcc-4.8.0.20130210 to gcc-4.8.0.20130303 complete > > So, are these options in /etc/make.conf harmful: > > #CMAKE_ARGS+=-DCMAKE_COLOR_MAKEFILE=off > #CFLAGS+= -fno-color-diagnostics > #CXXFLAGS+= -fno-color-diagnostics > Just som idle speculation here. Since gcc bootstraps itself, meaning that the final copy of gcc you install is built by gcc (this is true for lang/gcc47 and lang/gcc48, but not lang/gcc iirc). This gcc used will probably be confused about those arguments, at least if they are clang specific... Also, what is in config.log of the failed compiles? Regards! -- Niclas ___ 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: Help installing font in virtual machine
just copy right file from /usr/local/lib/X11/fonts On Tue, 5 Mar 2013, AN wrote: This is a bit off topic for FreeBSD, but I would appreciate any help. I would like to install a font into a virtual machine, the font comes by default in Xorg on FreeBSD it is called Terminal. The font is also installed by default in opensuse and it is called DEC Terminal font. Could somebody tell me which package provides the font, and what package is needed or instructions to install it in a LinuxMint virtual machine. Any help is appreciated, thanks in advance. ___ 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"
FreeBSD ports which are currently marked forbidden
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: 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=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ 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 which are currently marked broken
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 7.x/8.x/9.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: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gdam portname: audio/hydrogen broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=hydrogen portname: audio/milkytracker broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=milkytracker portname: audio/py-tagpy broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20121104103132/py27-tagpy-0.94.8.log (_Nov__4_17:22:02_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-tagpy portname: benchmarks/mdtest broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=mdtest portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31 portname: cad/meshlab broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/meshlab-1.2.3_2.log (_Jul_16_09:33:26_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=meshlab portname: chinese/CNS11643-font broken because: checksum mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/zh-CNS11643-font-98.1.log (_Jul_16_09:35:05_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=CNS11643-font portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con portname: chinese/bitchx broken because: patch reject build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/zh-BitchX-1.2_5.log (_Oct__2_08:24:08_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=bitchx portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hso-kmod portname: comm
FreeBSD unmaintained ports which are currently marked broken
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 7.x/8.x/9.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: benchmarks/mdtest broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=mdtest portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con portname: chinese/bitchx broken because: patch reject build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/zh-BitchX-1.2_5.log (_Oct__2_08:24:08_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=bitchx portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=dsss portname: devel/libYGP broken because: Does not build with recent boost build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libYGP portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads portname: devel/p5-Dialog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Dialog portname: devel/py-extended_threading broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-extended_threading portname: devel/ros-common broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/powerpc-errorlogs/e.8.20120528024705/ros-common-1.4.3_1.log (_Aug__9_01:19:13_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ros-common portname: devel/ros_comm broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ros_comm portname: devel/subcommander2 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=subcommander2 portname: dns/opendd broken because: segfaults upon use build errors: none. overview:
