* From: Chuck Robey
* I'm very close to relying on packages for them. I'll have to see if
* there are *very* up-to-date packages. If there aren't, and I end up
As long as they build, FTP packages are usually within one week
(usually less) of the ports tree on both 3.1 and 4.0.
-PW
To Uns
* From: John Polstra
* Yep, alas, that's progression for ye. We have never supported mix
* & match of sourceballs from different releases. We do our best
* to support running old executables on newer systems, but that's a
* completely different issue.
:
* I am only speaking for John Pols
* Weird that CoolEdit is on that list.
*
* I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work
* a-ok after patching up ltconfig to make shared libs.
Did you click on the links to see what it's complaining about?
"It worked here" doesn't mean much in this context, as the
* From: "David O'Brien"
* I don't believe there are any C++ programs in XFree86, so you would be
* Ok. You would have noticed that C++ programs would not link.
Ok, thanks. BTW, the list of ports that built in 3.1 but failed in
4.0 are in
http://bento.freebsd.org/~asami/errorlogs/4-latest-3
* From: "David O'Brien"
* I wouldn't trust that 4.0-snap. That one should have a broken
* /usr/lib/libstdc++. I can send you working versions if you need.
*
* The 19990407 4.0-snap should be gold (well silver as we are still using
* the worse of the excptions stack unwinding method, jdp
* From: "David O'Brien"
*
* Hi all,
*
* I just committed a fix to the libstdc++ errors people see on the initial
* bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining
* bootstrap problems.
I don't know about the bootstrapping problems but 4.0-snaps started
showing up again
* From: "Jordan K. Hubbard"
* As long as that directory is not /var/db/pkg, where I put my package
* information, I agree that it doesn't matter either. :-)
Ok. I'll move it out then.
* I'm not sure that this is a solution so much as a band-aid, however.
Of course. It's more of a safety
* From: "David O'Brien"
* So the fix we mentioned might not be needed with the base EGCS. Maybe
* you can just compile all the ports just to see where we stand. I don't
Well, as soon as the first snapshot with the system egcs is released,
I'm planning to grab it and run the build through it
* From: Mikhail Teterin
* With the latest changes to the bsd.port.mk, my local setting (in
* /etc/make.conf) of:
* FETCH_CMD=/usr/local/bin/runsocks /usr/bin/fetch -p
* is ignored. It uses the default /usr/bin/fetch, which does nto work
* for me...
That's weird. The only change aroun
* From: Richard Wackerbarth
* I have to agree that the problem is real.
* However, let me point out that a "one identifier" solution is
* very short sided.
sighted :>
* There are two distinct environments to be considered.
* The HOST environment and the TARGET environment.
*
* From: "Matthew D. Fuller"
* [ Yes, I'm sticking my nose in where it probably doesn't belong and
* should get chopped off for it. It's a hobby ;]
Don't worry, I enjoy chopping off noses. :)
* On Thu, Apr 01, 1999 at 02:36:14AM -0800, a little birdie told m
* From: "Jordan K. Hubbard"
*
* Committing /var/db/pkg to mtree was fine, it probably should have been
* there to begin with. Sticking things into it outside of pkg_add,
* however, is evil. pkg_add "owns" this directory and every time we've
* tried to go behind its back, so to speak, we'v
* From: "Chad R. Larson"
* CVSup'd RELENG_2_2 this afternoon, did make install in
* /usr/src/share/mk. Still no good.
Oh yes, RELENG_2_2. Sorry, fixed.
-W
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
* From: Dom Mitchell
* Just a side note; this new file breaks pkg_info. I've appended a simple
* patch below; somebody ought to do something better for the version in
* the src tree.
Eek. I didn't know it tries to open all files without checking
whether it's a directory or not
*
* From: John Hay
* Now that "make world" do something in /var/db/pkg, shouldn't /var/db/pkg
* be added to the mtree list for 3.1-STABLE and current? Otherwise a
* make release will break and also a make world if you haven't installed
* any packages yet.
Oh, so *that* was what was breaking r
15 matches
Mail list logo
