I used to build groff with a toolchain from Macports.
Therefore I had perl at:
#!/opt/local/bin/perl -w
After cleaning my system I now use the system version of Perl at:
#!/usr/bin/perl -w
This has resulted in the correct version in the Makefile:
PERL = /usr/bin/perl
PERL_VERSION = 5.30.2
Si
> Am 08.05.2022 um 20:25 schrieb G. Branden Robinson
> :
>
> For those not following the groff-commit list (which I encourage readers
> of this list to do), the foregoing is done. Nearly all of the 27
> commits I pushed on 3 May[1] improve the build dependency situation.
> There are fewer spu
> Am 28.10.2021 um 20:46 schrieb John Gardner :
>
> Hi Axel,
>
> Before running ./bootstrap from the root directory, make sure all build
> artefacts are wiped:
>
> git pull && git checkout -- . && git clean -xfd
>
> I recall seeing this exact error a while ago when attempting to recompile
Today I did a
make clean
./configure --with-uchardet=no
make
and got
make[1]: *** No rule to make target `tmac/mdoc/doc-common', needed by `all-am'.
Stop.
Yes, I did an
autoconf
and
autoupdate
since autoconf (GNU Autoconf) 2.71f
suggested that.
Today I’m on MacOS 10.13 with a current
Hello,
I get the following error when building on MacOS 11:
sed: 17: ./contrib/sboxes/notquine.sed: unexpected EOF (pending }’s)
If I remove
/\\##/{
s/\\##//
b}
It works:
/Applications/Xcode.app/Contents/Developer/usr/bin/make all-am
GEN contrib/sboxes/msboxes.ms
GROFFcontr
> Am 07.02.2021 um 22:49 schrieb G. Branden Robinson
> :
>
> At 2021-02-05T14:26:33-0500, T. Kurt Bond wrote:
>> and ran it with the slightly munged (but with nothing in mom changed)
>> and several months out of date version of groff from git. (it's out
>> of date since it's been several mont
> Am 29.03.2018 um 00:46 schrieb Bertrand Garrigues
> :
>
> Hi all,
>
> Release candidate 1.22.4.rc2 is now available from GNU's alpha ftp.
> Compared to the previous releases (1.22.3.rc1) it includes the latest
> 2.3 version of 'mom' macro package, new features in 'gropdf' to generate
> presen
Am 12.10.2014 um 20:50 schrieb Werner LEMBERG :
>
>> I pulled from git and did a make distclean.
>
> This isn't enough. You have to re-execute `config.status'.
make distclean says:
rm -f Makefile config.cache config.log config.status groff.log groff.sum
src/include/config.h site.bak site.ex
Am 12.10.2014 um 18:14 schrieb Werner LEMBERG :
I pulled from git and did a make distclean.
>> During make:
>>
>> sed -e "s;@VERSION@;1.22.3;" webpage.ms [...]
>> sed: RE error: illegal byte sequence
>
> Should be fixed now.
Sorry, it isn't:
sed -e "s;@VERSION@;1.22.3;" webpage.ms | GROFF_CO
Am 12.10.2014 um 13:10 schrieb Werner LEMBERG :
>
>> I had a problem with make install (again illegal byte sequence).
>> As a result I had an incomplete installation.
>> This was fixed with LANG=C.
>
> Uh, oh, this is not enough information. Please show us the *exact*
> error message.
During
Am 12.10.2014 um 11:11 schrieb Werner LEMBERG :
> Well, this looks like a bug in the texi2pdf script. What texinfo
> version are you using?
Texinfo 4.8 (1.34)
Since texi2pdf is just a wrapper around texi2dvi the problem lies there.
(There is neither $LANG nor $LC_ALL in both scripts.)
>> W
Am 11.10.2014 um 09:13 schrieb Werner LEMBERG :
>
> After Bernd's commits to fix the IPC issue, I can do `make dist' and
> distribute it. Before doing this, however, I want to wait a few days
> so that you can test and check whether everything's fine. Please do so!
>
>
>Werner
I tried to
Am 15.09.2012 um 22:21 schrieb Peter Schaffter:
> Thanks for catching this. Here's a patch for
>
> groff-current/contrib/mom/Makefile.sub
>
>
>
> --- Makefile.sub.orig 2012-09-15 15:59:48.964497338 -0400
> +++ Makefile.sub
Hi!
I wanted to look at the new mom macros and installed groff from cvs.
I was a little surprised that the pdf files in contrib/mom/examples were all 0
bytes long.
And here is the reason:
GROFF_COMMAND_PREFIX=''; export GROFF_COMMAND_PREFIX;
PDFMOM_BIN_PATH=/Users/axel/src/groff/src/devices/gr
Am 26.04.2012 um 18:48 schrieb Werner LEMBERG:
>> In fact, the whole directory
>> groff/src/libs/gnulib/build-aux/snippet
>> is missing.
>>
>> `src/libs/gnulib/build-aux/arg-nonnull.h' is no longer in the repository
>> `src/libs/gnulib/build-aux/c++defs.h' is no longer in the repository
>> `src
Hi!
I updated groff, made clean, and configured.
After typing make I got:
make[4]: *** No rule to make target `../build-aux/snippet/arg-nonnull.h',
needed by `arg-nonnull.h'. Stop.
make[2]: *** No rule to make target `../build-aux/snippet/c++defs.h', needed by
`c++defs.h'. Stop.
make[2]: **
Am 24.08.2010 um 15:20 schrieb Axel Kielhorn:
> When I try to install groff I get the following error:
>
> make[2]: *** No rule to make target `momdoc/typemacdoc.html', needed by
> `install_data'. Stop.
>
> since momdoc/typemacdoc.html is referenced by momdoc/toc
When I try to install groff I get the following error:
make[2]: *** No rule to make target `momdoc/typemacdoc.html', needed by
`install_data'. Stop.
since momdoc/typemacdoc.html is referenced by momdoc/toc.html
the file seems to required but missing.
This is probably the result of:
* Wed Aug
Am 08.06.2010 um 11:22 schrieb Anik Wadehra:
> Hi All,
>
> I have cross-compiled groff with ppc architecture successfully.
>
> When I move the application to my ppc machine and try to convert text to
> ps (groff -Tps text.txt > postscript.ps).
>
> In case of Japanese postscript contains garbag
Am 17.01.2010 um 04:21 schrieb Larry Kollar:
>
> brian m. carlson wrote:
>
>>> I'm not a c++ expert in the least, but I couldn't get the CVS (from an
>>> hour ago) to compile without getting rid of the "inline" keyword from
>>> node::~node() as follows. Is this a problem on my end?
>>
>> This
Am 18.07.2009 um 09:28 schrieb Werner LEMBERG:
Theoretically the (untested) patch below should make it compile.
Please test.
Now I get new warnings:
g++ -I. -I. -I/Users/axel/src/groff/groff/src/include -I/Users/axel/
src/groff/groff/src/include -DHAVE_CONFIG_H -g -O2 -c div.cpp
node.h:6
Am 17.07.2009 um 22:43 schrieb Werner LEMBERG:
Today I tried to build the current cvs-version of groff on MacOS
10.5.7 with xcode 3.1.1.
Which compiler is this?
gcc version 4.0.1 (Apple Inc. build 5488)
i686-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5564)
has the same problem
Hello!
Today I tried to build the current cvs-version of groff on MacOS
10.5.7 with xcode 3.1.1.
I get the following link error:
Undefined symbols:
"node::~node()", referenced from:
vertical_size_node::~vertical_size_node()in div.o
vertical_size_node::~vertical_size_node()in di
de.tmac defines the german date for MS as:
ds DY \n[dy] \*[MO] \n[year]
which leads to
4 Januar 2009.
IMO this should be
ds DY \n[dy]. \*[MO] \n[year]
which will result in
4. Januar 2009
The code for MM already has the ".".
Axel
I've just updated to the current (10:00 CET today) version of groff
and had a problem building groff.pdf with the texinfo.tex file
supplied by groff and an almost current (2008-12-26) Texlive 2008.
The texinfo in groff/doc is 2004-11-25.16, the version in Texlive 2008
is 2008-11-09.14
Wit
I have finally reached the limit of 4 pages:-)
Please have a look at it to iron out the last wrinkles.
After that I would like to put it into the groff-wiki.
I can provide a rough english translation as well, but that will need
the review of a native speaker. Maybe we should change the name to
Am 24.09.2007 um 12:47 schrieb Walter Harms:
groff.man (7) linkt to http://cm.bell-labs.com/cm/cs/54.ps but the
actual file is at
http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz
Is is possible to have a copy of this document on gnu.org ?
sometimes documents vanish suddenly (i learned that leasso
Am 21.09.2007 um 20:32 schrieb Axel Kielhorn:
Hi!
I'm currently adding a section about further literature to my short
guide.
While reading the man-pages I stumbled over a few things:
groff_char.man the Latin-1 (ISO-8859-1) code.
groff.man (7) linkt to http://cm.bell-labs.com/cm/cs/
Hi!
I'm currently adding a section about further literature to my short
guide.
While reading the man-pages I stumbled over a few things:
groff_char.man the Latin-1 (ISO-8859-1) code.
groff.man (7) linkt to http://cm.bell-labs.com/cm/cs/54.ps but the
actual file is at
http://cm.bell-labs.com/
Am 14.09.2007 um 16:56 schrieb Tadziu Hoffmann:
Ah, yes, this is handled somewhat inconsistently. Usually
you use one prime for feet and two primes for inches,
and one prime for minutes and two primes for seconds.
The signgle-prime character is called \[fm] (foot mark).
and the double-prime ch
m\(fm?
The glyphs used to properly denote inches (feet, seconds,
minutes) are "primes", not typewriter quotes.
I will change that into:
Das „Zollzeichen "“ auf der Tastatur ist noch nicht einmal ein
Zollzeichen, den das sähe so aus: ″.
With kind regards
Axel Kielhorn
I'm back online after some struggle with my ISP.
In the meantime I added 2 more sections to my introduction, one about
dashes and one about spaces.
I'm still collection new material and will add new section when I learn
something new.
Please have a look and point out errors.
Axel
gkurz.
Am 28.08.2007 um 22:54 schrieb Janez Z(emva <[EMAIL PROTECTED]>:
The distinction between - and \- is interesting. Since I like to copy
a
command line from a document and paste it to the shell, this is
important. I have to figure out why it doesn't work here. Pasting to
TextEdit works and shows
Am 29.08.2007 um 01:21 schrieb Werner LEMBERG:
Start a new sentence at a new line (is this a "law" or just a good
idea?)
It's a good idea.
I thought so. It is diff- and therefore cvs-friendly.
Additionally, there's a difference between
foo. bar
and
foo. bar
The latter is the
Am 27.08.2007 um 13:53 schrieb Tadziu Hoffmann:
About half of that document is about my pet peeve, the
quotation marks:-)
While we're discussing german quotes I'd like to point out
a potential pitfall: even though in many fonts you can use
the english left quote as german right quote, *this
Am 27.08.2007 um 06:58 schrieb Werner LEMBERG:
Please take a look at this document (It is written in german), I
would like to add it to the groff-wiki or maybe even the groff
distribution, once it is finished.
Attached a revised version which already includes Bruno's changes.
This is far fr
Hello!
About two month ago I started looking at groff. I discovered that
support for german was recently added and installed 1.19.2, only to
learn that I needed 1.19.3 from CVS.
It took some digging and asking around until I was able to write my
first document. In order to spare future users
Am 22.08.2007 um 21:06 schrieb Werner LEMBERG:
Entering UTF-8 characters isn't a problem, but groff doesn't seem to
understand them.
You need the current CVS version together with command line option -k
(and probably -K)
Thanks Werner!
I do have 1.19.3. (about one month old)
I did find
Am 22.08.2007 um 00:00 schrieb Gunnar Ritter:
Unfortunately, this depends on the font you are using.
With Times, the difference is rather small, but if you
change e.g. to Palatino, a comma is noticeably larger
than a quote.
Bad news:-(
but I think I'll stay with ,, '', it looks more germa
Thanks Ted and Joerg!
Use whichever is most acceptable! There is a very slight difference
between \[Bq] and ,, : to get ,, to be exactly like \[Bq] you must
a) Move the first "," leftwards by pointsize*0.0012 points
b) Then move the second leftwards by pointsize*0.002 points.
I don't think th
Hi!
I'm writing a german document in ms and I'm wondering about the best
way to enter quotation marks.
Should I
.ds Q \(Bq
.ds U \(lq
and use
\*Q \*U?
or can I simply use ,,and''?
The later is much easier to type (and read) and the result looks the
same.
Axel
41 matches
Mail list logo
