> Have you tried just setting PORTSDIR and letting bsd.port.mk set the
> rest of the paths with their defaults that are relative to PORTSDIR? If
> that works, then we can start hunting for places that are not handling
> absolute vs. relative paths correctly in bsd.port.mk.
Now, with only:
PORT
On 2010-03-12 22:36:54, Greg Larkin wrote:
> Hi xw,
>
> I noticed something strange here. How is WRKDIR (in this case
> "/var/ports/work/var/ports/tree/devel/eggdbus/work") defined? It looks
> like bsd.port.mk combined your WRKDIRPREFIX and PORTSDIR to create that
> path, but skimming the code,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xorquew...@googlemail.com wrote:
[...]
> DISTDIR= /var/ports/distfiles
> PACKAGES= /var/ports/packages
> WRKDIRPREFIX= /var/ports/work
> PORTSDIR= /var/ports/tree
>
> jail# vi /etc/profile
> FTP_PASSIVE_MODE=yes
> HTTP_PROXY=10.1.3.3:
Sent from my HTC
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
This is a complete lot of how to reproduce the various errors I've
seen with 'make package-recursive'. I've checked the pointyhat logs
and there are no errors logged for the packages involved here. There
seems to be a bug somewhere in ports. I've used inkscape as a scapegoat
here but the errors occ
In article <10609484503...@192.168.2.69> you write:
>Hi,
>
>Andrey V. Elsukov wrote:
>> Can you show `pciconf -l` output?
>
># pciconf -l
>hos...@pci0:0:0:0: class=0x06 card=0x50001458 chip=0x79111002
>rev=0x00 hdr=0x00
>pc...@pci0:0:1:0: class=0x060400 card=0x79121002 chip=0x791210
On behalf of the 5th International Workshop on Systems Software
Verification (SSV '10) program committee, we'd like to invite you to
contribute papers that focus on finding real, applicable solutions to
systems software verification problems. Paper registration and abstracts
are due Friday, May 28
Hi.
Im busy implementing a kernel module to enable me to read/write
certain control registers for a PCI card. I do not wish to modify the
existing driver, merely create an add-on module that can be loaded to
accomplish what I need.
I can easily get the device_t structure of the device, and I know
On Friday 12 March 2010 04:29 am, Kostik Belousov wrote:
> On Thu, Mar 11, 2010 at 06:15:07PM -0500, Jung-uk Kim wrote:
> > On Thursday 11 March 2010 04:55 pm, Marcel Moolenaar wrote:
> > > On Mar 11, 2010, at 1:24 PM, Jung-uk Kim wrote:
> > > > While I was debugging syscalls, I found a very useful
"Matthias Andree" writes:
> Dag-Erling Smørgrav writes:
> > Matthias Andree writes:
> > > sendmail's configuration was never a black art unless you needed
> > > features beyond what the m4 macro set supported.
> > The m4 macro set is a fairly recent development.
> If "more than a decade" is a "f
On Thu, Mar 11, 2010 at 06:15:07PM -0500, Jung-uk Kim wrote:
> On Thursday 11 March 2010 04:55 pm, Marcel Moolenaar wrote:
> > On Mar 11, 2010, at 1:24 PM, Jung-uk Kim wrote:
> > > While I was debugging syscalls, I found a very useful field in
> > > struct thread, td_errno. It seems it was added f
Dag-Erling Smørgrav wrote on 2010-03-11:
Matthias Andree writes:
sendmail's configuration was never a black art unless you needed
features beyond what the m4 macro set supported.
The m4 macro set is a fairly recent development.
If "more than a decade" is a "fairly recent development", then
12 matches
Mail list logo
