Re: What is: py3kplist???

[Raphael Kubo da Costa]

On 9/1/20 8:13 PM, Willem Jan Withagen wrote:
> Hi,
> 
> In my ceph port one of the maintainers added this to
> 
> USE_PYTHON= cython py3kplist
> 
> But I'm trying to find out what it does?
> And it is not (yet) on the USE_PYTHON page in the ports handbook.

It's documented in Mk/Uses/python.mk:

#   py3kplist   - Automatically generates Python 3.x compatible
# __pycache__ entries from a Python 2.x packaging list
# when defined. Use this for ports that do *not* use
# standard Python packaging mechanisms such as
# distutils, and support *both* Python 2.x and 3.x.
# Not needed, if USE_PYTHON=autoplist is set.

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

Re: FreeBSD Port: qt5-network-5.12.1

[Raphael Kubo da Costa]

On 3/30/19 10:49 PM, Davide Beatrici wrote:
> Greetings,
> 
> I would like to inform you
> about https://bugreports.qt.io/browse/QTBUG-74844.
> 
> A patch is attached to the bug report.
> 
> Best regards,
> Davide

Thanks for the heads-up. Please note that you are a lot more likely to
get your patch reviewed and integrated if you follow Qt's contribution
guidelines: https://wiki.qt.io/Qt_Project_Guidelines
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: QT5

[Raphael Kubo da Costa]

The Doctor  writes:

> When will the QT5 team go over to QT5.10 ?

It's still unclear. Most of the work is done in the qt-5.10 branch on
GitHub (https://github.com/freebsd/freebsd-ports-kde), but, as usual, we
still need to get qt5-webengine to build, and that takes a lot of time
and isn't fun at all.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5-qmake failed update

[Raphael Kubo da Costa]

Walter Schwarzenfeld  writes:

> Another different error:
>
> ===>  Patching for qt5-multimedia-5.9.3
> ===>  Applying extra patch
> /usr/ports/multimedia/qt5-multimedia/files/extrapatch-no-gstreamer
> No such line 17 in input file, ignoring
> 1 out of 1 hunks failed--saving rejects to qtmultimedia.pro.rej
> *** Error code 1

Fixed in r458338, thanks for the report.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5-qmake failed update

[Raphael Kubo da Costa]

Walter Schwarzenfeld  writes:

> with
>
> ===>  Applying FreeBSD patches for qt5-qmake-5.9.3
> /usr/bin/sed -i "" -e "/DEFAULT_LIBDIRS=/ s,\"n,n/usr/local/lib&,"
> /ram/usr/ports/devel/qt5-qmake/work/qtbase-opensource-src-5.9.3/configure
> ===>   qt5-qmake-5.9.3 depends on package: pkgconf>=1.3.0_1 - found
> ===>  Configuring for qt5-qmake-5.9.3
> /bin/mkdir -p 
> /ram/usr/ports/devel/qt5-qmake/work/qtbase-opensource-src-5.9.3
> echo 'CMAKE_MODULE_TESTS = -' >
> /ram/usr/ports/devel/qt5-qmake/work/qtbase-opensource-src-5.9.3/.qmake.cache
> echo 'QMAKE_LIBDIR_FLAGS =
> -L/ram/usr/ports/devel/qt5-qmake/work/qtbase-opensource-src-5.9.3/lib' 
>>> 
> /ram/usr/ports/devel/qt5-qmake/work/qtbase-opensource-src-5.9.3/.qmake.cache
> Syntax error: ")" unexpected (expecting "then")
> *** Error code 2

Fixed in r458339, thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports' QT5_USE assumes qt5-*, but build links executables to a specific minor version 5.7.*

[Raphael Kubo da Costa]

Yuri  writes:
> I had this problem: system had the older qt5-*-5.6.1 version. I installed
> qbittorrent using pkg. qbittorrent then failed saying it can't find the Qt_5.7
> tag.
>
> QT5_USE makes sure qt5-* dependencies exist, but the actual dependency is a
> specific qt5 minor version. pkg therefore installs such port but it then 
> fails.
>
> Is there any solution to this problem? Are qt versions with different minor
> numbers (qt5-*-5.6 and qt5-*-5.7) really incompatible? This might be a bug in
> the qt build process that it requires the minor version match.

Was qbittorrent built with Qt 5.7? Qt only guarantees backwards
compatibility, so qbittorrent built with Qt 5.6 would continue working
if you have Qt 5.7+ installed, not the other way around.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New Updates to KDE break kde4-workspace on current amd64

[Raphael Kubo da Costa]

Michael Butler  writes:

> Seems we have another path-related problem when pulseaudio is enabled in
> kde-runtime (-lcanberra):

Thanks for the report, I've fixed this code path in r437146.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New Updates to KDE break kde4-workspace on current amd64

[Raphael Kubo da Costa]

Manfred Antar  writes:

> The new updates to kdelibs kde-runtime and others break build of 
> kde4-worspace:

Thanks for the report. We were aware of the breakage, and as of r437053
everything _should_ be back to normal (I'm still testing some ports that
were blocked by kde4-workspace).
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:

> On 19/02/2017 13:56, Raphael Kubo da Costa wrote:
>
>> tech-lists  writes:
>> 
>>> Shall I try building qt5-concurrent again?
>> 
>> Yes, please.
>
> still failing, unfortunately. I've posted the script log here:
>
> http://www.zyxst.net/~bofh/logs/qt5c6.txt

/usr/local/bin/ld.gold: error: cannot open 
/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/lib/libQt5Core.so:
 No such file or directory

I think this indicates the symlink above is broken, and your
devel/qt5-core has not been updated to 5.7.1 yet.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:

> Shall I try building qt5-concurrent again?

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

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:

> On 19/02/2017 13:01, Raphael Kubo da Costa wrote:
>
>> The output looks like Qt4's qmake, not Qt5's. Can you run
>> "/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake
>> -v" and paste the output?
>
> #
> /storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake
> -v
> QMake version 3.0
> Using Qt version 5.6.2 in /usr/local/lib

Hmm, the -qtconf option that it's complaining about was introduced in Qt
5.7.0. devel/qt5-qmake should have been updated automatically before
qt5-concurrent.

Can you make sure qt5-qmake (which used to be called devel/qmake5) is at
5.7.1 before updating these other Qt5 ports?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:

> Hi, here's the output:
>
> # pwd
> /storage/usr/ports/devel/qt5-concurrent
>
> # make WANT_QT_VERBOSE_CONFIGURE=YES
> ***Unknown option -qtconf
> Usage:
> /storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake
> [mode] [options] [files]

The output looks like Qt4's qmake, not Qt5's. Can you run
"/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/bin/qmake
-v" and paste the output?

Are you setting QT_SELECT to a different value or changing any of
misc/qtchooser's settings?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:

> Hi,
>
> On 19/02/2017 11:51, Raphael Kubo da Costa wrote:
>
>> Can you send config.log to the list? From the error message it's not
>> clear what exactly is wrong with the mkspec, of if the problem's really
>> with the mkspec at all.
>
> Weirder and weirder. There is no config.log present.

The message mentioning config.log is automatic and comes from the ports
framework. In my recollection Qt's configuration process did create one
though, which is why I suggested trying to get that.

Can you try building qt5-concurrent with the WANT_QT_VERBOSE_CONFIGURE
make variable set instead?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5 fails to build

[Raphael Kubo da Costa]

tech-lists  writes:
> Running configuration tests...
> Failed to process makespec for platform
> '/usr/local/lib/qt5/mkspecs/freebsd-clang'
>
> Turn on verbose messaging (-v) to see the final report.
>
> ===> Script "configure" failed unexpectedly.
> Please report the problem to k...@freebsd.org [maintainer] and attach the
> "/storage/usr/ports/devel/qt5-concurrent/work/qtbase-opensource-src-5.7.1/config.log"

Can you send config.log to the list? From the error message it's not
clear what exactly is wrong with the mkspec, of if the problem's really
with the mkspec at all.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Fwd: 2017-02-18 Update to Qt 4 and Qt 5

[Raphael Kubo da Costa]

Robert Burmeister  writes:

> k...@freebsd.org is not accepting mail
>
>>  UPDATING
>>  Following what is already done in Qt 5, the Qt 4 ports no longer install
>>  their binaries into ${LOCALBASE}/bin (which is "/usr/local/bin" in most
>>  cases). Additionally, the "-qt4" suffix has been dropped from the file names
>>  of the binaries that had it, such as "qmake-qt4".
>>
>
> Could we have portupgrade instructions?

We'd be more than glad to add those if someone can provide them; I have
not used portupgrade myself since at least 2009, so it's hard for me to
provide any instructions.

> Neither QT4 nor QT5 will build on my FreeBSD 11 i386 system.

Can you clarify? What errors are you seeing?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cmake release builds don't disable assertions (NDEBUG)

[Raphael Kubo da Costa]

Michael Gmelin  writes:

> While debugging an unexpected assertion problem, I noticed that ports
> using cmake don't set -NDEBUG, even when building in Release mode.
>
> Is this intentional?

Is it the software you're porting that checks for DEBUG or some library
it uses?

CMake code should check for CMAKE_BUILD_TYPE and adjust the compiler
flags accordingly (if at all); so if the software itself is checking for
DEBUG but not passing (or omitting it) I'd say the bug is there, not in
Mk/Uses/cmake.mk.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Hash changes in the freebsd-ports GitHub mirror

[Raphael Kubo da Costa]

Hi all,

I tried running `git pull` a few minutes ago and had a ton of conflicts.

It turns out all hashes after c96fb0418e545a569b5975b4d878a30a948c29d5
("fix issues related with USES=fonts" from 2015-07-18, aka r392404) are
now different in all GitHub branches.

Is anyone else experiencing this? Was this change intentional?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: upgrade to devel/dbus breaks xfce4

[Raphael Kubo da Costa]

Aryeh Friedman  writes:

> After upgrading deval/dbus to dbus-1.10.12 xfce4 fails to start as a
> non-root user due to being unable to open/write to /etc/machine-id. I
> made a tempurary fix by touching /etc/machine-id and chmod'ing it to
> 777.

If the /etc/machine-id message you're getting looks like

D-Bus library appears to be incorrectly set up; failed to read
machine uuid: Failed to open "/etc/machine-id": No such file or
directory

it may be misleading as /etc/machine-id is a fallback if other files
were not found before (see bug 213540, for example).

Is dbus running when you try to launch XFCE?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5-webkit fails to build

[Raphael Kubo da Costa]

Michael Butler  writes:

> /usr/lib/libgcc_s.so: error: undefined reference to 'free'
> /usr/lib/libgcc_s.so: error: undefined reference to '__assert'
> /usr/lib/libgcc_s.so: error: undefined reference to 'fwrite'
> /usr/lib/libgcc_s.so: error: undefined reference to 'fflush'
> /usr/lib/libgcc_s.so: error: undefined reference to 'malloc'
> /usr/lib/libgcc_s.so: error: undefined reference to '__stderrp'
> /usr/lib/libgcc_s.so: error: undefined reference to 'snprintf'
> /usr/lib/libgcc_s.so: error: undefined reference to 'fprintf'
> /usr/lib/libgcc_s.so: error: undefined reference to 'memcpy'
> /usr/lib/libgcc_s.so: error: undefined reference to 'abort'
> /usr/lib/libgcc_s.so: error: undefined reference to 'memset'
> /usr/lib/libgcc_s.so: error: undefined reference to 'getenv'
> /usr/lib/libgcc_s.so: error: undefined reference to 'dladdr'
> /usr/lib/libgcc_s.so: error: undefined reference to 'mprotect'

This looks unrelated to qt5-webkit; are you building your own world?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: qt5-webkit fails to build

[Raphael Kubo da Costa]

Michael Butler  writes:

> It seems to fail because the qmake config can't find libicu ..

You need to find out why exactly it's not finding ICU. Try going to the
build directory (work/.build) and check config.log. It's also possible
to reproduce the test by cd'ing to
work/.build/Tools/qmake/config.tests/icu and calling gmake from there.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fontconfig update uglifies fonts

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:
> You can either change the HINTING option when building the port or
> create a ~/.config/fontconfig/fonts.conf with something like this:
>
> 
> 
> 
>  
>   
>hintnone
>   
>  
> 

"hintnone" was just an example and is likely the opposite of what you
want. In your specific case you probably need "hintmedium" or
"hintfull".
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: fontconfig update uglifies fonts

[Raphael Kubo da Costa]

"Russell L. Carter"  writes:

> Hi,
>
> On 10/stable amd64, the recent fontconfig update makes the fonts used
> in thunderbird, firefox, (u)xterm, and emacs quite a bit uglier.  The
> font strokes seem to be thicker and fuzzier.  Emacs I fixed by
> reinstalling bitstream-vera, but (u)xterm use that and they're still
> broken.  I ran fc-cache -f, but no change.  I turned off antialiasing
> via /usr/local/etc/fonts/local.conf and that made the strokes nice and
> thin but overall even uglier.
>
> Any ideas/pointers on how to fix this?

This is likely caused by the fact that the new fontconfig version allows
one to choose the default hinting style and defaults to "slight"; from
your description it looks like were used to a different value.

You can either change the HINTING option when building the port or
create a ~/.config/fontconfig/fonts.conf with something like this:




 
  
   hintnone
  
 

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

Re: Need some help with c++/qt5 code

[Raphael Kubo da Costa]

Shane Ambler  writes:

>> I agree. Maybe using Q_GLOBAL_STATIC helps?
>>
>> - Remove m_table from TPanelFactory.
>> - In pane.cpp, you do something like this:
>>
>>typedef QMap PanelMapType;
>>Q_GLOBAL_STATIC(PanelMapType, s_panelMap);
>>
>>you then need to replace uses of m_table with s_panelMap and use
>>s_panelMap->operation() instead of m_table.operation().
>
> Thanks that does the trick.

I'm glad it worked :-) It's a good candidate for upstreaming if you're
working with them.

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

Re: Need some help with c++/qt5 code

[Raphael Kubo da Costa]

Dimitry Andric  writes:

> On 14 Apr 2016, at 13:58, Shane Ambler  wrote:
>> 
>> Hi there, while I am comfortable with c and python, I only know a little
>> c++ and could use some help.
> ...
>> class TPanelFactory
>> {
>>QString m_panelType;
>>static QMap m_table;
>> 
>> public:
>>TPanelFactory(QString panelType);
>>~TPanelFactory();
>> 
>>QString getPanelType() const { return m_panelType; }
>> 
>>virtual void initialize(TPanel *panel) = 0;
>>virtual TPanel *createPanel(QWidget *parent);
>>static TPanel *createPanel(QWidget *parent, QString panelType);
>> };
>> 
>> m_table is then in the source file as
>> 
>> QMap TPanelFactory::m_table;
>> 
>> The segfault happens in the constructor -
>> 
>> TPanelFactory::TPanelFactory(QString panelType)
>>: m_panelType(panelType)
>> {
>>assert(m_table.count(panelType) == 0);
>>m_table[m_panelType] = this;
>> }
>> 
>> the last line causes the segfault, if I comment it out then main() is
>> entered, but I expect removing that line will bite back soon enough.
>> 
>> How can I get this working?
>> 
>> Why would this fail on FreeBSD but not OSX or windows?
>
> Most likely the program depends on the initialization order of global
> constructors.  This is bad practice, and should be avoided.

I agree. Maybe using Q_GLOBAL_STATIC helps?

- Remove m_table from TPanelFactory.
- In pane.cpp, you do something like this:

  typedef QMap PanelMapType;
  Q_GLOBAL_STATIC(PanelMapType, s_panelMap);

  you then need to replace uses of m_table with s_panelMap and use
  s_panelMap->operation() instead of m_table.operation().

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

Re: Is the kmymoney port broken?

[Raphael Kubo da Costa]

Christian Baer  writes:

> I rebuilt the kdelibs from the ports and did a make reinstall. After
> that I rebuilt KMymoney and the install worked fine. Thanks for your
> help!

I'm glad it worked. Feel free to also file a bug via bugs.freebsd.org
about KBANKING option not being on by default (I personally would rather
have fewer options in kmymoney and just always enable this).

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

Re: Is the kmymoney port broken?

[Raphael Kubo da Costa]

CC'ing the list again.

Christian Baer  writes:
> On 03/22/16 11:05, Raphael Kubo da Costa wrote:
>
> Hello Raphael, thanks for your reply!
>
>> Do you have kdelibs-4.14.3_6 installed? My initial guess is that you
>> haven't recompiled kdelibs after its header locations were changed and
>> those files are still in
>> ${PORTSDIR}/work/stage/usr/local/include/kmymoney/ instead of
>> include/kde4/kmymoney.
>
> That is a possibility. :-)
>
> I actually installed KDE via 'pkg install', along with just about
> everything else I have running on this machine at the moment - and I
> recently (not quite two weeks ago) upgraded everything, including KDE4.
>
> The ports tree I rebuilt completely (rm -rf /usr/ports and svn checkout)
> before compiling KMymoney. So if it the kdelibs were built in the
> process, they should have been built with new settings. However, it is
> possible that they were already installed.

It's easy to check: pkg info kdelibs. The version field should say
4.14.3_6. If you've just built kmymoney I'd assume it would require that
new version though. Please also make sure your Mk/bsd.kde4.mk is at
r411201 or later.

> Sorry about the dumb question (I'm just not so deep into this stuff):
> What do you mean with the header locations were changed. I am guessing
> this means the position within the directory-tree. Is that correct? And
> if so, can I just change it by recompiling and reinstalling the kdelibs
> without screwing up other stuff currently installed?

Yes, I am referring to this commit I made a week ago:
<https://svnweb.freebsd.org/ports?view=revision&revision=411156>

Which made kdelibs (and several ports that depend on it) install its
headers into /usr/local/include/kde4 instead of /usr/local/include.

You can try recompiling x11/kdelibs4 after making sure both the port and
bsd.kde4.mk are at their latest versions, but I think it should have
already happened when you tried building kmymoney.

A few other things you can try in order to rule out other possibilities:
- After building kmymoney, run `find work -name importinterface.h' to
  check where the header was staged.
- See if resetting your build options (make rmconfig) makes any
  difference.

It would also be helpful if you could attach your whole build log if the
problem persists.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD ports you maintain which are out of date

[Raphael Kubo da Costa]

Ryan Steinmetz  writes:

> On (03/11/16 12:35), Raphael Kubo da Costa wrote:
>>Mathieu Arnold  writes:
>>> Someone already put:
>>>
>>> PORTSCOUT=  ignore
>>
>>I did that in r410199, and tried a different approach first in r410104.
>>It's not clear to me why these reports are still being sent.
>
> ignore:  Set to 1 to tell portscout not to do any version checking at
> all. Useful if, say, a particular port is not going to be
> updated ever again, yet portscout still finds files that look
> like updates.
>
> PORTSCOUT=ignore:1

Oops. I've committed this change in r410827, fingers crossed. Thanks for
the pointer.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD ports you maintain which are out of date

[Raphael Kubo da Costa]

Mathieu Arnold  writes:

> +--On 9 mars 2016 07:16:14 -0500 Ryan Steinmetz  wrote:
> | 
> | On (03/09/16 13:11), Mathieu Arnold wrote:
> |> Hi,
> |> 
> |> This really is getting annoying.
> |> 
> | 
> | You can control the behavior by setting portscout flags on the port:
> | 
> | http://portscout.freebsd.org/info/portscout-portconfig.txt
>
> Someone already put:
>
> PORTSCOUT=  ignore

I did that in r410199, and tried a different approach first in r410104.
It's not clear to me why these reports are still being sent.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: openblas 0.2.15,1 port broke build for BARCELONA AMD core

[Raphael Kubo da Costa]

Andrew Reilly  writes:
> Hi there,
>
> My portmsaster run just broke on the recent openblas upgrade, with version
> stamp in head/math/openblas/Makefile 409114 26-02-18 16:35:48Z rakuco. Now 
> that
> I’ve hacked on this to make it build, I remember having done something like
> this the last time, so perhaps nothing has actually changed in this respect,
> there’s just been a version increase that still doesn’t know about my CPU.
>
> My build/target machine is, according to sysctl:
> hw.machine: amd64
> hw.model: AMD A6-3500 APU with Radeon(tm) HD Graphics
> hw.ncpu: 3
>
> The auto-config system for openblas has determined that this is (in config.h):
> #define AMD_UNKNOWN
> but also
> #define CORE_BARCELONA
> #define CHAR_CORENAME “BARCELONA”
>
> So on the assumption that the AMD_UNKNOWN should be BARCELONA, I have tweaked
> cpuid_x86.c to add case 3 along with case 1 and case 10 in the 
> switch(exfamily)
> to return CPUTYPE_BARCELONA.
>
> I’m not sure if it wouldn’t have been better to slide that in with case 6,
> because model=1 and support_avx()->0, so that would have worked too.
>
> the full set of get_cputype() values for my machine are:
> family=0xf, exfamily=0x3, model=0x1, exmodel=0x0, support_avx=0
>
> The code in cpuid_x86.c thinks that NUM_CORES is 1, despite the sysctl
> information above, so I guess that only one core is going to be used, but 
> since
> this is not a high performance machine and is generally thermally challenged,
> I’m not too concerned about that. Just want it to build at all.
>
> With this couple of tweaks the math/openblas port seems to have built OK, so I
> hope that this change can be included in the port or the up-stream so that I
> don’t have to remember to do this all again next time!

Hi Andrew,

I don't maintain the openblas port, I just committed a patch for it that
was sent to Bugzilla.

This looks like a problem that should be reported upstream
(https://github.com/xianyi/OpenBLAS/issues), it's even possible it's
already been fixed in their git repository.

You can also file a bug in our bug tracker so the port maintainer can
take a look at this, but I don't think there's much he can do besides
relaying that information upstream.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: graphics/giflib: Update to 5.1.2_1 breaks GIF rendering in Konqueror

[Raphael Kubo da Costa]

Patrick Hess  writes:

> After upgrading graphics/giflib from 5.1.1 to 5.1.2_1, Konqueror won't
> display GIF images in web pages:
>
> http://www.phess.net/images/giflib-bug.png
>
> On the left hand side, with giflib 5.1.1, everything looks as expected.
> On the right hand side, after upgrading giflib to 5.1.2_1, none of the
> GIF icons are rendered correctly. Only the Fresh Ports logo and the two
> magnifying glass icons are still there (as they're JPEGs, not GIFs).
>
> I personally prefer using Konqueror over that obese Firefox for most of
> my web browsing, but it feels like I'm the only one. Is anybody else out
> there using Konqueror and can confirm (or disconfirm, for that matter)
> this behaviour?

It's weird, but it works fine here with an up-to-date ports tree, but I
build my own packages with Poudriere. I see a new kdelibs4 package was
generated in the cluster a couple of days ago, can you try reinstalling
to see if it was a matter of somehow giflib being originally updated
without triggering a rebuild of the kdelibs4 port caused it (it
shouldn't, I think)? Otherwise, do you get any useful messages on the
terminal when you open FreshPorts with khtml?

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

Re: Cannot build www/mod_dnssd with poudriere

[Raphael Kubo da Costa]

Wolfgang Riegler  writes:

>  o ./mod_dnssd.c && touch ./mod_dnssd.slo
> ./mod_dnssd.c:29:23: error: mod_unixd.h: No such file or directory
> ./mod_dnssd.c:911: warning: missing initializer
> ./mod_dnssd.c:911: warning: (near initialization for 'commands[8].func')

[...]

> ===>  Cleaning for ap22-mod_dnssd-0.6_12

mod_unixd.h is present in www/apache24, but not www/apache22, hence the
error. I'm not sure about the fix though? Is mod_dnssd supposed to work
with Apache 2.2?

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

Re: Cannot build www/mod_dnssd with poudriere

[Raphael Kubo da Costa]

(Sorry if a similar message shows up later, gmane didn't seem to deliver
my original reply)

Wolfgang Riegler  writes:
> ./mod_dnssd.c:29:23: error: mod_unixd.h: No such file or directory
> ./mod_dnssd.c:911: warning: missing initializer
> ./mod_dnssd.c:911: warning: (near initialization for 'commands[8].func')
[...]
> ===>  Cleaning for ap22-mod_dnssd-0.6_12

mod_unixd.h is only present in Apache 2.4, not 2.2. Is mod_dnssd
supposed to work with www/apache22?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: When is Qt-5.5 coming to ports?

[Raphael Kubo da Costa]

Olivier Duchateau  writes:

> 2016-01-02 21:46 GMT+01:00 Kurt Jaeger :
>>
>> Hi!
>>
>> > > Since it turned out that nobody was working on this, I ported qt-5.5.1
>> > > myself.
>> >
>> > What? o_O
>> >
>> > Qt 5.5.x is already ported, check the KDE devel repository.
>>
>> That's here, right ?
>>
>> https://freebsd.kde.org/area51.php
>
> Yes, it's right place. To test the latest releases of Qt and KDE
> Plasma, you must to go in plasma5 branch.

With my kde@ hat on, I apologize for the lack of response here. I tend
to check the kde-freebsd mailing list more often than this one, and then
forgot to answer here.

We've been working on 5.5.1 for a while now, and with the end of year
holidays I managed to get it working on all FreeBSD releases. I expect
to file an exp-run request and land it soon.

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

Re: Error Building devel/cmake

[Raphael Kubo da Costa]

Amit Sengupta  writes:

> [100%] Built target documentation
> Installing the project stripped...
> *** Signal 11

Something has crashed, but it's not clear what. Can you add --verbose to
CONFIGURE_ARGS in devel/cmake/Makefile and rebuild? Do you get any core
dumps with this crash?

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

Re: [kde-freebsd] problem with graphics/libkdcraw-kde4 after upgrade of libraw to libraw-0.16.2

[Raphael Kubo da Costa]

Gary Palmer  writes:

> On Mon, Jun 15, 2015 at 06:54:19PM +0100, Gary Palmer wrote:
>> Hi,
>> 
>> After the upgrade of libraw earlier in the month I've been unable to build
>> graphics/libkdcraw-kde4.  This is on 9.3-RELEASE-p13
>> 
>> Build log at the end
>> 
>> Anyone got any ideas?
>
>
> Never mind, it built last night.  No idea what changed

https://svnweb.freebsd.org/ports?view=revision&revision=389739 happened.
___
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: cmake build failure depending on liblzma

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Jim Pazarena  writes:
>
>> -- Looking for lzma_auto_decoder in /usr/local/lib/liblzma.so
>> -- Looking for lzma_auto_decoder in /usr/local/lib/liblzma.so - not found
>> -- Looking for lzma_easy_encoder in /usr/local/lib/liblzma.so
>> -- Looking for lzma_easy_encoder in /usr/local/lib/liblzma.so - not found
>> -- Looking for lzma_lzma_preset in /usr/local/lib/liblzma.so
>> -- Looking for lzma_lzma_preset in /usr/local/lib/liblzma.so - not found
>> -- Could NOT find LibLZMA (missing:  LIBLZMA_HAS_AUTO_DECODER
>> LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET) (found version
>> "5.0.5")
>> CMake Error at CMakeLists.txt:310 (message):
>>   CMAKE_USE_SYSTEM_LIBLZMA is ON but LibLZMA is not found!
>> Call Stack (most recent call first):
>>   CMakeLists.txt:488 (CMAKE_BUILD_UTILITIES)
>
> It should work if you remove archivers/lzmalib, whose liblzma.so is
> being picked up instead of base's liblzma.so.
>
> It's a workaround, I still need to think of a proper fix. Would you mind
> filing a PR about this?

I've committed a fix in r385307.

___
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: cmake build failure depending on liblzma

[Raphael Kubo da Costa]

Jim Pazarena  writes:

> -- Looking for lzma_auto_decoder in /usr/local/lib/liblzma.so
> -- Looking for lzma_auto_decoder in /usr/local/lib/liblzma.so - not found
> -- Looking for lzma_easy_encoder in /usr/local/lib/liblzma.so
> -- Looking for lzma_easy_encoder in /usr/local/lib/liblzma.so - not found
> -- Looking for lzma_lzma_preset in /usr/local/lib/liblzma.so
> -- Looking for lzma_lzma_preset in /usr/local/lib/liblzma.so - not found
> -- Could NOT find LibLZMA (missing:  LIBLZMA_HAS_AUTO_DECODER
> LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET) (found version
> "5.0.5")
> CMake Error at CMakeLists.txt:310 (message):
>   CMAKE_USE_SYSTEM_LIBLZMA is ON but LibLZMA is not found!
> Call Stack (most recent call first):
>   CMakeLists.txt:488 (CMAKE_BUILD_UTILITIES)

It should work if you remove archivers/lzmalib, whose liblzma.so is
being picked up instead of base's liblzma.so.

It's a workaround, I still need to think of a proper fix. Would you mind
filing a PR about this?

___
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: upgrading texlive broken due to cmake

[Raphael Kubo da Costa]

Will Parsons  writes:

> tex-kpathsea installed, but texlive-base didn't due to a failure to
> build the cmake dependency:
[...]
> ===>  Building for py27-sphinx-1.2.3
> running build
> running build_py
> running egg_info
> writing requirements to Sphinx.egg-info/requires.txt
> writing Sphinx.egg-info/PKG-INFO
> writing top-level names to Sphinx.egg-info/top_level.txt
> writing dependency_links to Sphinx.egg-info/dependency_links.txt
> writing entry points to Sphinx.egg-info/entry_points.txt
> reading manifest file 'Sphinx.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'doc/_build'
> writing manifest file 'Sphinx.egg-info/SOURCES.txt'
> cd /usr/ports/textproc/py-sphinx/work/Sphinx-1.2.3/build/lib &&
> /usr/bin/env
> PYTHONPATH=/usr/ports/textproc/py-sphinx/work/Sphinx-1.2.3/build/lib:/usr/local/lib/python2.7/site-packages
> /usr/local/bin/python2.7 -m sphinx.pycode.pgen2.driver -c 'import
> load_grammar'
> /usr/local/bin/python2.7: No module named jinja2

See how this is actually a failure to build the py-sphinx dependency.
Does the port build if you try to build it individually?

___
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 Port: qt5-webkit-5.3.2_2

[Raphael Kubo da Costa]

Will Brokenbourgh via freebsd-ports  writes:

> Dear Maintainers,
>
> Happy New Year!
>
> Browsers such as QupZilla and Rekonq use Qt5-Webkit for their
> functionality.
>
> There are websites that use WOFF (Web Open Font Format) however
> FreeBSD's Qt5-Webkit package appears to have an issue, which causes
> the websites to not display text at all.
>
> Please see the notice message below, which is displayed on the
> command-line when sites using WOFF are loaded:
>
>> WOFF support requires QtWebKit to be built with zlib support.
>>
> (/wrkdirs/usr/ports/www/webkit-qt5/work/qtwebkit-opensource-src-5.3.2/Source/WebCore/
>> platform/graphics/qt/FontCustomPlatformDataQt.cpp:60,
> WebCore::FontCustomPlatformData
>> *WebCore::createFontCustomPlatformData(WebCore::SharedBuffer *))
>
> Is it difficult or impossible to enable zlib support?  I would really
> like to use QupZilla with sites such as Outlook.com which currently
> doesn't work because of this issue.

I don't think it should be very difficult. Can you please file a PR
(https://bugs.freebsd.org/submit) and assign it to kde@?
___
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"

Custom PREFIX + USE_LDCONFIG=yes creates leftovers

[Raphael Kubo da Costa]

I've been testing cad/brlcad as part of my work to update CMake to
3.1.0. One thing I noticed with "poudriere bulk -t" (regardless of the
CMake version) is that it fails at the end with leftovers:

>> Error: Files or directories left over:
@dir /usr/local/libdata/ldconfig

This seems to be caused by brlcad's use of a custom PREFIX,

PREFIX?=${LOCALBASE}/${PORTNAME}
NO_MTREE=   yes

since USE_LDCONFIG causes a file to be created outside the PREFIX.

USE_LDCONFIG's documentation in bsd.port.mk indicates it's supposed to
write its files to ${PREFIX} instead of ${LOCALBASE}, but r357076 says
otherwise.

What's the right way to fix this?

___
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: Giving Up Maintainership

[Raphael Kubo da Costa]

Guido Falsi  writes:

> Unluckily upgrading it will be a problem since new version depends on
> Python QT5 libraries.
>
> So I take a chance to ask:
>
> Is there any active work on creating ports for these?
>
> Who should I talk about this to?

I don't think anyone is working on this at the moment. If you're willing
to do it, please keep kde@ in the loop, as we maintain the existing
PyQt4 ports and will probably end up either maintaining or touching the
Qt5 ports a lot.

___
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"

Dealing with a port being merged into another

[Raphael Kubo da Costa]

Hi everyone,

One of the changes we (kde@) have made in the upcoming Qt 5.3.2 update
is merging devel/qt5-qmldevtools into lang/qt5-qml.

I'd now like to know what needs to be done to make it easy to everyone
to upgrade their ports. By everyone I mean people using pkg as well as
people using port{master,upgrade,whatnot}, and by "make it easy" I mean
I don't want to have to write an UPDATING entry (that many people will
not read) that tells people they need to manually remove qt5-qmldevtools
from their systems before upgrading.

Do I need CONFLICTS_INSTALL? Will everything be handled automatically?
Is the UPDATING entry inevitable?
___
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: QtSerialPort?

[Raphael Kubo da Costa]

Larry Rosenman  writes:

> I'm working with the author of SleepyHead to port it to FreeBSD as
> well as it's current OS's of Linux/Mac OS X/Windows.
>
> It appears that the www/webkit-qt5 port does NOT install QtSerialPort.

They look like completely separate things to me, so I don't get why the
former should install the latter in the first place.

> Does anyone know which port(s) need to be modified to bring in this
> module?

This is an addon, right? A new port would probably need to be created
for it.

___
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: Problem with emacs

[Raphael Kubo da Costa]

Pete Carah  writes:

> In trying to build emacs (9.2-stable) (ports svn as of this morning, but
> one from a few weeks ago does this too) I get the following:
>
> checking for posix_openpt... yes
> checking for library containing tputs... no
> configure: error: The required function `tputs' was not found in any library.
> The following libraries were tried (in order):
>   libtinfo, libncurses, libterminfo, libtermcap, libcurses
> Please try installing whichever of these libraries is most appropriate
> for your system, together with its header files.
> For example, a libncurses-dev(el) or similar package.

What does config.log say?

___
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: Kalzium build fails (part of KDE4 port upgrade)

[Raphael Kubo da Costa]

Dave  writes:

> [ 48%] Generating parser.cmx
> [ 49%] Generating datastruct.cmx
> [ 50%] Generating chem.cmi
> [ 51%] Generating lexer.cmx
> [ 51%] Generating chem.cmx
> File "/usr/ports/science/kalzium/work/kalzium-4.12.5/src/solver/chem.ml", 
> line 1:
> Error: /usr/local/lib/ocaml/facile/facile.cmi
> is not a compiled interface for this version of OCaml.
> It seems to be for an older version of OCaml.

Does it help if you rebuild math/facile?

___
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"

What should I replace @exec and @unexec with?

[Raphael Kubo da Costa]

I was taking a look at the Porter's Handbook today and noticed that
@exec and @unexec are considered deprecated, but I couldn't find out
what should be used instead.

Should all uses of @exec and @unexec be replaced with pkg-{un}install
scripts in the future?

___
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: astro/wcslib fails to install

[Raphael Kubo da Costa]

Jan Henrik Sylvester  writes:

> My latest port upgrade (from source via portmaster) on
> 10.0-RELEASE/amd64 fails at astro/wcslib, which has been bumped after
> the astro/cfitsio update. It fails to install with:
>
> pkg-static:
> lstat(/usr/ports/astro/wcslib/work/stage/usr/local/bin/HPXcvt): No such
> file or directory

I've fixed wcslib's behavior with regard to how it handles the CFITSIO
option in r353362 -- it's going to be properly off most of the time
regardless of whether astro/cfitsio is present on the system or not,
unless people really turn that option on via `make config'. If they do,
they also need to apply ports/189487 to astro/cfitsio, otherwise
wcslib's configure script will fail to build its test programs with
libcfitsio.so and assume it is not present (and the plist will be
wrong).

> Building astro/wcslib does not fail, but there are numerous segfaults
> starting with these:
>
> make[2]: *** [libwcs-4.13.4.a(lin.o)] Segmentation fault (core dumped)
> gmake[2]: *** Archive member `libwcs-4.13.4.a(lin.o)' may be bogus; not
> deleted
>
> cc -DHAVE_CONFIG_H -I. -I.. -O2 -pipe -fno-strict-aliasing -c sph.c
> ar r libwcs-4.13.4.a sph.o
> ar: warning: Incorrect file header signature
> gmake[2]: *** [libwcs-4.13.4.a(sph.o)] Segmentation fault (core dumped)

Should be fixed by r353360 (the port is not MAKE_JOBS_SAFE).

___
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: astro/wcslib fails to install

[Raphael Kubo da Costa]

Rainer Hurling  writes:

> Am 08.05.2014 05:14 (UTC+1) schrieb Sunpoet Po-Chuan Hsieh:
>> On Wed, May 7, 2014 at 9:52 PM, Jan Henrik Sylvester  wrote:
>>> My latest port upgrade (from source via portmaster) on
>>> 10.0-RELEASE/amd64 fails at astro/wcslib, which has been bumped after
>>> the astro/cfitsio update. It fails to install with:
>>>
>>> pkg-static:
>>> lstat(/usr/ports/astro/wcslib/work/stage/usr/local/bin/HPXcvt): No such
>>> file or directory
>>>
>>> Building astro/wcslib does not fail, but there are numerous segfaults
>>> starting with these:
>>>
>>> make[2]: *** [libwcs-4.13.4.a(lin.o)] Segmentation fault (core dumped)
>>> gmake[2]: *** Archive member `libwcs-4.13.4.a(lin.o)' may be bogus; not
>>> deleted
>>>
>>> cc -DHAVE_CONFIG_H -I. -I.. -O2 -pipe -fno-strict-aliasing -c sph.c
>>> ar r libwcs-4.13.4.a sph.o
>>> ar: warning: Incorrect file header signature
>>> gmake[2]: *** [libwcs-4.13.4.a(sph.o)] Segmentation fault (core dumped)
>>>
>>> What is happening here?
>>>
>>> I do not have anything in make.conf that should be related (only
>>> WITH_NEW_XORG=yes, TEX_DEFAULT=texlive, and some port specific options
>>> of unrelated ports).
>>>
>>> Cheers,
>>> Jan Henrik
>> 
>> It should be fixed in r353239. Please update your ports tree and try
>> again. Thanks!
>
> Even with recent ports tree (r353281), which includes the patch of
> astro/cfitsio (r353239), the error remains for me on 11.0-CURRENT.

I believe I've fixed the segfault issue with r353360.

___
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: Upgrade of astro/kstars to 4.12.4_1 fails - linker error

[Raphael Kubo da Costa]

"Dr. Peter Voigt"  writes:

> I am running 10.0-RELEASE-p2 and after the latest ports tree update the
> upgrade of astro/kstars to 4.12.4_1 fails:
>
> # portmaster --no-confirm --no-term-title -D -G kstars
>
> Scanning dependencies of target testcsvparser
> [100%] Building CXX object
> Tests/CMakeFiles/testfwparser.dir/testfwparser.o [100%] Building CXX
> object Tests/CMakeFiles/testcsvparser.dir/testcsvparser.o Linking CXX
> executable
> testfwparser 
> /usr/ports/astro/kstars/work/kstars-4.12.4/kstars/kstars.cpp:122:7:
> warning: '__GLIBC__' is not defined, evaluates to 0 [-Wundef] #if
> ( __GLIBC__ >= 2 &&__GLIBC_MINOR__ >= 1  && !defined(__UCLIBC__) )
> ^ /usr/local/lib/libcfitsio.so: undefined reference to
> `compress2mem_from_mem' /usr/local/lib/libcfitsio.so: undefined
> reference to `compress2file_from_mem' /usr/local/lib/libcfitsio.so:
> undefined reference to `uncompress2mem' /usr/local/lib/libcfitsio.so:
> undefined reference to `zuncompress2mem' /usr/local/lib/libcfitsio.so:
> undefined reference to `uncompress2file' /usr/local/lib/libcfitsio.so:
> undefined reference to `uncompress2mem_from_mem' c++: error: linker
> command failed with exit code 1 (use -v to see invocation) ---
> Tests/testfwparser --- *** [Tests/testfwparser] Error code 1

This looks like a problem in astro/cfitsio. Have you tried rebuilding it
first?

___
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: [9.2-STABLE/CLANG 3.3|3.4] x11/kdelibs4

[Raphael Kubo da Costa]

Dimitry Andric  writes:

>> The box in question is a Dell Latitude E6510 notebook with only 4 GB of RAM, 
>> could this
>> be the issue? The system very often starts swapping. Even my oldstyle E8400 
>> workstation
>> with only 8 GB (most recent 11.0-CURRENT) starts swapping very often and 
>> recently, I saw
>> musterious compiler erros and stopping compiling processes never seen bevor. 
>> Restarting
>> the failed portbuild most often finish successfully.
>
> There were some postings recently, about newer versions of FreeBSD being
> supposedly more "swappy", see e.g.:
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2014-April/thread.html#78361
>
> I have no idea if this is really substantiated with evidence, or just a
> feeling, though. :)
>
> In any case, when you are experiencing mysterious compiler errors, and
> your system is heavily exercising RAM and swap, it is always a good idea
> to do a full hardware diagnostics test.
>
> For your RAM, you can use memtest86+, and since you have a Dell, you can
> use their diagnostics program to test other parts of the machine.

For what it's worth, ports/187150 might be related to this as well (I've
never experienced those problems myself, but I'm on HEAD).

___
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: problem build kde4

[Raphael Kubo da Costa]

"Nilton Jose Rizzo"  writes:

> when i try to install the ktorrent it's always stop with an error.
> So I decided that will install the full kde4 meta ports, but this
> error occur ever time i type make install command.  My solution
> (I think have some problem with makefile) was change the version
> number 4.12.3 -> 4.12.4, and the jovie ports was installed

Was your x11/kdelibs4 successfully upgraded to 4.12.4?

jovie retrieves the "4.12.4" part of libkttsd.so from
/usr/local/kde4/share/apps/cmake/modules/KDE4Defaults.cmake.

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

Re: devel/libkolab failing to build on 11-current

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Shawn Webb  writes:
>
>> devel/libkolab has been failing for the past few weeks.
>>
>> Log file from an 11-current/amd64 Poudriere build here:
>> http://pastebin.com/kfjkMpE7
>
> I was able to reproduce it here too. It's weird that no pkg-fallout
> email has been sent about this failure.
>
> I've submitted a patch to the kolab development list and will backport
> it to the port.
>
> Thanks for the report.

Fixed in r348328.

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

Re: devel/libkolab failing to build on 11-current

[Raphael Kubo da Costa]

Shawn Webb  writes:

> devel/libkolab has been failing for the past few weeks.
>
> Log file from an 11-current/amd64 Poudriere build here:
> http://pastebin.com/kfjkMpE7

I was able to reproduce it here too. It's weird that no pkg-fallout
email has been sent about this failure.

I've submitted a patch to the kolab development list and will backport
it to the port.

Thanks for the report.

___
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: annoying pkg-fallout notices, how can I stop it?

[Raphael Kubo da Costa]

John Marino  writes:

> Somebody else will have to answer the question.  Basically you submit
> the request and somebody will take care of it.

To expand on this: you can either mail portmgr with the patch you want
to merge and ask for approval or add "MFH: 2014Q1" to your commit
message to have the mail sent automatically for you.

___
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: Anyone having problems with CMake 2.8.12.1_3 and ftp/curl?

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Raphael Kubo da Costa  writes:
>
>> Has anyone else experienced the same issue?
>
> I've finally managed to reproduce the issue locally by installing
> security/openssl.

Thanks everyone, this should be fixed by r347674.

___
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: Anyone having problems with CMake 2.8.12.1_3 and ftp/curl?

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Has anyone else experienced the same issue?

I've finally managed to reproduce the issue locally by installing
security/openssl.

___
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"

Anyone having problems with CMake 2.8.12.1_3 and ftp/curl?

[Raphael Kubo da Costa]

I've received one report from a user on 8-STABLE saying my latest commit
to devel/cmake broke the build for him. Specifically, it fails like
this:

/usr/ports/devel/cmake/work/cmake-2.8.12.1/Utilities/cmcurl/multi.c:1708: 
error: expected declaration specifiers or '...' before numeric constant
/usr/ports/devel/cmake/work/cmake-2.8.12.1/Utilities/cmcurl/multi.c:1710: 
error: conflicting types for 'curl_multi_socket_action'
/usr/local/include/curl/multi.h:287: error: previous declaration of 
'curl_multi_socket_action' was here

I'm unable to reproduce it locally (-HEAD) or in a 8.4-i386 jail inside
Poudriere, even if I manually make ftp/curl a dependency in
devel/cmake's Makefile.

Has anyone else experienced the same issue?

___
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: avogadro update

[Raphael Kubo da Costa]

Ajtim  writes:

> On Tuesday 11 February 2014 10:31:58 you wrote:
>> Ajtim  writes:
>> 
>> > -- [4/5] Numpy Module
>> > Traceback (most recent call last):
>> >   File "", line 1, in 
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/__init__.py", line 
>> > 137, in 
>> > import add_newdocs
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/add_newdocs.py", line 
>> > 9, in 
>> > from numpy.lib import add_newdoc
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/lib/__init__.py", 
>> > line 13, in 
>> > from polynomial import *
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/lib/polynomial.py", 
>> > line 17, in 
>> > from numpy.linalg import eigvals, lstsq, inv
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/linalg/__init__.py", 
>> > line 48, in 
>> > from linalg import *
>> >   File "/usr/local/lib/python2.7/site-packages/numpy/linalg/linalg.py", 
>> > line 23, in 
>> > from numpy.linalg import lapack_lite
>> > ImportError: /usr/local/lib/libalapack.so.2: Undefined symbol "cblas_zswap"
>> > -- Numpy NOT found - Python support disabled.
>> > CMake Warning at CMakeLists.txt:277 (message):
>> >   Not all python dependencies are found - Python support diabled
>> 
>> There you go ^
>> 
>> Looks like you need to rebuild lapack, blas or something related to it (some
>> numpy dependency at least).
>
> I did rebuild blas and lapack and the problem exist:

lapack and blas were suggestions based on numpy's dependencies. Start by
finding out which port installs libalapack.so and go from there. Some
quick googling for "libalapack" already shows ports/176993, for example.
___
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: avogadro update

[Raphael Kubo da Costa]

Ajtim  writes:

> -- [4/5] Numpy Module
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/local/lib/python2.7/site-packages/numpy/__init__.py", line 137, 
> in 
> import add_newdocs
>   File "/usr/local/lib/python2.7/site-packages/numpy/add_newdocs.py", line 9, 
> in 
> from numpy.lib import add_newdoc
>   File "/usr/local/lib/python2.7/site-packages/numpy/lib/__init__.py", line 
> 13, in 
> from polynomial import *
>   File "/usr/local/lib/python2.7/site-packages/numpy/lib/polynomial.py", line 
> 17, in 
> from numpy.linalg import eigvals, lstsq, inv
>   File "/usr/local/lib/python2.7/site-packages/numpy/linalg/__init__.py", 
> line 48, in 
> from linalg import *
>   File "/usr/local/lib/python2.7/site-packages/numpy/linalg/linalg.py", line 
> 23, in 
> from numpy.linalg import lapack_lite
> ImportError: /usr/local/lib/libalapack.so.2: Undefined symbol "cblas_zswap"
> -- Numpy NOT found - Python support disabled.
> CMake Warning at CMakeLists.txt:277 (message):
>   Not all python dependencies are found - Python support diabled

There you go ^

Looks like you need to rebuild lapack, blas or something related to it (some
numpy dependency at least).
___
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: [kde-freebsd] avogadro update

[Raphael Kubo da Costa]

Ajtim  writes:

> Avogadro 1.1.1_1 update on reeBSD 10.0-RELEASE (amd64) doesn't work:
>
> > Compressing man pages (compress-man)
> ===>  Installing for avogadro-1.1.1_1
> ===>  Checking if science/avogadro already installed
> ===>   Registering installation for avogadro-1.1.1_1
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythonerror.h):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythoninterpreter.h):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pythonscript.h):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/avogadro/1_1/extensions/pythonterminal.so):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/python2.7/site-packages/Avogadro.so):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/engineScripts/wireframe.py):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/extensionScripts/example.py):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/extensionScripts/):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/engineScripts/):
>  No such file or directory
> pkg-static: 
> lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/): 
> No such file or directory

Please post the output of `make configure'. I suspect something went
wrong with your boost updates and the Python dependencies are not being
found by Avogadro.
___
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: [kde-freebsd] avogadro update

[Raphael Kubo da Costa]

"Alex V. Petrov"  writes:

> For me stop build:
>
> [ 10%] Building CXX object
> libavogadro/src/extensions/surfaces/openqube/CMakeFiles/OpenQube.dir/moc_gaussianset.cxx.o
> usr/local/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse
> error at "BOOST_JOIN"
> --- libavogadro/src/moc_pythonengine_p.cxx ---
> *** [libavogadro/src/moc_pythonengine_p.cxx] Error code 1
>
> make[4]: stopped in /usr/ports/science/avogadro/work/avogadro-1.1.1
> 1 error

This one has been fixed by ports r343646.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: security/libssh does not install ssh_threads

[Raphael Kubo da Costa]

Dima Panov  writes:

> 14.01.14, 9:29, Peter Klett ?:
>> Hi,
>> 
>> I'm currently trying to compile the nogui version of
>> net-p2p/retroshare which has a dependency to libssh-0.5.4. In its
>> Makefile it includes -lssh and -lssh_threads but the later is not
>> build / installed by libssh.
>> 
> [skip]
>
> Please update. libssh-0.5.5_1 installs both standard and threaded libs.

This is interesting. I ended up trying to find why this was the case and
it seems to be us passing -DTHREADS_HAVE_PTHREAD_ARG and libssh checking
for the wrong variable to decide whether to build libssh_threads.so.

I've sent some patches upstream in
http://thread.gmane.org/gmane.network.ssh.libssh.general/1389

___
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: Patch fixing www/cherokee build

[Raphael Kubo da Costa]

charles rapenne  writes:

> The port www/cherokee is marked broken : does not configure
>
> I found a fix to make it build correctly, I don't know the difference
> between HAS_CONFIGURE and GNU_CONFIGURE, but it does fix the problem.

Thanks for pointing that out. I chose to fix it differently in r339271:
upstream had a clearly wrong check for sizeof(sig_atomic_t) that was not
being used anywhere that was causing this problem. I've removed it in a
patch and have also sent a patch upstream in
https://github.com/cherokee/webserver/pull/1100

___
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: why science/paraview not available from pkg.FreeBSD.org?

[Raphael Kubo da Costa]

Anton Shterenlikht  writes:

> On amd64 11-current I'm getting:

[...]

> Any reason why this package is not available?

It fails to build in the cluster:
http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/Week-of-Mon-20131230/089507.html

___
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"

check-stagedir.sh and %%PORT{DOCS,EXAMPLES}%%

[Raphael Kubo da Costa]

The usual advice for ports that support staging is to remove the checks
for ${PORT_OPTIONS:MDOCS} and friends and unconditionally create
${STAGEDIR}${DOCSDIR} and copy files there (the same applies to
MEXAMPLES and EXAMPLESDIR).

This seems to work fine in the default case (ie. DOCS and EXAMPLES are
set in the port's configuration). If I take a simple port such as
textproc/chpp, unset any of those two options and run something like
`make DISTDIR=/tmp clean stage check-orphans`, check-stagedir.sh
complains about missing plist entries protected by
%%PORT{DOCS,EXAMPLES}%% even though they are actually present.

Other ports just set PORTDOCS and PORTEXAMPLES in the Makefile, and the
same thing happens.

Is this a bug in the script or is there something obvious I'm missing?

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

Re: devel/kdesdk4: compilation dies on FreeBSD 10.0-BETA and FreeBSD 11.0-CURRENT

[Raphael Kubo da Costa]

"O. Hartmann"  writes:

> Since a while, I'm unable ti update/recompile/install port
> devel/kdesdk4 on both FreeBSD 10.0 (starting with the last CURRENT,
> over ALPHA up to BETA2 now) and on all systems running FreeBSD
> 11.0-CURRENT.
>
> The only extraordinary option in my environment is in /etc/src.conf
> -sdt=c++11 defined for building the base/world - and in /etc/make.conf
> -march=native and -O3 as the default.
>
> It doesn't matter wether I switch over to plain standard either
> in /etc/src.conf (which is exclusively for world as I understand) or
> in /etc/make.conf. The error(s) shown below are present on ALL FreeBSD
> 10 and FreeBSD 11 machines and that is a bunch of 4 machines.
>
> I have, so far, rebuilt all boxes with world ommiting "-std=c++11" or
> -O3 optimisations, but the error belwo still occur.

I've sent some patches upstream for review that should fix this issue,
and am currently waiting for review: 
http://article.gmane.org/gmane.linux.umbrello.devel/11418
___
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: lyx 2.0.6

[Raphael Kubo da Costa]

"Julian H. Stacey"  writes:

> Hi, Reference:
>> From:Ajtim 
>> Date:Thu, 17 Oct 2013 06:39:15 -0400
>
> Ajtim wrote:
>> My system: FreeBSD 10.0-BETA1
>> When I built print/lyx I got:
>> fatal error: too many errors emitted, stopping now [-ferror-limit=]
>
> Mine on 10.0-BETA1:
>   6 errors generated.
> As ports/print/lyx/Makefile has
>   MAINTAINER= rak...@freebsd.org
> I added.
>   cc: rak...@freebsd.org

Yeah, LyX is at a very bad shape if used with libc++ instead of
libstdc++: its code is not C++11-compliant and uses tr1 stuff that is
not present in libc++.

To be honest, I'm still not sure how to solve it: using USE_GCC in the
Makefile did not work last time I tested, as the other ports it relied
on had been built with libc++ and there were linking problems due to two
different STL implementations being used at the same time.

___
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: x11/kdelibs4: /usr/local/include/grantlee/typeaccessor.h:70:40: error: no matching function for call to 'distance' return

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> "O. Hartmann"  writes:
>
>> After a messy "iconv" orgy update session, I update yesterday
>> x11/kdelib4 successfully. After updating the OS to
>>
>>  FreeBSD 10.0-CURRENT #2 r255356: Sat Sep  7 13:04:03 CEST 2013 amd64
>>
>> today, I run today surprisingly into this error:
>>
>> [...]
>> In file included
>> from 
>> /usr/ports/x11/kdelibs4/work/kdelibs-4.10.5/kdeui/tests/proxymodeltestsuite/modeleventlogger.cpp:33:
>> In file included from /usr/local/include/grantlee_core.h:24: In file
>> included from /usr/local/include/grantlee_templates.h:34: In file
>> included
>> from /usr/local/include/grantlee/metatype.h:27: 
>> /usr/local/include/grantlee/typeaccessor.h:70:40:
>>
>> error: no matching function for call to 'distance' return
>> QVariant::fromValue( std::distance( container.begin(),
>> container.end() ) );
>> [...]
>>
>> grantlee has also been update successfully, I recompiled it today again
>> successfulyy, but without any success.
>
> Are you using libc++ and is the error message much bigger than that?
> I've fixed that one in Qt and the patch is part of 4.8.5. I'll see how
> much work is left to bring in 4.8.5 into ports.

Fixed in r326778.

___
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: x11/kdelibs4: /usr/local/include/grantlee/typeaccessor.h:70:40: error: no matching function for call to 'distance' return

[Raphael Kubo da Costa]

"O. Hartmann"  writes:

> After a messy "iconv" orgy update session, I update yesterday
> x11/kdelib4 successfully. After updating the OS to
>
>  FreeBSD 10.0-CURRENT #2 r255356: Sat Sep  7 13:04:03 CEST 2013 amd64
>
> today, I run today surprisingly into this error:
>
> [...]
> In file included
> from 
> /usr/ports/x11/kdelibs4/work/kdelibs-4.10.5/kdeui/tests/proxymodeltestsuite/modeleventlogger.cpp:33:
> In file included from /usr/local/include/grantlee_core.h:24: In file
> included from /usr/local/include/grantlee_templates.h:34: In file
> included
> from /usr/local/include/grantlee/metatype.h:27: 
> /usr/local/include/grantlee/typeaccessor.h:70:40:
>
> error: no matching function for call to 'distance' return
> QVariant::fromValue( std::distance( container.begin(),
> container.end() ) );
> [...]
>
> grantlee has also been update successfully, I recompiled it today again
> successfulyy, but without any success.

Are you using libc++ and is the error message much bigger than that?
I've fixed that one in Qt and the patch is part of 4.8.5. I'll see how
much work is left to bring in 4.8.5 into ports.

___
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: [patch] x11-toolkits/qt4-gui: configure error: Cups support cannot be enabled due to functionality tests!

[Raphael Kubo da Costa]

Boris Samorodov  writes:

> 31.08.2013 19:21, Raphael Kubo da Costa пишет:
>> Boris Samorodov  writes:
>> 
>>> Hi All,
>>>
>>> I've examined the following error (486 ports affected):
>>> http://pb2.nyi.freebsd.org/bulk/nogcc-default/2013-08-30_22h26m46s/logs/errors/qt4-gui-4.8.4.log
>>>
>>> ... and it appeared to be a result of latest iconv changes at FreeBSD.
>>>
>> Are you able to reproduce this error locally? The build error you linked
>> to only says building the test file for cups detection failed. Before
>> committing the change, I'd like to double-check the exact error message.
>
> Yes, the error is while running a test to find cups. The test program
> fails to build without "-liconv" flag. Here is the log from my testing
> system:
> http://gw.wart.ru/bulk/10-amd64-default/2013-08-31_00h56m31s/logs/errors/qt4-gui-4.8.4.log

This one still doesn't have the exact build error caused by trying to
build cups.cpp.

I haven't been watching the whole iconv-in-base catastrophe very
closely, but from the recent threads it really looks like qt4-gui is the
wrong place to fix this specific problem.

___
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: [kde-freebsd] [patch] x11-toolkits/qt4-gui: configure error: Cups support cannot be enabled due to functionality tests!

[Raphael Kubo da Costa]

Boris Samorodov  writes:

> Hi All,
>
> I've examined the following error (486 ports affected):
> http://pb2.nyi.freebsd.org/bulk/nogcc-default/2013-08-30_22h26m46s/logs/errors/qt4-gui-4.8.4.log
>
> ... and it appeared to be a result of latest iconv changes at FreeBSD.
>
Are you able to reproduce this error locally? The build error you linked
to only says building the test file for cups detection failed. Before
committing the change, I'd like to double-check the exact error message.
___
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"

r253839 (stop recursively copying DT_NEEDED entries) and devel/ncurses

[Raphael Kubo da Costa]

 has made
ld(1) stop copying DT_NEEDED entries from shared libraries, which brings
us in line with what most of the Linux world has been doing for a while
and is a Good Thing (TM) since we stop adding implicit dependencies to
our binaries.

I've noticed one possible regression with devel/ncurses, though: most of
the time, simply passing -lncurses or -lncursesw to the linker like most
ports do will not work, since one also needs to pass -ltinfo or -tinfow.
This happens because we build devel/ncurses with --with-termlib (which
causes libtinfo{w}.so to be generated).

I guess this was not detected in exp-runs because devel/ncurses is not
normally pulled by ports with USES=ncurses (if a port is being built in
a chroot, Uses/ncurses.mk will just check that base's ncurses is
installed and ${LOCALBASE}/lib/libcurses.so does not exist and move on).

This can be easily tested by passing USES=ncurses:port to any port that
has USES=ncurses (such as devel/tig, security/pinentry or shells/zsh)
or, like in my case, just happening to have devel/ncurses installed
because x11/rxvt-unicode needs it.

On the Linux distributions I checked (Arch Linux, openSUSE and Ubuntu),
either ncurses was not build with --with-termlib (so libncurses{w}.so
would provide all the required symbols) or they have some multiarch
setup in place so that /usr/lib/-linux-gnu/libncurses{w}.so is an
ld script that has something like

   INPUT(libncurses{w}.so AS_NEEDED(libtinfo{w}.so))

that solves the problem.

Right now, I'm not sure the best way to fix this is to patch each port
manually or stop passing --with-termlib in devel/ncurses.

___
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: qt4-qmake-4.8.4 upgrading stops for input. Which file to patch?

[Raphael Kubo da Costa]

Leslie Jensen  writes:

> All >> qt4-qmake-4.8.4 (1/1)
>
> ===>  Cleaning for qt4-qmake-4.8.4_1
> ===>   qt4-qmake-4.8.4_1 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by qt4-qmake-4.8.4_1 for building
> ===>  Extracting for qt4-qmake-4.8.4_1
> => SHA256 Checksum OK for KDE/qt-everywhere-opensource-src-4.8.4.tar.gz.
> ===>  Patching for qt4-qmake-4.8.4_1
> ===>  Applying FreeBSD patches for qt4-qmake-4.8.4_1
> File to patch:

Fixed in r324772.

___
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: [kde-freebsd] port options are not saved in some ports

[Raphael Kubo da Costa]

Baptiste Daroussin  writes:

> http://people.freebsd.org/~bapt/kde.diff

This should be fixed in r322586, thank you very much.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/qt4-corelib dosen´t build

[Raphael Kubo da Costa]

Bernt Hansson  bananmonarki.se> writes:

> Hello list.
>
> I´m having problems with devel/qt4-corelib

Please try removing x11-toolkits/qt33 while you build your Qt ports, this is a
known issue we haven't worked around so far.


___
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: [kde-freebsd] kde3 ports expired today

[Raphael Kubo da Costa]

Matthias Apitz  writes:

> We have (perhaps) all seen this in UPDATING and while compiling qt3*
> ports; I think, it is not a good idea deleting the KDE3 ports (which do
> compile) from our ports tree, while the KDE4 ports do not compile, at
> least not on i386 architecture. See the PR's about automoc4 and others.

To be fair, the problem with the random automoc crashes seems to be
specific to i386 on CURRENT (we do have binary packages for our released
versions after all) and dim@ was already taking a look at that a few
days ago.
___
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: Can't build devel/qt4-corelib any more -- help?

[Raphael Kubo da Costa]

David Wolfskill  writes:

> However, I note that there appear to be no qt* ports installed currently:
>
> albert(9.1-S)[9] popd
> /var/db/pkg
> albert(9.1-S)[10] echo qt*
> echo: No match.
> albert(9.1-S)[11]

Can you also check that you don't have some stray q* headers in
/usr/local/include?

___
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: Can't build devel/qt4-corelib any more -- help?

[Raphael Kubo da Costa]

David Wolfskill  writes:

> ../../include/QtCore/../../src/corelib/arch/qatomic_arch.h:96:4: error: 
> #error "Qt has not been ported to this architecture"

This usually indicates that Qt3 headers are being picked instead of the
Qt4 ones when building; I guess we never really got around to properly
fixing this.

Can you try removing qt3 while building?

___
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: science/avogadro fails to build

[Raphael Kubo da Costa]

Carmel  writes:

> FreeBSD-8.3 STABLE amd64
>
> Evidently, the "science/avogadro" port does not have a full time
> maintainer. In that case, I will report the problem here. Basically,
> the port refused to build. It ends with this output: (it probably
> suffers severe line wrap distortion)

I have probably fixed it in r318197, please svn up and give it a try.

___
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: science/avogadro fails to build

[Raphael Kubo da Costa]

Carmel  writes:

> FreeBSD-8.3 STABLE amd64
>
> Evidently, the "science/avogadro" port does not have a full time
> maintainer. In that case, I will report the problem here. Basically,
> the port refused to build. It ends with this output: (it probably
> suffers severe line wrap distortion)

BTW, if anyone's willing to tackle this one, please remember to close
ports/178537 too.

___
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: qt-mysql-plugin-3.3.8_10 failed on amd64 8

[Raphael Kubo da Costa]

John Marino  writes:

> I have attached a patch that fixes the problem.  It was related to the
> extraction cleanup.  Can somebody commit it?

Committed in r318134, 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: teTeX and TeXLive

[Raphael Kubo da Costa]

Hiroki Sato  writes:

>  Once it is confirmed that TEX_DEFAULT=texlive works, I will switch
>  the default value from tetex to texlive at some point.

Thanks a lot for all the work. Is removing tetex a middle or long-term
goal?

___
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: textproc/libkolabxml does not compile

[Raphael Kubo da Costa]

David Demelier  writes:

> ===>  Building for libkolabxml-0.8.1
> [  4%] Built target xsdbin
> [  8%] Generating XSD bindings
> terminate called after throwing an instance of 'std::runtime_error'
>   what():  locale::facet::_S_create_c_locale name not valid
> Abort trap

For posterity: this was a problem in devel/boost-libs fixed in r311771.

___
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"

Adopting porttools upstream?

[Raphael Kubo da Costa]

Hi there,

sergei@'s commit bit was taken into safekeeping years ago and porttool's
project in SourceForge [1] has not seen any CVS commit for a long time
as well.

[1] https://sourceforge.net/projects/porttools

Meanwhile, we've been patching ports-mgmt/porttools to keep up with our
infrastructure changes and whatnot.

I was thinking of integrating those fixes upstream and continuing the
development somewhere else. skreuzer@ seems to have a fork on GitHub [2]
with no previous history and some commits on top.

[2] https://github.com/skreuzer/porttools

I, for one, ran devel/cvs2svn on the existing CVS history and converted
it to git. The result looks OK and can be see in [3].

[3] https://github.com/rakuco/porttools

I'm not terribly interested in becoming porttools' upstream myself, but
if others fail to jump aboard that could end up happening.

Thoughts?

___
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: Why delete KDE3 ports?

[Raphael Kubo da Costa]

John Marino  writes:

> On 1/8/2013 21:14, Raphael Kubo da Costa wrote:
>> Additionally, I'd argue that it is hard for it to be "known insecure"
>> since upstream does not maintain it even for security vulnerabilities
>> anymore, so security problems have nowhere to be reported and
>> vulnerabilities common to KDE3 and KDE4 only get published and fixed in
>> the latter.
>
> This doesn't count?
> http://cve.mitre.org/cve/
> http://web.nvd.nist.gov/view/vuln/search?execution=e2s1
>
> It seems to be there is somewhere to report them...

The vulnerabilities disclosed in those places are normally published
after upstream has been contacted and come up with a fix for the
security issue, so I don't think the lack of new KDE3 advisories
compared to KDE4 ones means the former is safer.

___
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: Why delete KDE3 ports?

[Raphael Kubo da Costa]

Adam Vande More  writes:

> On Mon, Jan 7, 2013 at 12:53 PM, John Marino  wrote:
>> "possibly insecure":  I think this needs to be "known insecure" rather
>> than holding it's last release date against it.
>
> http://www.kde.org/info/security/advisory-20100413-1.txt
>
> Probably other security issues as well.  I didn't have to look very long.
>  In a codebase as large as KDE's, it seems a very slim chance indeed years
> could go by without maintenance and still maintain security.

Additionally, I'd argue that it is hard for it to be "known insecure"
since upstream does not maintain it even for security vulnerabilities
anymore, so security problems have nowhere to be reported and
vulnerabilities common to KDE3 and KDE4 only get published and fixed in
the latter.

___
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: kde4 errors and no .xsession-errors file!

[Raphael Kubo da Costa]

David Southwell  writes:

> I cannot find a .xession-errors file - what turns it off or on?
>
> I need to find out what is going wrong.
>
> Kde4 is not loading

How are you starting KDE? If you're using startx, you just need to
redirect startkde's output to .xsession-errors.

___
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: Cannot upgrade FlySpray

[Raphael Kubo da Costa]

Nick Hilliard  writes:

> On 23/10/2012 10:12, Andrea Venturoli wrote:
>>> 1 out of 1 hunks failed--saving rejects to includes/fix.inc.php.rej
>>> => Patch patch-includes-fix.inc.php failed to apply cleanly.
>>> *** Error code 1
>
> Damn, the patch submission process turned all the CRLFs into LFs.  Here's a
> new patch.  I'll submit it to GNATS.

Fixed in r306358 by setting the svn:eol-style property to CRLF for that
file.

___
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: raptor: should there be a note in UPDATING?

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Raphael Kubo da Costa  writes:
>
>> Raphael Kubo da Costa  writes:
>>
>>> Someone (TM) should check whether the first include is really necessary,
>>> or if the code can't include , or if
>>> -I/usr/local/include/raptor2 can't be passed before
>>> -I/usr/local/include.
>>
>> Everything built fine without the {CPP,LD}FLAGS additions here. I'm
>> tempted to commit that change, but wonder if it will end up breaking
>> some weird setup...
>
> Coming to think of it again, removing those lines changing {CPP,LD}FLAGS
> would have an impact if one is using openssl from ports, as the check
> for MD5() in libcrypto.so would be done for the library in base, not
> ${LOCALBASE}.

I think I've finally fixed the issue in r302968.

___
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: raptor: should there be a note in UPDATING?

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Raphael Kubo da Costa  writes:
>
>> Someone (TM) should check whether the first include is really necessary,
>> or if the code can't include , or if
>> -I/usr/local/include/raptor2 can't be passed before
>> -I/usr/local/include.
>
> Everything built fine without the {CPP,LD}FLAGS additions here. I'm
> tempted to commit that change, but wonder if it will end up breaking
> some weird setup...

Coming to think of it again, removing those lines changing {CPP,LD}FLAGS
would have an impact if one is using openssl from ports, as the check
for MD5() in libcrypto.so would be done for the library in base, not
${LOCALBASE}.

___
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: raptor: should there be a note in UPDATING?

[Raphael Kubo da Costa]

Raphael Kubo da Costa  writes:

> Someone (TM) should check whether the first include is really necessary,
> or if the code can't include , or if
> -I/usr/local/include/raptor2 can't be passed before
> -I/usr/local/include.

Everything built fine without the {CPP,LD}FLAGS additions here. I'm
tempted to commit that change, but wonder if it will end up breaking
some weird setup...

___
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: liblrdf

[Raphael Kubo da Costa]

ajtiM  writes:

> ===>>> make failed for textproc/liblrdf
> ===>>> Aborting update
>
> ===>>> Update for textproc/liblrdf failed
> ===>>> Aborting update

Please see the other thread about the same issue.

___
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: raptor: should there be a note in UPDATING?

[Raphael Kubo da Costa]

Robert Backhaus  writes:

> I just had a problem building liblrdf. The cause was raptor-1 was
> still installed. Checking UPDATING shows nothing that mentions raptor
> after the KDE update last November.
> Does there need to a note in UPDATING to uninstall raptor?

It seems more appropriate to fix the port: according to the build log
posted in <201208211544.18566.lum...@gmail.com> (the other liblrdf
thread), -I/usr/local/include is being passed before
-I/usr/local/include/raptor2, and it is likely that the source code
#includes , which is installed by both raptor and raptor2
(albeit into different directories).

Someone (TM) should check whether the first include is really necessary,
or if the code can't include , or if
-I/usr/local/include/raptor2 can't be passed before
-I/usr/local/include.

___
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"

Right LICENSE* values for a GPLv2 port with a licensing exception

[Raphael Kubo da Costa]

Hello there,

I'm currently working on porting xsd [1], which is a GPLv2-licensed with
an exception that allows the distribution of derivative works under
other free software licenses.  The contents of this exception can be
found in [2].

In this case, how am I supposed to set the LICENSE* variables in the
Makefile?  Should I use LICENSE_COMB=dual and consider FLOSSE a separate
license that must be agreed to besides the GPLv2?

[1] http://www.codesynthesis.com/projects/xsd/
[2] http://www.codesynthesis.com/projects/xsd/FLOSSE

___
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: [CFT] editors/emacs to 24.1

[Raphael Kubo da Costa]

Joseph Mingrone  writes:

> for a few months).  Running emacsclient -t works fine.  If I start
> emacs with just "% emacs", and I don't wait to long, I can kill it
> with a C-c and the warning/error messages below appear in xterm:
>
> % emacs
> ^C
> (process:1589): GLib-WARNING **: In call to g_spawn_sync(), exit
> status of a child process was requested but SIGCHLD action was set to
> SIG_IGN and ECHILD was received by waitpid(), so exit status can't be
> returned. This is a bug in the program calling g_spawn_sync(); ei
> ther don't request the exit status, or don't set the SIGCHLD action.
>
> (process:1589): GLib-GIO-CRITICAL **: g_dbus_connection_add_filter:
> assertion `G_IS_DBUS_CONNECTION (connection)' failed

I don't use emacsclient myself, but I remember having some similar
problems (and getting the g_spawn_sync() warning) when building the port
(the current version in ports, not 24.1) with SYNC_INPUT=off.
___
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: [CFT] editors/emacs to 24.1

[Raphael Kubo da Costa]

ash...@freebsd.org (Ashish SHUKLA) writes:

> Any feedback would be greatly appreciated.

It seems to be running fine here, I've now even switched to GTK3 (I
wonder if there should be an error message if one selected more than one
GUI option).

Gnus from git with the new Emacs also seems to be running fine.

___
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: Cannot upgrade kdesdk-4.7.4_1 to 4.8.4

[Raphael Kubo da Costa]

sindrome  writes:

> Trying to upgrade kdesdk-4.7.4_1 to 4.8.4 and running into the
> following error.  Anyone have an idea?

This seems to come from the same libkonq problems which are currently
blocking your kde4-baseapps upgrade.

___
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: Cannot upgrade kde-baseapps-4.7.4_1 to 4.8.4

[Raphael Kubo da Costa]

sindrome  writes:

> Linking CXX executable dolphin
> ../../lib/libdolphinprivate.so.5.0.1: undefined reference to
> `KVersionControlPlugin2::staticMetaObject'

For posterity: we've also been contacted in the kde@ mailing list [1],
and are currently tracking it there. It may be the case that the OP did
not follow UPDATING, as there's a dangling /usr/local/lib/libkonq.so
which should not be present and is being wrongfully picked up.

[1] http://article.gmane.org/gmane.comp.kde.freebsd/21894

___
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: Cannot upgrade kde-runtime-4.8.4' to 'kde-runtime-4.8.4_1'

[Raphael Kubo da Costa]

sindrome  writes:

> (Soprano::PluginManager) found no soprano plugin at
> "/usr/local/lib/soprano/libsoprano_raptorparser.so" - error: "Cannot
> load library /usr/local/lib/soprano/libsoprano_raptorparser.so:
> (Shared object "libssl.so.8" not found, required by
> "libraptor2.so.0")"

Looks like a screwup in your OpenSSL installation.

___
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: [CFT] editors/emacs to 24.1

[Raphael Kubo da Costa]

ash...@freebsd.org (Ashish SHUKLA) writes:

> I've started work on the updating, and I've created a diff[1] to update port
> to 24.1 as well as converted it to use OptionsNG[2] framework.

Thanks for working on this! Would it be possible to produce a diff with
the required to changes to bsd.emacs.mk as well?

One additional question, slightly off-topic: are there plans to remove
old emacs ports such as v21 and/or v22?
___
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"