Any FreeBSD port around GCC
probably would want to use those - which is not the case right now.
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
sd-mips
> -rw-r--r-- 1 root wheel231 Dec 25 19:25:26 2019 xtoolchain.mk.in
>
> is missing the patch-clang-vec_step that is in:
>
> FBSDG5L2# ls -laT /usr/ports/lang/gcc9/files/
That is a hack that can be used to work around the issue; I strongly
rec
ne legitimate configuration on the planet where a
PORTREVISION bump is required, we have to perform it in our repository.
(This is not saying I may not have made a mistake somewhere, but in
general those bumps do appear necessary.)
Gerald
___
freebsd-p
your ports tree?
I just double checked, and
r507371 | gerald | 2019-07-26 20:35:21 + (Fr., 26 Juli 2019) | 7 lines
Update the default version of GCC as pulled in via USE_GCC=yes and a
myriad of other ways from GCC 8 (8.3 right now) to GCC 9 (9.1 right now).
landed in the tree directly
statically)
IGNORE= GCC requires dynamically linked binutils
.endif
Now the question is: How to implement something like this practically?
Gerald @FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
l
so lang/gcc9 will then get it as well.
Hope this simplifies things for our users!
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Hmm, I received zero feedback on this proposal, when it appeared
important for a number of users.
What's your take, Andreas, Tijl (your patch essentially with a bit
of an updated description), and toolchain?
Gerald
On Wed, 27 Feb 2019, Gerald Pfeifer wrote:
> Hi Tijl, hi everyone,
>
ompatible (since _Unwind* is
> part of the ABI). This isn't a blocker for the patch.
>
> I emailed the patch to gerald on 2017-02-21. He responded in the usual
> way that he prefers patches submitted upstream and because I thought the
> patch would not be accepted upstream he
On Tue, 26 Feb 2019, Tobias Kortkamp wrote:
> Added in https://svnweb.freebsd.org/changeset/ports/493984
You. Rock. Tobias.
Thank you!
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
nd package/maintain this, please?
Thanks,
Gerald
PS: I have not been using FreeBSD on a desktop for some 15 years and
zero expertise around sound, plus lack time, so really need help.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.o
is that I don't know what to put in instead of
... there given that different lang/gcc* ports do carry the same
libraries (and usually with the same .so version).?
Gerald
Index: bsd.gcc.mk
===
--- bsd.gcc.mk (revision
slimming in their rpms:
For the more current lang/gcc* ports (not the gcc5-aux and gcc6-aux
ports which I do not maintain) I have now removed packaging the headers
processed by fixincludes, so any problems in that direction should be
gone.
Gerald
___
f
your patch is out of spec.
(I have had lang/gcc7 essentially ready for weeks, alas on a system that is a
dead brick due to loss of its power brick and me traveling. Should be finally
addressed by the end of this week.)
Gerald
___
freebsd-ports@
d be fine, it's a number of ports that are not (even blocking
the move from GCC 5 to 6 as default).
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
st important since it's the default; then 6; 4.x is
for retro computing fans ;-), so 7 will then be next.
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
,
not STABLE (and hence hoped we'd have more time for this change).
My Internet connectivity right now is only slightly above pigeon speed, so
sorry for any delays.
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
On Sun, 28 May 2017, Gerald Pfeifer wrote:
> What do you guys think about the following patch for emulators/wine
> to help clarify this?
I now applied this to help clarify for others (just changing
lang/i386-wine to emulators/i386-wine - too much lang/gcc* work
recently ;-).
ith 32-bit Windows binaries use lang/i386-wine.
> - On an amd64 environment with 64-bit Windows binaries use lang/wine.
What do you guys think about the following patch for emulators/wine
to help clarify this?
Gerald
Index: pkg-descr
we ignore those
complaints from the QA framework or patch individual ports?
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
C do not use our
install-* tools, but a script install-sh (which you can find at the root
of the GCC source tree that uses cp, chmod, strip,... for compatibility
reasons with many systems).
So I guess setting BINMODE=755 is the best option if we want binaries
and libraries in the gcc* ports stripp
rs the compilation is based on a
> bootstrap compiler which already carries outdated headers.
> A workaround, suggested by gerald@ the last time a similar issue
> happened was to run for install-tools/fixinc.sh. I think that may
> regenerate the headers and let the build use updated he
ways_ picked the first, confirming your point. Or is
that only the case for `make makesum`?
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
As some of you may have seen, I have done a bit of work on
bsd.sites.mk recently.
One question I ran into: If a site offers both HTTPS and HTTP,
which of the two do we prefer? (Or do we want to list both?)
Gerald @FreeBSD.org
___
freebsd-ports
nse with an exact value of OPSYS ("FreeBSD").
Would it make sense to add a check to portlint that every condition
(or practically probably line, considering "...\\\n..." as one line)
that has OSVERSION also has OPSYS?
Gerald
lly delay updates
of the wine-devel port until that extra patchset is ready, for the
wine-staging port and if someone sets the STAGING option in the main
port.)
> Gerald, please see above. In r430845, the info for the wine-staging
> tarball disappeared from wine-devel/distinfo.
Thanks fo
rs of shaky, untested and
non-standard elements on top of each other.
As far as lang/gcc* ports are concerned, I believe the best use
of our time will be moving lang/gcc from GCC 4.9 (where it finally
got to) to GCC 5.
Gerald
___
freebsd-ports@freebs
d failed to find anything (which also would be surprising given
no other reports in the last decade).
vbox@, any ideas?
Gerald
> The specific example turns out to be. . .
>
> emulators/virtualbox-ose-additions leads to:
>
> ===>>> The following actions will be
ementation in the Ports Collection. :-)
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
re scripts is turning off the "C99_MATH_TR1" support.
...I believe since FreeBSD 10 has better libc support for the long
math functions, so our best course of action (apart from counting
down those months that FreeBSD 9 still has) is seeing that we can
finally update lang/gc
am and in our lang/gcc* ports).
If there is anything you see missing, please advise.
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ase -- or a local patch
like this).
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ur canonical GCC port, now features
gfortran as well as gcc and g++ without the appended major version
number.
(Not committed yet; feedback very welcome.)
Gerald
Index: Makefile
===
--- Makefile(revision 402204)
+++ Makefile
ing is expected and can be
ignored.
This being an old port, nothing has changed on the GCC side. Which
means something in -CURRENT must have broken it.
Gerald
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/f
On Tue, 7 Apr 2015, Ben Woods wrote:
> It looks like this is a bug which has been reported upstream in the wine
> forums:
> https://forum.winehq.org/viewtopic.php?t=24430&p=99442
Interestingly it only happens on FreeBSD head, though; all other
version appear
x) case (x): stropt = #x; break
>^
> socket.c:370:27: error: use of undeclared identifier 'WS_IPX_DSTYPE'
> DEBUG_SOCKOPT(WS_IPX_DSTYPE);
> ^
...does anyone know what is going on in HEAD and what to do about
it?
Or is this a temporary thi
aders
test -z 'strip' || strip
.../gcc-ref8-amd64/libexec/gcc/x86_64-unknown-freebsd8.4/5.0.0/install-tools/fixincl
gmake[2]: Leaving directory '.../OBJ-0118-1528/fixincludes'
(I also tried setting STRIP_CMD to true, alas that is not used by GCC.)
Gerald
.../prefix/gcc5/libexec/gcc5/gcc/i386-portbld-freebsd10.1/5.0.0/install-tools/fixincl';
reason: Permission denied
Makefile:191: recipe for target 'install-strip' failed
gmake[3]: *** [install-strip] Error 1
How do we best go about this?
Gerald
___
h not
doing that and thus building a lot faster has been one of the
features of lang/gcc. -- Since it does not reproduce for me,
do others see the same failure?
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
x27;ve been running weekly testers for
about a year (until I switch that to GCC 4.9 a few months ago),
which has never exhibited that.
Is there anything special on your end (in base, hardware, options...)?
Gerald
___
freebsd-ports@freebsd.org mailin
we'd just break out a small gcc-runtime package.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Tue, 1 Jul 2014, Gerald Pfeifer wrote:
>>> It's LOCALBASE that points to /home/gerald/10-i386, so I am really
>>> puzzled about those @unexec rmdir's that want to remove my LOCALBASE.
>> You can try attached patch.
> Cool. That fixes the issue in my t
On Mon, 30 Jun 2014, Antoine Brodin wrote:
>> In my case PREFIX points to /scratch. It's LOCALBASE that points to
>> /home/gerald/10-i386, so I am really puzzled about those @unexec rmdir's
>> that want to remove my LOCALBASE.
>>
>> Why should any port or p
On Fri, 20 Jun 2014, Antoine Brodin wrote:
>> Build with a non-standard PREFIX and LOCALBASE in /home/gerald/10-i386,
>> make ports builds have been failing with the following for a bit (for
>> lang/gcc49 among others):
>>
>> Running regression-test, checking f
[ No ideas? Shall I just file a bug report? ]
Build with a non-standard PREFIX and LOCALBASE in /home/gerald/10-i386,
make ports builds have been failing with the following for a bit (for
lang/gcc49 among others):
Running regression-test, checking for orphans, checking pkg-plist
Build with a non-standard PREFIX and LOCALBASE in /home/gerald/10-i386,
make ports builds have been failing with the following for a bit (for
lang/gcc49 among others):
Running regression-test, checking for orphans, checking pkg-plist.
> Checking for pkg-plist issues (check-pl
On Wed, 11 Jun 2014, Antoine Brodin wrote:
>>> ===> Installing ldconfig configuration file
>>> cannot create
>>> $WRKDIRPREFIX/stage/home/gerald/10-i386/libdata/ldconfig/gcc49: No such
>>> file or directory
>>> *** Error code 2
>
This is a new failure that I found when testing a (trivial) update
to lang/gcc410 with some of my usual scripts:
> Compressing man pages (compress-man)
===> Installing ldconfig configuration file
cannot create $WRKDIRPREFIX/stage/home/gerald/10-i386/libdata/ldconfig/gcc49:
N
e from the dead.
As far as libiberty.a goes, I think at least the lang/gcc* ports should
be good.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-por
N_DEPENDS= libtorrent=0.13.2_1:${PORTSDIR}/net-p2p/libtorrent
I have never seen such a crazy dependency before. Try making this
_2 instead of _1, but, really, this is crazy.
Andrej, any idea?
Why is this not checking for libtorrent.so? And a LIB_DEPENDS instead?
Something like
LIB_DEPENDS=
rsions.
(In my day job, we have been doing this for years. Once we have
several binary packages from one port, that ought to be relatively
straightforward.)
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing
USE_GCC? If so, here is the bug.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing
USE_GCC? If so, here is the bug.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
the CONFLICTS, please advise so that we can
tighten them.
Gerald
--
Gerald Pfeifer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-uns
> could use NetBSD's snprintb() (see
> <http://netbsd.gw.com/cgi-bin/man-cgi?snprintb+3+NetBSD-current>).
>
> Getting rid of non-standard extensions in general is really the way to
> go. This would enable compiling with any standards-compliant compiler,
> even
On Sun, 24 Nov 2013, Dewayne Geraghty wrote:
> Thanks to Gerald for addressing this issue per
> http://svnweb.freebsd.org/ports/head/Mk/bsd.gcc.mk?sortby=date&view=log
> clamav now builds.
Thanks for the confirmation. And sorry for the temporary brea
es. I just tested this, and in my environment it seems to work
(passing the tests described in the Handbook).
ports/184178 when you commit this. :)
Thanks,
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
On Sat, 23 Nov 2013, Baptiste Daroussin wrote:
> On Sat, Nov 23, 2013 at 01:26:58AM +0100, Gerald Pfeifer wrote:
>> Okay, now I am confused. How can my workaround work for three quadrants
>> of {8.4,9.2} x {amd64,i386} and fail for just one combination?
> Probably one of the p
Okay, now I am confused. How can my workaround work for three quadrants
of {8.4,9.2} x {amd64,i386} and fail for just one combination?
Gerald
On Sat, 23 Nov 2013, Ports-QAT wrote:
> Work around ports infrastructure breakage introduced with staging and
> remove info/gcc46 our
llowing
upon `make deinstall` in my testing:
/scratch2/tmp/gerald/prefix/gcc47/info/gcc47/dir: could not read (No such
file or directory) and could not create (No such file or directory)
/scratch2/tmp/gerald/prefix/gcc47/info/gcc47/dir: could not read (No such
file or directory) and could no
see, however, the following, which I don't think I've seen
without your patch upon `make deinstall`:
/scratch2/tmp/gerald/prefix/gcc47/info/gcc47/dir: could not read (No such file
or directory) and could not create (No such file or directory)
/scratch2/tmp/gerald/prefix/gcc47/info/gcc47/dir: c
On Sun, 10 Nov 2013, Antoine Brodin wrote:
> You can try patch at:
> http://people.freebsd.org/~antoine/ports/stage-info_subdir.diff
> (totally untested)
Thanks for looking into this, Antoine. I tested this using
lang/gcc47 and unfortunately info/gcc47 still remains in my
testing
On Sat, 9 Nov 2013, Dmitry Marakasov wrote:
> * Ports-QAT (q...@redports.org) wrote:
>
> +gerald@
Staging support broke INFO= here. The INFO= infrastructure should
take care of not leaving anything upon deinstallation and it did
so for years. I looked into fixing this in Mk/bsd.*.mk b
t should also affect
a number of other ports, not the lang/gcc49 port.
I tried the patch below, alas that didn't do the trick. Perhaps it
inspires someone, though?
Gerald
Index: bsd.stage.mk
===
--- bsd.stage.mk(r
make gcc49 port?
I did so yesterday. :-) It should be in your ports tree with the
next update.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ght thing; or you could just remove everything
except for
_GCC_PORT:= gcc${V}
Either should work.
(I'd love to update GCC_DEFAULT_VERSION to 4.7 one of these days; is
the cluster sufficiently recovered for a test run?)
Gerald
On Wed, 6 Mar 2013, Anton Shterenlikht wrote:
> Hi Gerald
>
> amd64 r246552 with clang
clang may be related.
Can you look into what happens here? My tests (with a full build)
definitely have succeeded, and they have actually used clang as cc
on FreeBSD 10.
Is this specific to amd6
ht?
That's what I have been hoping to do, yes. With the ports
build cluster being unavailable for months now, we simply
could not do the necessary testing though.
Anyone who wants to give this a try, I'd be happy to see that.
Gerald
__
what we have been doing
in terms of extensive building and testing, and (d) different from
many others have been doing.
That said, if someone wants to give it a try and test, I'd definitely
be open to make this an OPTION.
Makes sense?
Gerald
PS: ports.svn/java/eclipse-ecj> make build-depe
am planning to adjust the lang/gcc{,46,47,48} ports.
Let me know if you have any comments/suggestions on these changes
which I plan to commit in one, two days. (The below passed the
official set of ports and package testing.)
Gerald
Index: gcc-ecj45/Makefile
as we are doing for lang/gccXY.
What do you think?
>>> I had patches to do this even without pkgng, but it made things a
>>> little more complicated, and didn't seem to be a high priority, so I
>>> didn't pursue it. If people feel that it is important, I c
64-bit OS, how to best reflect that?
wine-devel-fbsd64 as per the current name? wine-devel-32on64?...??
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
e definitely can look into this. But, how about the run-time
dependency? Those ports that you have in mind, don't they have
any dependency on one of the GCC run-time libraries?
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
suming that this
part of the process, forcing deinstallation of the old version and
installing a new package, does not depend on "any" other ports?)
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-p
On Tue, 28 Aug 2012, Bryan Drewery wrote:
> I believe this was reported in ports/171135 as well for lang/gcc47.
> Received in private email:
This may or may not be the same issue. In a case like this it
is always possible that one is missing the obvious, but right
now I am simply not seeing it.
from GCC 4.x to GCC 4.x+y
run-times quite successfully and without any breakage more than once.
And we've got many, quite many, users.
In other words, if there is a challenge it's not GCC per se, more
our packaging of it (and some work Bapt is doing on the packa
.
> Reducing functionality to handle build infrastructure problems is
> not a desirable solution. But thanks for the response in any case. :)
Reducing functionality if that cuts the cost of building in half
and you do not actually use that functionality (only a single port
does, from
On Tue, 13 Dec 2011, b. f. wrote:
>> Ahh. I see the issue. I have not looked at bsd.gcc.mk, but it does not
>> seem like this should be too difficult. Just a matter of the right
>> person having the time. Would ports specifying gcc46 need to be
>> touched?
> Gerald had p
l,
and perhaps do similarly for lang/gcc47 as well. Thoughts?
Gerald
PS. The _GCC_BUILD_DEPENDS assignment below prevents breakage of
some ports. I plan on addressing this in a nicer manner, but prefer
to separate the two changes and proceed with this first ch
be one option.
Another might be reducing the amount of parallel building on your
system.
Finally, you indicated that you also saw Java create a large
temporary file. If you want to avoid building Java, the GCC
ports have an option to disable Java. Let
icated he had an idea, let's see. Whatever works. ;-)
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
text of FreeBSD and also upstream.
Are you saying you actually noticed some leftovers in /tmp, or that
there "just" has been more at certain points in time than you would
expect?
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists
stion I have is whether, given there is also clang,
this is really best suited for Mk/bsd.gcc.mk, or this should rather
become part of the general Mk/bsd.port.mk?
To me it looks more like the latter, Mk/bsd.port.mk, but if not for
some reason, please add a comment to the to
= ${CXXFLAGS.${CC}}
Similarly here. Where does this come from, why is it related to
the WITH_GCC versus USE_GCC patch? Can and should this be split
out? How is it used and where? Where is it defined?
Gerald
PS: I won't be able to do FreeBSD work the coming two weeks (at all,
pro
this is an omission, can someone more closely involved than
I have been so far donate a paragraph or two?)
Gerald
PS: I am thinking to split the existing emulators/wine port into
two, the regular one (tracking releases of Wine) and a -devel port
that tracks the bi-weekly snapshots that will lead to
suming that directly.
Based on your feedback I just noted the upstream revision ids and omitted
the ChangeLog patches.
Thanks,
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
t; The only small trouble with it was that the resulting
> files/patch-freebsd10 had the dos line endings.
Hmm, I think that must have happened when I mailed it (though no
Windows machine was involved)? The patch as I applied it should
not have
, and the port is updated accordingly,
> it will include the fixes. In the meantime, I think Gerald was
> waiting for Martin to incorporate the patch to adjust the
> run-autotools-fixup target in ports/Mk/bsd.port.mk
As usual, Brendan is right on target. :-) If you guys would like
to t
On Thu, 15 Dec 2011, Gerald Pfeifer wrote:
>> lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22
>> installed during its configure step with the errors like the following in
>> config.log:
>
> Yes, I am aware of it. lang/gcc is the slowly moving, con
y the use case for lang/gcc at this point is not users of
FreeBSD 10. That's going to change with the changes to Mk/bsd.gcc.mk
that we discussed on this list the last couple of days, and that will
not happen before it builds on FreeBSD 10.)
Gerald
_
kefile USE_FORTRAN=g77
science/elmerpost/MakefileUSE_FORTRAN=g77
Without these, lang/gcc44 and lang/gcc34, respectively, could be
obsoleted and removed.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
ery confident it does, but as b.f. stated
earlier in the thread, if you want to be 100% sure rebuilding all
dependent ports is always the safer approach.)
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-p
lang/gcc package is present wherever you install
things built that way, you should be good.
Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
USE_GCC=4.6+ or USE_FORTRAN=yes both will
automagically just pull in lang/gcc instead of lang/gcc46 by default.
That's the plan. It's taken a bit longer than I had hoped (for a
number of reasons), but we are nearly there. ;-)
Gerald
___
fre
ve something like a gcc-runtime package that falls
out of the lang/gcc port and covers all those needs. (That's not the
minimum, assuming we still have something -- bet it GCC 4.2 or LLVM
based in the base system -- but quite small.)
Gerald
___
freeb
ed at that, and Emanuel convinced me that apparently there
is no way to avoid one of these two deaths.
That looks like a nice project for someone to improve our general
infrastructure along these lines.
Gerald
___
freebsd-ports@freebsd.org ma
h FreeBSD 7.0 (and that magic 42 marker) until the rest of times.
Can you advise which value of __FreeBSD_version to use? The official
list at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html
does not have a reference from what
${PREFIX}/bin/ccache-update-links -v; \
> fi
>
It does not cover de-installation which raises two questions:
1. Why don't we have a post-deinstall target?
2. How is the task best accomplished?
Gerald
___
fr
Synopsis: [bsd.port.mk] Pass CPPFLAGS to MAKE_ENV and CONFIGURE_ENV
Responsible-Changed-From-To: gerald->ports
Responsible-Changed-By: gerald
Responsible-Changed-When: Fri Jan 28 20:31:30 UTC 2011
Responsible-Changed-Why:
I'm giving up.
This most obviously correct and trivial change has
art of the core operating system, but one of the
many the programs offered via the FreeBSD Ports Collection.
If you want to use GCC on FreeBSD, I recommend to go for lang/gcc45
(short: gcc45). I do not know what caused the installation of gcc44
on your system, but gcc45 should be strictly preferra
"uglier" pieces remain in the slave port itself.
Gerald
k
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
1 - 100 of 161 matches
Mail list logo
