Similar question. I tried to install the texlive-xetex. The installation is
successful, but there is no .fmt files installed.
On Sun, Oct 9, 2011 at 9:58 PM, Stephen Montgomery-Smith <
step...@missouri.edu> wrote:
> Hey guys, I did
>
>
> make -C /usr/ports/ports-mgmt/**portshaker-config install
>
On Sun, Oct 09, 2011 at 09:58:50PM -0500, Stephen Montgomery-Smith wrote:
> Now I have a whole bunch of texlive ports installed under
> /usr/ports/print. Am I just supposed to build the ports I need, or is
> there some grand texlive-build-all port that is in this long list somewhere?
I updated
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
No matches t
Doug Barton wrote:
>>> Also, once it got built, it failed to package:
>>>
>>> ===> Building package for chicken-4.7.0
>>> tar: lib/chicken/6/modules.db: Cannot stat: No such file or directory
>>> tar: Error exit delayed from previous errors.
>>> pkg_create: make_dist: tar command failed with code
> I updated this page:
> http://code.google.com/p/freebsd-texlive/wiki/Installing
Are there any plans on getting these committed to the mainline ports
tree? I'd be willing to work with you on that.
>
> You should at least install texlive-scheme-minimal but if you don't know
> exactly what you nee
On 10/10/2011 03:29 AM, Romain Tartière wrote:
On Sun, Oct 09, 2011 at 09:58:50PM -0500, Stephen Montgomery-Smith wrote:
Now I have a whole bunch of texlive ports installed under
/usr/ports/print. Am I just supposed to build the ports I need, or is
there some grand texlive-build-all port that i
On 10/10/2011 06:44 AM, Eitan Adler wrote:
Are there any plans on getting these committed to the mainline ports
tree? I'd be willing to work with you on that.
I agree with Eitan. I don't see a reason why texlive shouldn't make it
into the mainstream ports. What you need is to work with some
On 10/10/2011 07:23 AM, Stephen Montgomery-Smith wrote:
On 10/10/2011 06:44 AM, Eitan Adler wrote:
Are there any plans on getting these committed to the mainline ports
tree? I'd be willing to work with you on that.
I agree with Eitan. I don't see a reason why texlive shouldn't make it
into th
ajtiM wrote on 09.10.2011 15:19:
Hi!
I have Firefox 7.0.1 installed but no one of plugins work which I didn't have
a proble before. I made in /usr/local/lib/firefox dorectory plugins and made a
symlink from /usr/local/lib/web_browser/plugins but doesn't works.
One of the plugins is gnash plu
On 10/10/11 07:23, Stephen Montgomery-Smith wrote:
On 10/10/2011 06:44 AM, Eitan Adler wrote:
Are there any plans on getting these committed to the mainline ports
tree? I'd be willing to work with you on that.
I agree with Eitan. I don't see a reason why texlive shouldn't make it
into the ma
Hello!
I am running 64bit PC-BSD v9.0beta3 (updated from beta2), originally
installed from USBFULL 9.0beta2.
I have tried to do a pbi_makeport of Quassel to obtain the monolithic build
of Quassel. I did my best to instigate this desired outcome by using the
pbi.conf file with the appropriate opt
It's been quite a few weeks that this empty/pointless message has been
sent to the list, what needs to happen to make it stop?
On 10/10/2011 04:08, FreeBSD bugmaster wrote:
> Note: to view an individual PR, use:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
>
> The following is a lis
On Sat, 8 Oct 2011 09:51:00 + (GMT)
"Thomas Mueller" mentioned:
>
> > You cannot use this port to build toolchaing for compiling Linux and
> > NetBSD applications. This port creates toolchain using the newlib
> > libc library, which is used by some embedded operating systems (e.g.
> > rtems
Until the pointy-haireds come up with a better solution, here is a patch
that incorporates work that others have done into a manageable form so
that those interested in working with ports on 10-current have some
tools to work with:
http://dougbarton.us/bam.patch
You need to do the equivalent of '
On Mon, Oct 10, 2011 at 3:22 PM, Doug Barton wrote:
> It's been quite a few weeks that this empty/pointless message has been
> sent to the list, what needs to happen to make it stop?
Assign bugs to ports@ - then it won't be empty anymore.
--
Eitan Adler
_
On 10/10/2011 14:48, Eitan Adler wrote:
> On Mon, Oct 10, 2011 at 3:22 PM, Doug Barton wrote:
>> It's been quite a few weeks that this empty/pointless message has been
>> sent to the list, what needs to happen to make it stop?
>
> Assign bugs to ports@ - then it won't be empty anymore.
There is
On 10/10/2011 15:00, Nali Toja wrote:
> Doug Barton writes:
>
>> Until the pointy-haireds come up with a better solution, here is a patch
>> that incorporates work that others have done into a manageable form so
>> that those interested in working with ports on 10-current have some
>> tools to wo
On 10/09/2011 09:29, Hajimu UMEMOTO wrote:
> Hi,
>
>> On Fri, 07 Oct 2011 16:48:52 -0700
>> Doug Barton said:
>
> dougb> In case anyone wants to take this on, this port fails to install on
> 10.0
> dougb> because it uses its own version of libtool. I took a quick look but
> dougb> there
On Mon, Oct 10, 2011 at 1:59 PM, Doug Barton wrote:
> Until the pointy-haireds come up with a better solution, here is a patch
> that incorporates work that others have done into a manageable form so
> that those interested in working with ports on 10-current have some
> tools to work with:
>
> ht
Doug Barton writes:
> Until the pointy-haireds come up with a better solution, here is a patch
> that incorporates work that others have done into a manageable form so
> that those interested in working with ports on 10-current have some
> tools to work with:
>
> http://dougbarton.us/bam.patch
[.
I've recently started using net/nss-pam-ldapd (0.7.13_2). The systems
on which it is deployed are all i386, either 8.2-RELEASE or recent
8-STABLE.
It works well for me except that it breaks top(1) - obviously at the
point where top translates uid's to names. Forcing top(1) to skip the
uid/userna
Since the release has been pushed back some more since the last mail, we
do have some time to test a possible fix for the issues we're seeing
with libtool on FreeBSD 10.0. However, fixing libtool is only part of
the problem as hundreds, if not thousands, of ports roll their own
detection and need
23 matches
Mail list logo
