Since the release has been pushed back some more since the last mail, we
do have some time to test a possible fix for the issues we're seeing
with libtool on FreeBSD 10.0. However, fixing libtool is only part of
the problem as hundreds, if not thousands, of ports roll their own
detection and need
Hi!
> >> On a newly installed development machine I installed
> subversion-freebsd
> >> from ports and ended up with a huge dependency chain.
> > If you're just using it for FreeBSD you can un-check all
> the OPTIONS. If
> > you might want to use the http:// protocol to check
> something out th
On Mon, October 10, 2011 18:38, Phil Oleson wrote:
> On 10/10/11 15:30, Nenhum_de_Nos wrote:
>>
>> On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote:
>>>
>>> On Sat, October 8, 2011 20:03, Doug Barton wrote:
On 10/08/2011 14:53, Warren Block wrote:
> nspluginwrapper needs to be run as th
On Mon, 10 Oct 2011 12:04:19 -0700
Stanislav Sedov mentioned:
> On Sat, 8 Oct 2011 18:35:13 +0100
> Chris Rees mentioned:
>
> >
> > Last I heard, portmgr explicitly disapproved of this fix-- have I missed
> > something??? Erwin specifically said not to do it.
> >
> > Since when can anyone jus
On Mon, Oct 10, 2011 at 1:33 PM, Hartmann, O.
wrote:
> On 10/10/11 21:04, Stanislav Sedov wrote:
>> On Sat, 8 Oct 2011 18:35:13 +0100
>> Chris Rees mentioned:
>>
>>> Last I heard, portmgr explicitly disapproved of this fix-- have I missed
>>> something??? Erwin specifically said not to do it.
>>>
On 10/10/11 15:30, Nenhum_de_Nos wrote:
>
> On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote:
>>
>> On Sat, October 8, 2011 20:03, Doug Barton wrote:
>>> On 10/08/2011 14:53, Warren Block wrote:
nspluginwrapper needs to be run as the end user.
>>>
>>> The pkg-message tells them to do that.
On Mon, Oct 10, 2011 at 1:59 PM, Doug Barton wrote:
> Until the pointy-haireds come up with a better solution, here is a patch
> that incorporates work that others have done into a manageable form so
> that those interested in working with ports on 10-current have some
> tools to work with:
>
> ht
On 10/09/2011 09:29, Hajimu UMEMOTO wrote:
> Hi,
>
>> On Fri, 07 Oct 2011 16:48:52 -0700
>> Doug Barton said:
>
> dougb> In case anyone wants to take this on, this port fails to install on
> 10.0
> dougb> because it uses its own version of libtool. I took a quick look but
> dougb> there
On 10/10/2011 15:00, Nali Toja wrote:
> Doug Barton writes:
>
>> Until the pointy-haireds come up with a better solution, here is a patch
>> that incorporates work that others have done into a manageable form so
>> that those interested in working with ports on 10-current have some
>> tools to wo
Doug Barton writes:
> Until the pointy-haireds come up with a better solution, here is a patch
> that incorporates work that others have done into a manageable form so
> that those interested in working with ports on 10-current have some
> tools to work with:
>
> http://dougbarton.us/bam.patch
[.
On Sun, October 9, 2011 13:39, Nenhum_de_Nos wrote:
>
> On Sat, October 8, 2011 20:03, Doug Barton wrote:
>> On 10/08/2011 14:53, Warren Block wrote:
>>> nspluginwrapper needs to be run as the end user.
>>
>> The pkg-message tells them to do that.
>
> ops, haven't seen it though. all the ports cle
Until the pointy-haireds come up with a better solution, here is a patch
that incorporates work that others have done into a manageable form so
that those interested in working with ports on 10-current have some
tools to work with:
http://dougbarton.us/bam.patch
You need to do the equivalent of '
On 10/10/11 21:04, Stanislav Sedov wrote:
> On Sat, 8 Oct 2011 18:35:13 +0100
> Chris Rees mentioned:
>
>> Last I heard, portmgr explicitly disapproved of this fix-- have I missed
>> something??? Erwin specifically said not to do it.
>>
>> Since when can anyone just commit stuff to bsd.port.mk, re
On Sat, 8 Oct 2011 18:35:13 +0100
Chris Rees mentioned:
>
> Last I heard, portmgr explicitly disapproved of this fix-- have I missed
> something??? Erwin specifically said not to do it.
>
> Since when can anyone just commit stuff to bsd.port.mk, regardless of its
> location?
>
> This is a bad
John wrote:
> > ... gpart should show warning message if user is trying to put
> > GPT on non real disk devices.
...
>This also seem to prevent something useful like:
>
> # camcontrol inquiry da0
> pass2: Fixed Direct Access SCSI-5 device
> pass2: Serial Number 3TB1BKGX9036W9EN
> pass2:
Lev Serebryakov wrote:
> >> GPT _must_ be placed twice -- at first and last sectors
> >> (really, more than one sectors). By standard. Secondary
> >> copy must be at end of disk. Period.
> > Then, "by standard" GPT cannot coexist with GLABEL. Such setup
> > should be disallowed, or at least big n
Lev Serebryakov wrote:
> GPT must have backup copy in last sector by standard ...
In that case, shouldn't it refuse to install on any provider that is
not in fact a disk, so as not to create configurations that cannot
work properly?
> MBR doesn;t have any additional metadata. How adding one wil
ok, I'll do some more detailed testing in the next few days.
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Friday 07 October 2011 08:32:40 Adrian Chadd wrote:
> On 7 October 2011 13:55, Garrett Cooper wrote:
> >> Has anyone seen this before?
> >>
> >> This is _not_ plug/unplug the active storage device, or another
> >> storage device. This is when doing IO on a storage device (whether the
> >> root
2011/10/9 Larry Rosenman :
> I had gotten a PR about sysutils/lsof not compiling with clang.
That could be mine, ports/160544 ?
> I had
> Vic Abell check it out, and the problem is NOT with lsof per se, but
> with the system headers.
>
> Is there a project afoot to update the system headers to ma
20 matches
Mail list logo
