Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2004 03:59:45 -0000
From:      Mathieu Arnold <mat@mat.cc>
To:        pf4freebsd@freelists.org
Subject:   [pf4freebsd] Re: Version 2.03 - m_copym panic (and others)
Message-ID:  <134924046.1075459163@pouet.in.mat.cc>
In-Reply-To: <20040130092639.GA33809@kt-is.co.kr>
References:  <200401291603.23944.max@love2party.net> <9609296.1075400143@andromede.faubourg.reaumur.net> <20040130015907.GA86565@kt-is.co.kr> <132624359.1075456863@pouet.in.mat.cc> <20040130092639.GA33809@kt-is.co.kr>

next in thread | previous in thread | raw e-mail | index | archive | help
+-Le 30/01/2004 18:26 +0900, Pyun YongHyeon =3DE9crivait :
| On Fri, Jan 30, 2004 at 10:01:03AM +0100, Mathieu Arnold wrote:
|  > +-Le 30/01/2004 10:59 +0900, Pyun YongHyeon ?crivait :
|  > |  > Stop in /usr/o/usr/ports/security/pf/work/pf_freebsd_2.02.
|  > |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|  > |  > *** Error code 1
|  > |  >=3D20
|  > |  > Stop in /usr/ports/security/pf.
|  > |            ^^^^^^^^^^^^^^^^^^^^^^
|  > |=3D20
|  > | I don't know why port system try to use "/usr/o/usr/ports" =3D
directory.
|  > | (symbolic link or NFS mounted?)
|  > | If your ports tree reside in "/usr/o/usr/ports", you may need to
|  > | define PORTSDIR environment variable. See ports(7) for available
|  > | other environment variables.
|  >=3D20
|  > Hum, /usr/ports is NFS mounted, and to avoid building everything in
|  > /usr/ports which would lead to much much traffic and reduce compile
| speed  > (or because it's mounted from a CDROM being read only), you ca=
n
| define :  > WRKDIRPREFIX=3D3D/some/path/to/somewhere/you/can/write
|  > in your make.conf. See make.conf(5) for more details. Being also
|  > mat@FreeBSD.org, I guess that is a part I know a bit ;)
|  >=3D20
|  > The problem lines in lines like this :
|  >=3D20
|  > mtag =3D3D m_tag_get(PACKET_TAG_PF_QID, sizeof(*atag), M_NOWAIT);
|  >=3D20
|  > it's the sizeof(*atag) gcc does not like. Why, I quite frankly don't
| know.  >=3D20
|=3D20
| I don't know why gcc complain this. If ALTQ was installed successfully,
| this should not happen.(At least, it always work for me.)

Well, altq works (5.2-beta2 patch), and old pf 2.00 works too, but I'd
rather have a newer version :)

| If your /usr/ports is NFS mounted, util.mk in include/mk/util.mk can
| link sys directory incorrectly.

I don't see why, I've been using this NFS mounted installations for years=
,
with all my servers, and never had I any trouble with it. Moreover, I hav=
e
pf 2.00 compiled on it.

| At present, util.mk assume the following ALTQ directory:
| 	1. /usr/src/sys.altq or
| 	2. /sys or
| 	3. /usr/src/sys

2 and 3 leads to 1.

| Please check symbolic links for '@' and 'machine' were set correctly.
| (See work/pf_freebsd_2.02/pf after compilation failure.)

lrwxr-xr-x  1 root  wheel      17 30 jan 10:33 @@ -> /usr/src/sys.altq
lrwxr-xr-x  1 root  wheel      30 30 jan 10:33 machine@ ->
/usr/src/sys.altq/i386/include

looks good.

| If the link was set correctly, check the existence of stale header
| files in your system.

Which header file do you think of ? I've checked if_altq.h as it seems to
be the only included one. I only have one version of it.

--=3D20
Mathieu Arnold




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?134924046.1075459163>