Re: My first port

On Mon, 22 Jun 2020 06:04:22 +0600 Muhammad Moinur Rahman wrote: > Hi, > > Try to find out the reference location "share/pkgconfig” in the CMake > file. Then you can use REIINPLACE_CMD to change that line or modify > accordingly. > > The purpose of @sample is not this. @sample is primarily

My first port

Hi freebsd-ports, I'm trying to create my first port and things are taking shape, but I'm down to one little detail making me feel a bit dirty. The port is based on the latest release of swi-prolog, which has switched to cmake/ninja. My final issue is that the pkg-conf-.pc file gets

Re: pcm1:virtual:dsp1.vp0: play interrupt timeout, channel dead

On 03/19/2018 00:41, Cy Schubert wrote: The other thing you might want to check out is if you multiboot your laptop that any non-FreeBSD operating system may put hardware into an inconsistent state. For example, my Acer laptop loses sound if I boot Windows then boot FreeBSD. The workaround is

Blender/libicu linking issues

Hi, When linking Blender 2.71 on fbsd10 I get: Linking CXX executable ../../bin/blender /usr/bin/ld: warning: libicuuc.so.52, needed by /usr/local/lib/libboost_regex.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libicui18n.so.52, needed by

Re: Blender/libicu linking issues

On 07/13/2014 18:25, Baptiste Daroussin wrote: On Sun, Jul 13, 2014 at 06:05:29PM +0200, Nikolaj Thygesen wrote: Hi, When linking Blender 2.71 on fbsd10 I get: Linking CXX executable ../../bin/blender /usr/bin/ld: warning: libicuuc.so.52, needed by /usr/local/lib/libboost_regex.so

Filezilla

Hi, Is it just me, or is Filezilla 3.8 currently unable to install?? I get messages like these: pkg-static: lstat(/usr/ports/ftp/filezilla/work/stage/usr/local/share/locale/vi_VN/LC_MESSAGES/): No such file or directory pkg-static:

Re: [patch] request for update of x11/nvidia-driver

On 02/16/2011 18:42, Emanuel Haupt wrote: Hi Alexey I'm running version 260.19.36 of x11/nvidia-driver for a while now without any problems. Could you please consider updating the port? I'm sure further feedback from other users would help. Emanuel Hi, I've been running that same

FreeBSD Port: libcanberra-0.10_5

The current libcanberra - libcanberra-0.10.tar.gz - doesn't handle multithreaded gtk applications well (doesn't take the gdk lock when playing sounds), which is supposedly fixed in the latest release. Are there any plans of doing updates in the near future? br - Nikolaj Thygesen

FreeBSD Port: valgrind-3.5.0_1,1

Hi, Valgrind still seems troubled when it comes to multithreaded programs. It seems pthread_self() always returns the same id no matter which thread calls it - possibly the id of last created thread. Running a simple test program under Valgrind fails whereas running it as a regular binary

What's the deal with gmime2-sharp

Hi, Lately, whenever I try to portupgrade -a I get: ** Port marked as IGNORE: mail/gmime2-sharp: try to install weaked-named assembly into the GAC. and subsequently tomboy doesn't build. I'm not that profficient at .net stuff, and have no clue, what it wants me to do. br - Nikolaj

numerous gcc installations

Hi list, Could anyone please explain to me whether it's really required to have two extra versions of gcc installed. I Recently upgraded py25-numpy, which in turn pulled in gcc-4.2.5_20081126 as a dependency. A few days ago blas refused to compile because: ===Verifying reinstall for

FreeBSD Port: opera-9.60.20081004

When running the new opera 2.60 on fbsd, it will try to launch: /usr/local/share/opera/bin/operapluginwrapper.linux which doesn't exist. Another wrapper: /usr/local/share/opera/bin/operapluginwrapper.freebsd does exist though. I guess this is the one to really call?! br - N :o)

Re: Commiting new ports

Sahil Tandon wrote: Wesley Shields [EMAIL PROTECTED] wrote: On Fri, Jun 06, 2008 at 12:56:48AM +0200, Nikolaj Thygesen wrote: Hi, I hope this is the right list to ask this question. I recently commited a new port, and received two messages from ports. The first one noted

Commiting new ports

Hi, I hope this is the right list to ask this question. I recently commited a new port, and received two messages from ports. The first one noted that a person had assigned the port to himself, and the second mail simply stated that the PR went from open to closed due to feedback timeout.