Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Saturday 24 July 2004 12:52 pm, Matthew Seaman
<[EMAIL PROTECTED]> wrote:
> On Sat, Jul 24, 2004 at 11:25:16AM -0700, Joshua Tinnin wrote:
> > On Saturday 24 July 2004 10:00 am, Matthew Seaman
> > <[EMAIL PROTECTED]> wrote:
> > > On Sat, Jul 24, 2004 at 09:12:47AM -0700, Joshua Tinnin wrote:
> > > > smogmonster# portsdb -uU
> > > > Updating the ports index ... Generating INDEX.tmp - please
> > > > wait.."Makefile", line 34: Malformed conditional (${XFREE86_VERSION}
> > > > == 3 && !defined(WITHOUT_X))
> > > > "Makefile", line 36: if-less endif
> > > > "Makefile", line 36: Need an operator
> > > > make: fatal errors encountered -- cannot continue
> > > > ===> chinese/arphicttf failed
> > > > *** Error code 1
> > > > 1 error
> > >
> > > Run cvsup(1) again -- looks like you managed to cvsup in the middle of
> > > all of the commits being made to add the xorg capability to the ports
> > > tree. It's been fixed now.
> >
> > I hate to tell you this, but I tried it again and it's still getting this
> > error. BTW, I'm updating ports-all.
>
> Then take 'chinese' out of your refuse file. In fact, if you want to
> be able to build an INDEX yourself, you have to take all of the
> language categories out of the refuse file.
>
> Otherwise, just download a recently built INDEX by:
>
> # make fetchindex
>
> and forget all about running portsdb before running portupgrade.
I appreciate this. I went ahead and renamed my refuse file, and portsdb -Uu
(does the order of the options matter?) worked after that. I was focused too
much on the XFree86/XOrg issue and didn't see that was the problem.
Thanks again,
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Sat, Jul 24, 2004 at 11:25:16AM -0700, Joshua Tinnin wrote:
> On Saturday 24 July 2004 10:00 am, Matthew Seaman
> <[EMAIL PROTECTED]> wrote:
> > On Sat, Jul 24, 2004 at 09:12:47AM -0700, Joshua Tinnin wrote:
> > > smogmonster# portsdb -uU
> > > Updating the ports index ... Generating INDEX.tmp - please
> > > wait.."Makefile", line 34: Malformed conditional (${XFREE86_VERSION} == 3
> > > && !defined(WITHOUT_X))
> > > "Makefile", line 36: if-less endif
> > > "Makefile", line 36: Need an operator
> > > make: fatal errors encountered -- cannot continue
> > > ===> chinese/arphicttf failed
> > > *** Error code 1
> > > 1 error
> >
> > Run cvsup(1) again -- looks like you managed to cvsup in the middle of
> > all of the commits being made to add the xorg capability to the ports
> > tree. It's been fixed now.
>
> I hate to tell you this, but I tried it again and it's still getting this
> error. BTW, I'm updating ports-all.
Then take 'chinese' out of your refuse file. In fact, if you want to
be able to build an INDEX yourself, you have to take all of the
language categories out of the refuse file.
Otherwise, just download a recently built INDEX by:
# make fetchindex
and forget all about running portsdb before running portupgrade.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgpqjffjHoDHF.pgp
Description: PGP signature
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Saturday 24 July 2004 10:00 am, Matthew Seaman
<[EMAIL PROTECTED]> wrote:
> On Sat, Jul 24, 2004 at 09:12:47AM -0700, Joshua Tinnin wrote:
> > smogmonster# portsdb -uU
> > Updating the ports index ... Generating INDEX.tmp - please
> > wait.."Makefile", line 34: Malformed conditional (${XFREE86_VERSION} == 3
> > && !defined(WITHOUT_X))
> > "Makefile", line 36: if-less endif
> > "Makefile", line 36: Need an operator
> > make: fatal errors encountered -- cannot continue
> > ===> chinese/arphicttf failed
> > *** Error code 1
> > 1 error
>
> Run cvsup(1) again -- looks like you managed to cvsup in the middle of
> all of the commits being made to add the xorg capability to the ports
> tree. It's been fixed now.
I hate to tell you this, but I tried it again and it's still getting this
error. BTW, I'm updating ports-all.
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Sat, Jul 24, 2004 at 09:12:47AM -0700, Joshua Tinnin wrote:
> smogmonster# portsdb -uU
> Updating the ports index ... Generating INDEX.tmp - please wait.."Makefile",
> line 34: Malformed conditional (${XFREE86_VERSION} == 3
> && !defined(WITHOUT_X))
> "Makefile", line 36: if-less endif
> "Makefile", line 36: Need an operator
> make: fatal errors encountered -- cannot continue
> ===> chinese/arphicttf failed
> *** Error code 1
> 1 error
Run cvsup(1) again -- looks like you managed to cvsup in the middle of
all of the commits being made to add the xorg capability to the ports
tree. It's been fixed now.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgpBZV2xjeb82.pgp
Description: PGP signature
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
Joshua Tinnin wrote:
On Saturday 24 July 2004 08:36 am, Bob Perry <[EMAIL PROTECTED]> wrote:
Joshua Tinnin wrote:
On Saturday 24 July 2004 07:36 am, Joshua Tinnin <[EMAIL PROTECTED]>
wrote:
On Friday 23 July 2004 10:10 pm, Bob Perry <[EMAIL PROTECTED]> wrote:
Just cvsup'd my system for the weekend and found three additions
to the /usr/ports/CHANGES file. They referenced a replacement of
the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable,
a big update to PHP ports and bsd.php.mk to add more flexibility plus
an announcement that "OpenLDAP version 2.2 is now the default..."
I'm still learning FreeBSD and deal with issues as they come up. I
remember reading postings regarding the XFree86 issue but thought
I had the option to leave well enough alone. Maybe not.
I don't know about the other two, but as for the X_WINDOW_SYSTEM
variable, it looks to me like it's related to this:
http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html
It only applies to -CURRENT right now, but it's as easy as adding a line
to rc.conf if you want to stay with XFree86.
Sorry, that should have been make.conf. It's too early ...
JT,
Thanks for the update. Just read all of the related messages and I think I
can handle this.
Need to pause for a moment and give myself a FreeBSD pep talk.
Thanks again.
Well, that being said, I did just encounter a problem when trying to update
the ports database after a cvsup (running 5.2.1-RELEASE-p9 with XOrg):
smogmonster# portsdb -uU
Updating the ports index ... Generating INDEX.tmp - please wait.."Makefile",
line 34: Malformed conditional (${XFREE86_VERSION} == 3
&& !defined(WITHOUT_X))
"Makefile", line 36: if-less endif
"Makefile", line 36: Need an operator
make: fatal errors encountered -- cannot continue
===> chinese/arphicttf failed
*** Error code 1
1 error
My /etc/make.conf is:
# Created: Fri Apr 16 06:11:06 2004
# Setting to use base perl from ports:
PERL_VER=5.6.1
PERL_VERSION=5.6.1
PERL_ARCH=mach
NOPERL=yo
NO_PERL=yo
NO_PERL_WRAPPER=yo
CPUTYPE?=athlon-xp
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
#X_WINDOW_SYSTEM=xorg
I commented the line with the new X_WINDOW_SYSTEM variable to see if that were
the problem, but it didn't change anything.
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
This is what I found in the CHANGE file. I'm sure you already read it
but maybe
there's something that could help by taking a second look. This is the
best that I
can offer:
20040723:
AUTHOR: [EMAIL PROTECTED]
The XFREE86_VERSION variable is replaced by the X_WINDOW_SYSTEM variable.
XFREE86_VERSION may no longer be used by ports Makefiles.
X_WINDOW_SYSTEM may
currently be set to xorg, xfree86-4, and xfree86-3 (please use :L in
checking
it). Several X_*_PORT variables are provided by bsd.port.mk which map
to the
appropriate port for the X_WINDOW_SYSTEM chosen.
Bob Perry
--
I've learned that whatever hits the fan will not be evenly
distributed.
FreeBSD 4.9-RELEASE-p2 #0
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Saturday 24 July 2004 08:36 am, Bob Perry <[EMAIL PROTECTED]> wrote:
> Joshua Tinnin wrote:
> >On Saturday 24 July 2004 07:36 am, Joshua Tinnin <[EMAIL PROTECTED]>
> >
> >wrote:
> >>On Friday 23 July 2004 10:10 pm, Bob Perry <[EMAIL PROTECTED]> wrote:
> >>>Just cvsup'd my system for the weekend and found three additions
> >>>to the /usr/ports/CHANGES file. They referenced a replacement of
> >>>the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable,
> >>>a big update to PHP ports and bsd.php.mk to add more flexibility plus
> >>>an announcement that "OpenLDAP version 2.2 is now the default..."
> >>>
> >>>I'm still learning FreeBSD and deal with issues as they come up. I
> >>>remember reading postings regarding the XFree86 issue but thought
> >>>I had the option to leave well enough alone. Maybe not.
> >>
> >>I don't know about the other two, but as for the X_WINDOW_SYSTEM
> >> variable, it looks to me like it's related to this:
> >>
> >>http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html
> >>
> >>It only applies to -CURRENT right now, but it's as easy as adding a line
> >> to rc.conf if you want to stay with XFree86.
> >
> >Sorry, that should have been make.conf. It's too early ...
>
> JT,
> Thanks for the update. Just read all of the related messages and I think I
> can handle this.
>
> Need to pause for a moment and give myself a FreeBSD pep talk.
>
> Thanks again.
Well, that being said, I did just encounter a problem when trying to update
the ports database after a cvsup (running 5.2.1-RELEASE-p9 with XOrg):
smogmonster# portsdb -uU
Updating the ports index ... Generating INDEX.tmp - please wait.."Makefile",
line 34: Malformed conditional (${XFREE86_VERSION} == 3
&& !defined(WITHOUT_X))
"Makefile", line 36: if-less endif
"Makefile", line 36: Need an operator
make: fatal errors encountered -- cannot continue
===> chinese/arphicttf failed
*** Error code 1
1 error
My /etc/make.conf is:
# Created: Fri Apr 16 06:11:06 2004
# Setting to use base perl from ports:
PERL_VER=5.6.1
PERL_VERSION=5.6.1
PERL_ARCH=mach
NOPERL=yo
NO_PERL=yo
NO_PERL_WRAPPER=yo
CPUTYPE?=athlon-xp
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
#X_WINDOW_SYSTEM=xorg
I commented the line with the new X_WINDOW_SYSTEM variable to see if that were
the problem, but it didn't change anything.
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
Joshua Tinnin wrote: On Saturday 24 July 2004 07:36 am, Joshua Tinnin <[EMAIL PROTECTED]> wrote: On Friday 23 July 2004 10:10 pm, Bob Perry <[EMAIL PROTECTED]> wrote: Just cvsup'd my system for the weekend and found three additions to the /usr/ports/CHANGES file. They referenced a replacement of the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable, a big update to PHP ports and bsd.php.mk to add more flexibility plus an announcement that "OpenLDAP version 2.2 is now the default..." I'm still learning FreeBSD and deal with issues as they come up. I remember reading postings regarding the XFree86 issue but thought I had the option to leave well enough alone. Maybe not. I don't know about the other two, but as for the X_WINDOW_SYSTEM variable, it looks to me like it's related to this: http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html It only applies to -CURRENT right now, but it's as easy as adding a line to rc.conf if you want to stay with XFree86. Sorry, that should have been make.conf. It's too early ... JT, Thanks for the update. Just read all of the related messages and I think I can handle this. Need to pause for a moment and give myself a FreeBSD pep talk. Thanks again. Bob Perry -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Saturday 24 July 2004 07:36 am, Joshua Tinnin <[EMAIL PROTECTED]> wrote: > On Friday 23 July 2004 10:10 pm, Bob Perry <[EMAIL PROTECTED]> wrote: > > Just cvsup'd my system for the weekend and found three additions > > to the /usr/ports/CHANGES file. They referenced a replacement of > > the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable, > > a big update to PHP ports and bsd.php.mk to add more flexibility plus > > an announcement that "OpenLDAP version 2.2 is now the default..." > > > > I'm still learning FreeBSD and deal with issues as they come up. I > > remember reading postings regarding the XFree86 issue but thought > > I had the option to leave well enough alone. Maybe not. > > I don't know about the other two, but as for the X_WINDOW_SYSTEM variable, > it looks to me like it's related to this: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html > > It only applies to -CURRENT right now, but it's as easy as adding a line to > rc.conf if you want to stay with XFree86. Sorry, that should have been make.conf. It's too early ... - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
On Friday 23 July 2004 10:10 pm, Bob Perry <[EMAIL PROTECTED]> wrote: > Just cvsup'd my system for the weekend and found three additions > to the /usr/ports/CHANGES file. They referenced a replacement of > the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable, > a big update to PHP ports and bsd.php.mk to add more flexibility plus > an announcement that "OpenLDAP version 2.2 is now the default..." > > I'm still learning FreeBSD and deal with issues as they come up. I > remember reading postings regarding the XFree86 issue but thought > I had the option to leave well enough alone. Maybe not. I don't know about the other two, but as for the X_WINDOW_SYSTEM variable, it looks to me like it's related to this: http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032267.html It only applies to -CURRENT right now, but it's as easy as adding a line to rc.conf if you want to stay with XFree86. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to Handle the Three Newest Additions to the /usr/ports/CHANGES?
Just cvsup'd my system for the weekend and found three additions to the /usr/ports/CHANGES file. They referenced a replacement of the XFREE86_VERSION variable by the X_WINDOW_SYSTEM variable, a big update to PHP ports and bsd.php.mk to add more flexibility plus an announcement that "OpenLDAP version 2.2 is now the default..." I'm still learning FreeBSD and deal with issues as they come up. I remember reading postings regarding the XFree86 issue but thought I had the option to leave well enough alone. Maybe not. Not sure I understand fully what the other two are all about yet. Looks like I have a long weekend ahead of me. Think I'll postpone the portupgrade until I research these changes further. Is there more detail provided somewhere on these three changes? Thanks, Bob Perry -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
