Re: Can't build kernel with ndis

[Thomas Mueller]

> Once you get used to it, the merge operation in mergemaster is pretty
> easy to use on most files. Always use 'r' for the $FreeBSD$ line and
> 'l' for the sections that are modified. In the password and group
> files, it is usually just 'r' followed by a few 'l's. I run the
> "pre-buildworld" run (-p) as is and use -iPF options with the 'main'
> mergemaster run. You can also use 'U' which will save a lot of time in
> the main run, but it is NOT fool-proof and can bite you on rather rare
> occasions, so I have stopped using it. Believe me when I tell you it
> was a LOT worse in the days before mergemaster was written and all of
> the merging had to be done by hand. That was really a pain!

> Good luck with ndis. I've had mixed success with it over the years,
> but have no devices that require it ATM and even when I did, I used
> the module.
> --
> R. Kevin Oberman, Network Engineer
> E-mail: kob6...@gmail.com

I guess doing all the merging by hand, prior to mergemaster, was error-prone.

NetBSD has etcupdate.  I am not decided which is better between NetBSD 
etcupdate and FreeBSD mergemaster.

I think etcupdate is less destructive.  With mergemaster, you really need to 
make a backup copy of /etc.

Tom
___
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: #warning: this file includes < > which is depreciated

[Chris Rees]

On 27 December 2012 15:44, Jos Chrispijn  wrote:
> Looking at my port updates, I more often see this line
>
> #warning: this file includes <  >  which is depreciated
>
> Is this due to bad source compilation or does it affect certain FreeBSD
> versions only?

You really need to give more detail :)

Which port?  Which version of FreeBSD are you running?

Chris
___
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.1-RC3: xorg-input-mouse, xfce4-panel

[Kimmo Paasiala]

On Fri, Dec 28, 2012 at 1:51 PM, CeDeROM  wrote:
> On Fri, Dec 28, 2012 at 12:42 PM, Kimmo Paasiala  wrote:
>> You're misunderstanding a few things. There are no "release packages"
>> for any release of FreeBSD. What you have on the install discs are
>> just "snapshot" packages built from the ports tree as it happened (...)
>
> I know, I hoped 1.7.2 driver or 1.8.1 can get into a port tree before
> packages for 9.1 are built and released. When I applied a patch (some
> structure fields initialization) from 1.7.2 on current 1.7.1 driver
> problem of detection and strange mouse behavior was gone. If 1.7.1
> gets into the packages lots of people will report this issue... thats
> all.
>
> Best regards :-)
> Tomek
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Related to this,

It doesn't look like the FreeBSD ports SVN repository is used to its
full potential. SVN allows branching and creation of experimental
versions of the tree very easily and cheaply, yet all the experimental
repositories references so far are stored in some external
repositories, github or elsewhere.

What gives?
___
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.1-RC3: xorg-input-mouse, xfce4-panel

[CeDeROM]

On Fri, Dec 28, 2012 at 1:02 PM, Kimmo Paasiala  wrote:
> It doesn't look like the FreeBSD ports SVN repository is used to its
> full potential. (...)

Yea, btw why FreeBSD does not use GIT? I have been using it for some
time and I have not seen better source code revision utility. GIT is
really amazing, SVN/CVS seems to be a file revision control, while GIT
is the source code revision control, this tool surprises me all the
time with its great features :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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.1-RC3: xorg-input-mouse, xfce4-panel

[Kimmo Paasiala]

On Fri, Dec 28, 2012 at 2:08 PM, CeDeROM  wrote:
> On Fri, Dec 28, 2012 at 1:02 PM, Kimmo Paasiala  wrote:
>> It doesn't look like the FreeBSD ports SVN repository is used to its
>> full potential. (...)
>
> Yea, btw why FreeBSD does not use GIT? I have been using it for some
> time and I have not seen better source code revision utility. GIT is
> really amazing, SVN/CVS seems to be a file revision control, while GIT
> is the source code revision control, this tool surprises me all the
> time with its great features :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

I would personally use GIT but I'm ok with SVN too. I absolutely hate
CVS :P  My point is really that why not centralise all the development
that happens around the ports tree. The infrastructure is there
already.

-Kimmo
___
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.1-RC3: xorg-input-mouse, xfce4-panel

[Kurt Jaeger]

Hi!

> Yea, btw why FreeBSD does not use GIT?

http://wiki.freebsd.org/Git

points to some text that describes this topic:

http://wiki.freebsd.org/GitDrawbacks

-- 
p...@opsec.eu+49 171 3101372 8 years to go !
___
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"

9.1-PRE: updating of pkg-1.0.3 -> pkg-1.0.4 fails

[Hartmann, O.]

Last time I update ports on my latop was on Dec 20th. Everything went
well. Today I grabbed the laptop again, made an update of the ports tree
and try running portmaster.

The laptop is running FreeBSD 9.1-PRERELEASE #142 r244377: Tue Dec 18
07:29:18 CET 2012.

The update of pkgng is the first in line to be updated, but it fails as
you can see below. I do not understand the recommendations, since I use
USE_PKGNG=yes on that box without problems for a couple of weeks now.

I then downloaded the new pkg-1.0.4 sources manually and did a manula
update jumping into ports-mgmt/pkg; make reinstall.

This worked, but leaves the record in the pkg-db still on 1.0.3, so any
further portmaster attempt will end in installing the update of pkg
first, which ends up in the nasty message below.

I can not see this behaviour on any FreeBSD 10.0 box I have around!

What is wrong here?

Oliver

[...]
===>  Cleaning for pkg-1.0.4_1
You are about to convert your system to pkgng while you have ports/packages
installed with the old pkg_install tools.

You can choose to:
- keep pkg_install as the package management system by adding this line
to /etc/make.conf:

WITHOUT_PKGNG=yes

- switch to pkgng:
1) Add WITHOUT_PKGNG to /etc/make.conf
2) Install ports-mgmt/pkg
3) Convert your package database by running pkg2ng
4) Remove WITHOUT_PKGNG from /etc/make.conf

*** [pre-everything] Error code 1

Stop in /usr/ports/ports-mgmt/pkg.

===>>> make failed for ports-mgmt/pkg
===>>> Aborting update

===>>> Update for pkg-1.0.3_1 failed
===>>> Aborting update

Terminated

===>>> You can restart from the point of failure with this command line:
   portmaster  ports-mgmt/pkg devel/pkgconf
___
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.1-PRE: updating of pkg-1.0.3 -> pkg-1.0.4 fails

[Olli Hauer]

On 2012-12-28 14:45, Hartmann, O. wrote:
> Last time I update ports on my latop was on Dec 20th. Everything went
> well. Today I grabbed the laptop again, made an update of the ports tree
> and try running portmaster.
> 
> The laptop is running FreeBSD 9.1-PRERELEASE #142 r244377: Tue Dec 18
> 07:29:18 CET 2012.
> 
> The update of pkgng is the first in line to be updated, but it fails as
> you can see below. I do not understand the recommendations, since I use
> USE_PKGNG=yes on that box without problems for a couple of weeks now.
> 
> I then downloaded the new pkg-1.0.4 sources manually and did a manula
> update jumping into ports-mgmt/pkg; make reinstall.
> 
> This worked, but leaves the record in the pkg-db still on 1.0.3, so any
> further portmaster attempt will end in installing the update of pkg
> first, which ends up in the nasty message below.
> 
> I can not see this behaviour on any FreeBSD 10.0 box I have around!
> 
> What is wrong here?
> 
> Oliver
> 
> [...]
> ===>  Cleaning for pkg-1.0.4_1
> You are about to convert your system to pkgng while you have ports/packages
> installed with the old pkg_install tools.
> 
> You can choose to:
> - keep pkg_install as the package management system by adding this line
> to /etc/make.conf:
> 
> WITHOUT_PKGNG=yes
> 
> - switch to pkgng:
> 1) Add WITHOUT_PKGNG to /etc/make.conf
> 2) Install ports-mgmt/pkg
> 3) Convert your package database by running pkg2ng
> 4) Remove WITHOUT_PKGNG from /etc/make.conf
> 
> *** [pre-everything] Error code 1
> 
> Stop in /usr/ports/ports-mgmt/pkg.
> 
> ===>>> make failed for ports-mgmt/pkg
> ===>>> Aborting update
> 
> ===>>> Update for pkg-1.0.3_1 failed
> ===>>> Aborting update
> 
> Terminated
> 
> ===>>> You can restart from the point of failure with this command line:
>portmaster  ports-mgmt/pkg devel/pkgconf

Hm, can you look into the directory /var/db/pkg and check there a no leftovers 
from the old pkg tools (directories).
If there are any old directories the pre-everything target will be executed and 
you see this failure.
What gives the command pkg_info as output?

--
Regards,
olli
___
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: portmaster -w -r icu wants to install new ports

[Chess Griffin]

On Thu, Dec 27, 2012, at 09:32 PM, Kevin Oberman wrote:
> As I often do, I recommend using pkg_libchk -o | grep libicu | cut -f1
> -d: | sort | uniq' to provide a list of the ports that actually link
> to the shareable libraries in icu. Those are the only ports you really
> need to re-install. Walking up the dependency tree will catch many
> ports that depend on comething that links to a shareable, but don't
> link to it, itself.
> 

Thanks, this did seem to help.  After doing this and rerunning
portmaster I think I got the list down to the installed ports.  In any
event, all is updated and working well.  Cheers!

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

jitsi (was: Re: working SIP phone for FreeBSD?)

[Matthias Apitz]

El día Friday, December 28, 2012 a las 10:44:08AM +0100, Matthias Apitz 
escribió:

> > I've used your port and installed Jitsi on my laptop; thanks; do you
> > know why the account window on my sreen (1024x600) looks so ugly:
> > http://www.unixarea.de/jitsi.jpg
> > 
> > it registers fine to my Yahoo account and I will try SIP later on.
> 
> and I could not make jitsi using /dev/video0 of webcamd (which works
> fine in Skype and other apps); any idea?

I have had a look into the Java sources:

in 
jitsi/src/net/java/sip/communicator/impl/neomedia/device/JmfDeviceDetector.java 

initializeVideo()

there is no support for FreeBSD (only for MAC OS, Linux and Windows); I
added it the same way as Linux would do, hoping that our V4L2 is
doing its job; but it turned out that the Java/C interface shared object in 
jitsi/src/native/linux/video4linux2 does not get built by the port and
so it says in the log file:

12:57:00.189 INFO:
impl.neomedia.device.JmfDeviceDetector.initializeVideo().307 No Video4Linux2 
detected: no jvideo4linux2 in java.library.path

matthias
-- 
Matthias Apitz   |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: java/openjdk6 fails to build..

[Greg Lewis]

On Fri, Dec 21, 2012 at 07:27:22PM -0500, Eitan Adler wrote:
> On 21 December 2012 19:16, David Demelier  wrote:
> > Yes, I wanted to answser, but the man says that MAKE_JOBS are disabled by
> > default, I tried to build with MAKE_JOBS=1 and it works, the problem did
> > appear when MAKE_JOBS=6 was set. Can you reproduce the issue?
> 
> I want to mark this MAKE_JOBS_UNSAFE=yes and remove the current hack
> Any objection from java@ ?
> 
> > I had MAKE_JOBS=6 in my /etc/make.conf instead of MAKE_JOBS_NUMBER though
> 
> Exactly. MAKE_JOBS is not user-settable. MAKE_JOBS_NUMBER is.  IMHO
> MAKE_JOBS should start with an _.

I think that's right.  I have no objection.  I think whats in openjdk7
is closer to what it should be.

-- 
Greg Lewis  Email   : gle...@eyesbeyond.com
Eyes Beyond Web : http://www.eyesbeyond.com
Information Technology  FreeBSD : gle...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: java/openjdk6 fails to build..

[Eitan Adler]

On 28 December 2012 15:24, Greg Lewis  wrote:
> On Fri, Dec 21, 2012 at 07:27:22PM -0500, Eitan Adler wrote:
>> On 21 December 2012 19:16, David Demelier  wrote:
>> > Yes, I wanted to answser, but the man says that MAKE_JOBS are disabled by
>> > default, I tried to build with MAKE_JOBS=1 and it works, the problem did
>> > appear when MAKE_JOBS=6 was set. Can you reproduce the issue?
>>
>> I want to mark this MAKE_JOBS_UNSAFE=yes and remove the current hack
>> Any objection from java@ ?
>>
>> > I had MAKE_JOBS=6 in my /etc/make.conf instead of MAKE_JOBS_NUMBER though
>>
>> Exactly. MAKE_JOBS is not user-settable. MAKE_JOBS_NUMBER is.  IMHO
>> MAKE_JOBS should start with an _.
>
> I think that's right.  I have no objection.  I think whats in openjdk7
> is closer to what it should be.

What is in openjdk7 seems bogus and it isn't clear why it is there:
MAKE_JOBS_UNSAFE=   yes
is defined implying that MAKE_JOBS should always be 1 (and -j never set)
but it does some weird things with the global variables
MAKE_JOBS_NUMBER and DISABLE_MAKE_JOBS.

Can the generic handling in b.p.m not work?

IMHO MAKE_JOBS_SAFE=yes should be defined and either b.p.m or b.java.m
should be handling the special build code.
-- 
Eitan Adler
___
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.1-PRE: updating of pkg-1.0.3 -> pkg-1.0.4 fails

[O. Hartmann]

Am 12/28/12 15:01, schrieb Olli Hauer:
> On 2012-12-28 14:45, Hartmann, O. wrote:
>> Last time I update ports on my latop was on Dec 20th. Everything went
>> well. Today I grabbed the laptop again, made an update of the ports tree
>> and try running portmaster.
>>
>> The laptop is running FreeBSD 9.1-PRERELEASE #142 r244377: Tue Dec 18
>> 07:29:18 CET 2012.
>>
>> The update of pkgng is the first in line to be updated, but it fails as
>> you can see below. I do not understand the recommendations, since I use
>> USE_PKGNG=yes on that box without problems for a couple of weeks now.
>>
>> I then downloaded the new pkg-1.0.4 sources manually and did a manula
>> update jumping into ports-mgmt/pkg; make reinstall.
>>
>> This worked, but leaves the record in the pkg-db still on 1.0.3, so any
>> further portmaster attempt will end in installing the update of pkg
>> first, which ends up in the nasty message below.
>>
>> I can not see this behaviour on any FreeBSD 10.0 box I have around!
>>
>> What is wrong here?
>>
>> Oliver
>>
>> [...]
>> ===>  Cleaning for pkg-1.0.4_1
>> You are about to convert your system to pkgng while you have ports/packages
>> installed with the old pkg_install tools.
>>
>> You can choose to:
>> - keep pkg_install as the package management system by adding this line
>> to /etc/make.conf:
>>
>> WITHOUT_PKGNG=yes
>>
>> - switch to pkgng:
>> 1) Add WITHOUT_PKGNG to /etc/make.conf
>> 2) Install ports-mgmt/pkg
>> 3) Convert your package database by running pkg2ng
>> 4) Remove WITHOUT_PKGNG from /etc/make.conf
>>
>> *** [pre-everything] Error code 1
>>
>> Stop in /usr/ports/ports-mgmt/pkg.
>>
>> ===>>> make failed for ports-mgmt/pkg
>> ===>>> Aborting update
>>
>> ===>>> Update for pkg-1.0.3_1 failed
>> ===>>> Aborting update
>>
>> Terminated
>>
>> ===>>> You can restart from the point of failure with this command line:
>>portmaster  ports-mgmt/pkg devel/pkgconf
> 
> Hm, can you look into the directory /var/db/pkg and check there a no 
> leftovers from the old pkg tools (directories).
> If there are any old directories the pre-everything target will be executed 
> and you see this failure.
> What gives the command pkg_info as output?
> 
> --
> Regards,
> olli
> 

portmaster installs for each port still a directory in /var/db/pkg - so
there are plenty of directories.

I deleted them all and tried again - this time the update worked.

This is very strange and seems to be unlogical.

Oliver



signature.asc
Description: OpenPGP digital signature

Re: 9.1-PRE: updating of pkg-1.0.3 -> pkg-1.0.4 fails

[Baptiste Daroussin]

On Fri, Dec 28, 2012 at 10:39:00PM +0100, O. Hartmann wrote:
> Am 12/28/12 15:01, schrieb Olli Hauer:
> > On 2012-12-28 14:45, Hartmann, O. wrote:
> >> Last time I update ports on my latop was on Dec 20th. Everything went
> >> well. Today I grabbed the laptop again, made an update of the ports tree
> >> and try running portmaster.
> >>
> >> The laptop is running FreeBSD 9.1-PRERELEASE #142 r244377: Tue Dec 18
> >> 07:29:18 CET 2012.
> >>
> >> The update of pkgng is the first in line to be updated, but it fails as
> >> you can see below. I do not understand the recommendations, since I use
> >> USE_PKGNG=yes on that box without problems for a couple of weeks now.
> >>
> >> I then downloaded the new pkg-1.0.4 sources manually and did a manula
> >> update jumping into ports-mgmt/pkg; make reinstall.
> >>
> >> This worked, but leaves the record in the pkg-db still on 1.0.3, so any
> >> further portmaster attempt will end in installing the update of pkg
> >> first, which ends up in the nasty message below.
> >>
> >> I can not see this behaviour on any FreeBSD 10.0 box I have around!
> >>
> >> What is wrong here?
> >>
> >> Oliver
> >>
> >> [...]
> >> ===>  Cleaning for pkg-1.0.4_1
> >> You are about to convert your system to pkgng while you have ports/packages
> >> installed with the old pkg_install tools.
> >>
> >> You can choose to:
> >> - keep pkg_install as the package management system by adding this line
> >> to /etc/make.conf:
> >>
> >> WITHOUT_PKGNG=yes
> >>
> >> - switch to pkgng:
> >> 1) Add WITHOUT_PKGNG to /etc/make.conf
> >> 2) Install ports-mgmt/pkg
> >> 3) Convert your package database by running pkg2ng
> >> 4) Remove WITHOUT_PKGNG from /etc/make.conf
> >>
> >> *** [pre-everything] Error code 1
> >>
> >> Stop in /usr/ports/ports-mgmt/pkg.
> >>
> >> ===>>> make failed for ports-mgmt/pkg
> >> ===>>> Aborting update
> >>
> >> ===>>> Update for pkg-1.0.3_1 failed
> >> ===>>> Aborting update
> >>
> >> Terminated
> >>
> >> ===>>> You can restart from the point of failure with this command line:
> >>portmaster  ports-mgmt/pkg devel/pkgconf
> > 
> > Hm, can you look into the directory /var/db/pkg and check there a no 
> > leftovers from the old pkg tools (directories).
> > If there are any old directories the pre-everything target will be executed 
> > and you see this failure.
> > What gives the command pkg_info as output?
> > 
> > --
> > Regards,
> > olli
> > 
> 
> portmaster installs for each port still a directory in /var/db/pkg - so
> there are plenty of directories.
> 
> I deleted them all and tried again - this time the update worked.
> 
> This is very strange and seems to be unlogical.
> 
> Oliver
> 


Some of them were not only portmaster distfiles. Some where leftovers from your
conversion, (the ones with +CONTENTS in them) given that iirc you are now using
pkgng for long, I guess, that it doesn't matter at all, and the left overs were
"fixed" by your regular updates.

regards,
Bapt


pgpAN1Cq12SZW.pgp
Description: PGP signature

Re: wine/i386 for FreeBSD/amd64 port (aka wine-fbsd64)

[Gerald Pfeifer]

On Sat, 3 Nov 2012, David Naylor wrote:
> # Executive Summary
> 
> Over the past years I have been maintaining the wine-fbsd64 port (see 
> http://mediafire.com/wine_fbsd64 for more).  The port itself effectively 
> does static linking (it bundles all the libraries wine needs) with 
> scripts to bootstrap the environment to easily use wine from 
> FreeBSD/amd64.  There is also a script to install the i386 nVidia 
> graphic drivers so that wine has access to nVidia accelerated graphics 
> from FreeBSD/amd64.
> 
> I would like to propose this port gets included in the port's collection 
> and would like to get feedback, your comments please :-).

I would say, go ahead and send-pr the port (without the nVidia parts
for now).

If nobody else bites within two weeks of you sending it, share the number 
with me, and I'll give it a try.  I am sure that, once in, there will be 
many aspects we'll get feedback on and further tweaks and improvements, 
but it seems this is relatively widely used and useful, so let's make
it port of the ports collection and jointly take it from there.

>  - Can only be compiled in an i386 environment, but the resulting package is 
> *intended* for amd64 (although works fine in an i386 environment)
>  - If, somehow, there is a recursive calling of wine programs then 
> LD_(32_)LIBRARY_PATH and PATH will continue to grow with every iteration.  
>  - The pkgng ports cannot be installed in an i386 environment as they are 
> labelled for amd64.  

My primary question at this point, and to this group, is how to
actually name such a port?  

It probably makes sense to focus on wine-devel, initially, but 
given that it's really the 32-bit version that is intended for
the 64-bit OS, how to best reflect that?

wine-devel-fbsd64 as per the current name?  wine-devel-32on64?...??

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

Re: lang/gcc46

[Gerald Pfeifer]

On Mon, 6 Aug 2012, b. f. wrote:
> Oops: I forgot though, that partly due to this policy of not bumping
> gcc shared library versions, we have some shared libraries in the base
> system that conflict with the shared libraries of the various gcc
> ports, and we have been enforcing the right links by inscribing hints
> in the binaries to look first in the right gcc port directories.  But
> if we update lang/gcc from 4.6.x to another major version (e.g.
> 4.7.x), the directory changes, and linking for the old binaries will
> fail.  So let me qualify my earlier answer: you can keep the old
> software working with minimal intervention, for example, by adding a
> symlink from the old directory to the new one.

What we could do, for the canonical version of GCC (lang/gcc,
USE_GCC=yes) is install those libraries into /usr/local/lib
instead of /usr/local/lib/gccXY as we are doing for lang/gccXY.

What do you think?

>>> I had patches to do this even without pkgng, but it made things a 
>>> little more complicated, and didn't seem to be a high priority, so I 
>>> didn't pursue it.  If people feel that it is important, I could work 
>>> with Gerald to revive that
>> Making this change now would benefit a lot of people, now.
> Okay, but since I'm not in charge either, it will require (at least)
> Gerald's consent.

That would be cool.  Bapt wanted to look into this as well a few
months ago, so perhaps the two of you can (should?) sync before
proceeding?

Gerald

PS: I don't think we should go for the other option, static linking.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: java/openjdk6 fails to build..

[Greg Lewis]

On Fri, Dec 28, 2012 at 03:49:56PM -0500, Eitan Adler wrote:
> On 28 December 2012 15:24, Greg Lewis  wrote:
> > On Fri, Dec 21, 2012 at 07:27:22PM -0500, Eitan Adler wrote:
> >> On 21 December 2012 19:16, David Demelier  wrote:
> >> > Yes, I wanted to answser, but the man says that MAKE_JOBS are disabled by
> >> > default, I tried to build with MAKE_JOBS=1 and it works, the problem did
> >> > appear when MAKE_JOBS=6 was set. Can you reproduce the issue?
> >>
> >> I want to mark this MAKE_JOBS_UNSAFE=yes and remove the current hack
> >> Any objection from java@ ?
> >>
> >> > I had MAKE_JOBS=6 in my /etc/make.conf instead of MAKE_JOBS_NUMBER though
> >>
> >> Exactly. MAKE_JOBS is not user-settable. MAKE_JOBS_NUMBER is.  IMHO
> >> MAKE_JOBS should start with an _.
> >
> > I think that's right.  I have no objection.  I think whats in openjdk7
> > is closer to what it should be.
> 
> What is in openjdk7 seems bogus and it isn't clear why it is there:
> MAKE_JOBS_UNSAFE=   yes
> is defined implying that MAKE_JOBS should always be 1 (and -j never set)
> but it does some weird things with the global variables
> MAKE_JOBS_NUMBER and DISABLE_MAKE_JOBS.
> 
> Can the generic handling in b.p.m not work?
> 
> IMHO MAKE_JOBS_SAFE=yes should be defined and either b.p.m or b.java.m
> should be handling the special build code.

MAKE_JOBS_SAFE=yes should not be defined since neither of the ports are
safe for multiple make jobs.  As an exception, the HotSpot portion of the
build is and that is what the other portion handles.

-- 
Greg Lewis  Email   : gle...@eyesbeyond.com
Eyes Beyond Web : http://www.eyesbeyond.com
Information Technology  FreeBSD : gle...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrading ports problem with portupgrade(pkgng)

[Beach Geek]

On Dec 27, 2012 10:08 AM, "Beach Geek"  wrote:
>
>
> > > System: FreeBSD/i386 10-current, base/head(src)=r244363,
ports/head=r309344.
> > >
> > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed
ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db.
> > >
> > > I'm now trying to update my ports (from tree, not pkgs), and I get:
> > >
> > > # portupgrade -ae
> > > USING PKGNG
> > > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually
run 'pkgdb -F' to fix, or specify -O to force.
> > >
> > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use
'pkg check' directly.
> > >
> > > # pkg check -d (also tried pkg check -d -a)
> > > #
> > >
> > > Running portupgrade -ae gives same message as before.
> > >
> > > Went to port tree, upgraded glib with 'make deinstall reinstall
clean'. Then
> > > # pkg info glib glib-2.28.8_5 Some useful routines of C
programming (current stable version)
> > >
> > > Run portupgrade -ae.. same message.
> > >
> > > Could someone point me in the right direction...
> > >
> > > If I'm misunderstanding the man & wiki pages, please explain (I'll
even wear the pointyhat).
> > >
> > > Thanks, BG
> >
> > An update.
> > 4 servers have the problem in my previous post, and I've yet to find a
way to use portupgrade.
> > Only answers I've received were to use packages via pkgng. (Not an
option).
> >
> > For the other 9 servers, I tried it a little differently.
> > -  switch to pkgng
> > -  svn base and ports
> > -  upgrade base
> > -  upgrade ports with portupgrade.
> >
> > Worked fine for 8 of 9.
> >
> > Will be rolling the 5 broke servers back (yes, we have bkups) ;)
> >
> > Will leave the 8 working ones running pkgbg, and see how it goes.
> >
> > Still wondering, how to repair the database w/o pkgfb -F so portupgrade
will work?
> >
> > And as I understand,  poudriere must be used instead of portupgrade to
create packages?
> >
> > Thanks,
> > BG
>
> Please post responses here instead of emailing me directly.
>
> Only "fixes" that have been suggested are:
> * use packages only
> * delete all packages and /usr/local, then reinstall all packages.
>
> For ppl that want to build/install ports from the ports tree, what are
our options for fixing pkg db problems so we can keep ports upgraded?
>
> Note: "pkg check" is missing on wiki page.
>
> BG

My apologies, I missed the replies from Matthew and Baptiste.  They weren't
in my mailbox, saw them while browsing mailing list.

We have clusters of 13 box each. Only 1 cluster is running Current and
using pkgng, and is just for testing/playing. (Other clusters just upgraded
to 9.1)

I try using poudriere, setting up a repo for this cluster. (I guess later a
repo per each different configured cluster)

Thanks for the help and information.
Not sure I understand it yet, but that's what this 'devel' cluster is for.

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

Re: lang/gcc46

[Jeffrey Bouquet]

Sorry for the formatting. Reply is below

--- On Fri, 12/28/12, Gerald Pfeifer  wrote:

From: Gerald Pfeifer 
Subject: Re: lang/gcc46
To: "Brendan Fabeny" , "Baptiste Daroussin" 
Cc: freebsd-ports@freebsd.org, "Kevin Oberman" 
Date: Friday, December 28, 2012, 4:08 PM

On Mon, 6 Aug 2012, b. f. wrote:
> Oops: I forgot though, that partly due to this policy of not bumping
> gcc shared library versions, we have some shared libraries in the base
> system that conflict with the shared libraries of the various gcc
> ports, and we have been enforcing the right links by inscribing hints
> in the binaries to look first in the right gcc port directories.  But
> if we update lang/gcc from 4.6.x to another major version (e.g.
> 4.7.x), the directory changes, and linking for the old binaries will
> fail.  So let me qualify my earlier answer: you can keep the old
> software working with minimal intervention, for example, by adding a
> symlink from the old directory to the new one.

What we could do, for the canonical version of GCC (lang/gcc,
USE_GCC=yes) is install those libraries into /usr/local/lib
instead of /usr/local/lib/gccXY as we are doing for lang/gccXY.

What do you think?

>>> I had patches to do this even without pkgng, but it made things a 
>>> little more complicated, and didn't seem to be a high priority, so I 
>>> didn't pursue it.  If people feel that it is important, I could work 
>>> with Gerald to revive that
>> Making this change now would benefit a lot of people, now.
> Okay, but since I'm not in charge either, it will require (at least)
> Gerald's consent.

That would be cool.  Bapt wanted to look into this as well a few
months ago, so perhaps the two of you can (should?) sync before
proceeding?

Gerald

PS: I don't think we should go for the other option, static linking.
___
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"

..not  a reply but additional information, I hope it is not to off-topic to 
this post.  While trying to install gcc46, it wanted gcc46 already installed 
for some reason.  I had just deleted it "for" the install.  I did a workaround 
of sorts...
___
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: wine/i386 for FreeBSD/amd64 port (aka wine-fbsd64)

[David Naylor]

On 29 Dec 2012 2:03 AM, "Gerald Pfeifer"  wrote:
>
> On Sat, 3 Nov 2012, David Naylor wrote:
> > # Executive Summary
> >
> > Over the past years I have been maintaining the wine-fbsd64 port (see
> > http://mediafire.com/wine_fbsd64 for more).  The port itself effectively
> > does static linking (it bundles all the libraries wine needs) with
> > scripts to bootstrap the environment to easily use wine from
> > FreeBSD/amd64.  There is also a script to install the i386 nVidia
> > graphic drivers so that wine has access to nVidia accelerated graphics
> > from FreeBSD/amd64.
> >
> > I would like to propose this port gets included in the port's collection
> > and would like to get feedback, your comments please :-).
>
> I would say, go ahead and send-pr the port (without the nVidia parts
> for now).
>
> If nobody else bites within two weeks of you sending it, share the number
> with me, and I'll give it a try.  I am sure that, once in, there will be
> many aspects we'll get feedback on and further tweaks and improvements,
> but it seems this is relatively widely used and useful, so let's make
> it port of the ports collection and jointly take it from there.

Thanks, I shall do when I get back from holidays. Might have a surprise up
my sleeve :-)

> >  - Can only be compiled in an i386 environment, but the resulting
package is
> > *intended* for amd64 (although works fine in an i386 environment)
> >  - If, somehow, there is a recursive calling of wine programs then
> > LD_(32_)LIBRARY_PATH and PATH will continue to grow with every
iteration.
> >  - The pkgng ports cannot be installed in an i386 environment as they
are
> > labelled for amd64.
>
> My primary question at this point, and to this group, is how to
> actually name such a port?
>
> It probably makes sense to focus on wine-devel, initially, but
> given that it's really the 32-bit version that is intended for
> the 64-bit OS, how to best reflect that?
>
> wine-devel-fbsd64 as per the current name?  wine-devel-32on64?...??

I think there is precedent for the naming. Consider Linux ports, those
ports take the prefix "linux-" to indicate the architecture so I propose
"i386-wine-devel" to indicate a port that has binaries from the i386
architecture.

Regards,
___
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.1-RC3: xorg-input-mouse, xfce4-panel

[Adrian Chadd]

On 28 December 2012 04:02, Kimmo Paasiala  wrote:

> It doesn't look like the FreeBSD ports SVN repository is used to its
> full potential. SVN allows branching and creation of experimental
> versions of the tree very easily and cheaply, yet all the experimental
> repositories references so far are stored in some external
> repositories, github or elsewhere.
>
> What gives?

Because then people who wish to create experimental branches of a
rather large ports SVN tree would end up populating the core SVN repo,
which is reproduced on mirrors (both ours and whoever else wishes to
mirror the SVN repository.)

So the current method in src/ is to work out hacks in local mirrors of
the repository (eg via svn -> git gateways) and then when it's time to
start some public work - create a branch, do the hacking, merge it
into HEAD when it's ready.

That way it can also be worked on by non-FreeBSD contributors. Just
like what people do for Linux, who don't have kernel.org accounts.

I won't speak for the ports people but just keep that in mind. There's
sometimes larger scale issues abound. :-)

And before you say "but but but but but but git!" please keep in mind
that there's no such thing as a central GIT repository that _everyone_
dumps their work in, like what would happen if one created an SVN
branch for projects (in src, ports, doc, etc.) Everyone has their own
git repository forks and they push patches to "more authoritative"
trees over time.


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

FreeBSD Port: rubygem-chef-0.10.8_1

[Douglas Thrift]

Hello,

Are there any plans to update to Chef 10.16.4?

Thanks!
-- 
Douglas William Thrift


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