On Tue, Jul 18, 2017 at 08:33:57AM +0200, Klaus T. Aehlig wrote:
> Actually, it is not that far in the future; in fact, event today, bazel's
> cc_library rule accepts an .so in the sources attribute, making a work around
> possible (patching WORKSPACE to point to a hand-crafted d
On Mon, Jul 17, 2017 at 09:37:34AM +0200, Klaus T. Aehlig wrote:
> However, even with that approach, you should be aware that you're
> embedding the relevant dependencies rather than using them from
> ${LOCALBASE}. So, in the long run, it might be desirable to patch the
> releva
> Bazel (devel/bazel) based projects tend to fetch tarballs directly.
> WORKSPACE can be patched to change the fetch URL to one in
> /usr/ports/distfiles. However, what to do when the contents of tarballs
> need to be patched?
Unfortunately, there is no real good bazel way to do this. It was
di
On Sun, Nov 23, 2014 at 12:12:06AM -0800, Perry Hutchison wrote:
> "Christopher J. Ruwe" wrote:
>
> > ... Emacs, the very good operating system
> > missing only a decent editor ...
>
> Perhaps someone should port vi to it?
That actually already happened quite a while ago. Just add
(require 'vi
On Sun, May 18, 2014 at 11:02:04AM +0200, Marco Beishuizen wrote:
> On Sun, 18 May 2014, the wise Jos Chrispijn wrote:
>
> > Just to inform you that there is something going wrong updating this
> > port update:
> > --- cut ---
> > ../../../../src/gallium/auxiliary/util/u_sse.h:206: error:
Hi,
> Alternatively, you can turn off only a specific -Werror, e.g.
>
> CFLAGS += -Wno-error=unused
>
> it's ignored by gcc in base while gcc46 wants -Wno-error=unused-value
that's a very good point. Thanks a lot!
Best,
Klaus
___
freebsd-ports@fr
Hi,
> Are you sure that you don't have -Werror being set somehow?
well, fortunately I have! Note that it is a feature in this
context that a similar programs don't compile if the types
are incompatible.
Compare the following. -Wno-unused -Werror is indeed the
correct choice of flags.
Best,
Kl
Hallo,
while trying to find out why I couldn't build net/socat with clang
I found something that might be a general issue, and I wonder what
appropriate actions would be.
Trying 'cd /usr/ports/net/socat && make CC=clang' failed for me and
it turned out that the reason was that the configure scri
> Simplicity. [...] I've got ca. 70 Gentoo servers and I want my own
> portage overlay.
Thank you very much for that explanation! I was thinking in a different
direction, as the number of machines I have is quite limited, each
with very specific needs.
As long as it is only about adding new
Hi,
> 3. Someone deleted port I like to use / I want my personal ports tree:
> FreeBSD: I wish :/
> Gentoo: overlays works well.
Now I'm really curios what magic device gentoo has. Once thing I
most appreciate about FreeBSD is how flexible it is in precisely
this manner.
* if some port is remov
Dear Stanislav,
> Hmm, it should not depend on ncurses, and certainly it should not link against
> a static library. Can you please send me a build log of lang/ruby18?
I must admit that I'm not able to reproduce the error any more, so it
seems to be something more subtle than the mere presence
Hallo,
on my system, I have devel/ncurses installed. While upgrading
(to a ports tree as of yesterday evening) I found that I couldn't
build lang/ruby18. The error message complained that libncurses.a
was not compiled with -fPIC.
Of course, adding the lines
.if !empty(.CURDIR:M*/ports/devel/ncu
> The PR you referenced
> removed the rdiff binary too, but it was restored in a later commit.
yes, you're absolutely right! I missed that point. Thanks for the
explanation -- and thanks for readding the man page.
Best,
Klaus
___
freebsd-ports@freebsd.
> The change occurred sometime in the last few months. This might be
> related:
>
> https://github.com/blog/900-nodeload2-downloads-reloaded
Ah, I see. Thanks for the link.
Klaus
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailm
Hallo,
I recently had a quick look at net/librsync and was puzzled that
it installs rdiff, but not the man page for rdiff. Looking at the
history, this has happened with the update to 0.9.6, submitted in
PR ports/55469 [1]. However, I fail to see the reason for removing
the man page. Leaving it i
> Until recently, github required two requests to get a tarball: one to
> initiate the tarball creation, the other to download it.
Yes, that's what I remember. The URL you got after the first redirect
was then good for a couple of days -- till eventually it wasn't used
for long enough time and th
> > * due to autogeneration, you're quite likely to get a http-redirect,
> Does fetch support redirects?
Yes. But for good reasons, Mk/bsd.ports.mk contains the line
FETCH_ARGS?=-AFpr
Note the -A. Of course, it's no problem to make an exception for github, but
at least, one should be aware
> I've thought about checksums, but my simple experiment shows, that
> tag-related (not tip-related, of course) archives give same chsum
> after re-downloading in short time. But I don't check it for long-term
> stability.
Well, let's do at least one check with a one and a half year old tar ball.
> The main problem with that is: we have no way to keep a valid sum of the
> distfiles if it is autogenerated (in particular with github) and this sum is
> really important.
With github this fortunately is a non-issue. Even though they autogenerate their
tar balls, they keep enough information
> - no 'make clean' and reusing the object files of the current version for
> building the new, updated,
> version. That should save significant compilation time. Does that work as
> of today?
I doubt that that will work in that form. In fact, I quite like that
'make clean' in ports throws aw
Dear Stephen,
> Or one could instead modify devel/libtools, maybe something like this.
> Rename bin/libtool to libexec/libtool.sh, and then rewrite the libtool
> script as something like:
>
> #!/bin/sh
> PREFIX=/usr/local
> TEMPCCDIR=`mktemp -d -t /tmp`
> export PATH=${WRKDIR}:$PATH
> ${LN} -s
Hi,
I'm disappointed that there are plans to remove the ports framework. I
always considered this to be one of the very strong points of the ports
infra structure, precisely because I believe...
> Not only that but because maintainers would be
> able to choose the best possible configuration fo
Hi,
almost a month ago I submitted ports/154859, a maintainer update of www/uzbl
to the then up-to-date release. Nothing has happend so far, and in the mean
time a new version has been released and I'm currently testing the updated
port; I expect so send a PR in the next days. Now I wonder, wheth
Hi,
> I think some option like "CLANG_SAFE" or "USE_CLANG" (just
> saying, perhaps a better name can be found) should be added [...]
I also think that it would be very useful to go the same route
as with MAKE_JOBS, i.e., ports can opt in, and in the long run opt out,
of being build with clang.
> More fallout from the devel/libtool problem [...] but then libtool
> attempts to link the shared libraries with the base system compiler
> and toolchain.
Thanks for the explanation! Things start to make sense now...
Best,
Klaus
___
freebsd-ports@fr
Dear Mark,
> > Can anyone shed more light on why this port is marked BROKEN?
>
> In general you have to do a little bit of detective work. [...]
Thank you very much for your very detailed and helpful explanation!
That helped a lot. I hope, in the future I'll look at the right place
directly m
Hallo,
I'm looking for someone, who can give me some background information
on why science/libctl is marked as broken. According to cvs, this
was committed by erwin@ on 2011/02/25 09:30:06 saying "Mark BROKEN:
does not build". However, I found that by saying NO_IGNORE=YES it
builds and installs
> The reason is because PORTSDIR has not been defined at this point.
> The PORTSDIR variable is defined in /usr/ports/Mk/bsd.port.mk. Also
> bsd.port.mk doesn't get included until after the master port's
> Makefile gets included.
Oh yes, you're absolutely right. I completely forgot that bsd.port
> MASTERDIR= ${.CURDIR}/../py-httplib2
shouldn't that be
MASTERDIR=${PORTSDIR}/www/py-httplib2
Or have I misunderstood something here?
Best regards,
Klaus
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-po
Hi everybody,
sorry for the noise.
> > MASTERDIR= ${.CURDIR}/../py-httplib2
>
> shouldn't that be
>
> MASTERDIR=${PORTSDIR}/www/py-httplib2
>
> Or have I misunderstood something here?
I obviously did. At least the example in porters' handbook and
all slave ports use ${.CURDIR}/../ Could some
Hi,
Recently, I submitted PR ports/141674 suggesting a port for the uzbl
web browser. Given the current holiday season, I'm not surprised that
it is still unassigned. On the other hand, upstream has developped
further, and I wonder if I'm right in submitting updated versions of
this port as follo
31 matches
Mail list logo
