Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19826 - [links] Compile error because of codepage.inc

Attached to Project: Arch Linux
Opened by Guillaume Chanaud (gehasia) - Wednesday, 16 June 2010, 14:40 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 29 June 2010, 02:14 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When compiling with makepkg, links fail with :

In file included from charsets.c:21:0:
codepage.inc:3261:2: erreur: stray ‘#’ in program
codepage.inc:3261:18: erreur: expected ‘}’ before ‘LETTRE’
codepage.inc:3261:18: erreur: stray ‘\347’ in program

I'm on a french system with UTF8. The error is caused by ./Unicode/macroman.cp which contain a 'ç' character on line 199. This character is badly encoded (encoded as a X) and generate a codepage.inc which is
malformed

I join the patch and the new PKGBUILD for this to work properly.


Additional info:
* package version(s)
2.2
* config and/or log files etc.


Steps to reproduce:
   macroman.diff (0.5 KiB)
   PKGBUILD (1.2 KiB)
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 29 June 2010, 02:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in svn
Comment by Guillaume Chanaud (gehasia) - Wednesday, 16 June 2010, 14:44 GMT
I report to upstream too
Comment by Thomas Dziedzic (tomd123) - Monday, 28 June 2010, 19:23 GMT
can you provide a link?
Comment by Guillaume Chanaud (gehasia) - Monday, 28 June 2010, 19:59 GMT
A link to hat ?? Upstream bug report ? It has been reported by email as stated on links developers website ?
Or you want some others informations ?
Comment by Guillaume Chanaud (gehasia) - Monday, 28 June 2010, 19:59 GMT
A link to what ?? Upstream bug report ? It has been reported by email as stated on links developers website.
Or do you want some others informations ?
Comment by Thomas Dziedzic (tomd123) - Monday, 28 June 2010, 20:37 GMT
Checking the links ml archives, I can't find your message anywhere.
I'm asking for a direct link to your report.
Comment by Eric Belanger (Snowman) - Tuesday, 29 June 2010, 01:58 GMT
Thomas: Upstream wants bugs to be emailed directly to them. There is no public bug tracker or anything of the sort.
Comment by Thomas Dziedzic (tomd123) - Tuesday, 29 June 2010, 02:02 GMT
Ah, I got the wrong website :) I was using http://links.sourceforge.net/ which says to their (public) ML, nvm.

Loading...