GCC manpage contains invalid "@tie{}" tags

Bug #1405685 reported by Vladimir Rutsky
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc-11 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I found in `man gcc` following contents:

           "avrxmega7"
               "XMEGA" devices with more than 128@tie{}KiB of program memory and more than 64@tie{}KiB of RAM. mcu@tie{}= "atxmega128a1",
               "atxmega128a1u", "atxmega128a4u".

you can see there strange "@tie{}" tags between numbers and measure units, where non-breakable space should be.

`info gcc` doesn't have such tags, so looks like this is a bug of converting original GCC documentation to manpage format.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gcc-doc 4:4.8.2-1ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 26 00:46:37 2014
InstallationDate: Installed on 2014-01-01 (358 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gcc-defaults
UpgradeStatus: Upgraded to trusty on 2014-04-27 (242 days ago)

Revision history for this message
Vladimir Rutsky (rutsky) wrote :
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this issue and help making Ubuntu better.

I see the strange tags here too, and they are also present in the manpage on Ubuntu Vivid.

>`info gcc` doesn't have such tags, so looks like this is a bug of converting original GCC documentation to manpage format.

Could you double-check this? They show up when I run `info gcc` here.

Changed in gcc-defaults (Ubuntu):
status: New → Confirmed
tags: added: manpage utopic vivid
Revision history for this message
Vladimir Rutsky (rutsky) wrote :

> Could you double-check this? They show up when I run `info gcc` here.

I double-checked that I have installed gcc-4.8-doc package and in

$ info g++-4.8 "Invoking GCC" "Submodel Options" "AVR Options"

I can find same paragraph without "@tie{}" tags:

     'avrxmega7'
          "XMEGA" devices with more than 128 KiB of program memory and
          more than 64 KiB of RAM.
          MCU = 'atxmega128a1', 'atxmega128a1u', 'atxmega128a4u'.

A bit strage is that infopage has singlequotes ('avrxmega7') and man-page has double-quotes ("avrxmega7").

Info-page source doesn't have any tags on my system:

$ zcat /usr/share/info/gcc-4.8.info.gz | grep avrxmega7 -A 3
     'avrxmega7'
          "XMEGA" devices with more than 128 KiB of program memory and
          more than 64 KiB of RAM.
          MCU = 'atxmega128a1', 'atxmega128a1u', 'atxmega128a4u'.
--
     'avrxmega6', 'avrxmega7', respectively. If MCU specifies a device,
     this built-in macro is set accordingly. For example, with
     '-mmcu=atmega8' the macro will be defined to '4'.

$ dpkg -S /usr/share/info/gcc-4.8.info.gz
gcc-4.8-doc: /usr/share/info/gcc-4.8.info.gz

$ apt-cache policy gcc-4.8-doc
gcc-4.8-doc:
  Installed: 4.8.2-19ubuntu1
  Candidate: 4.8.2-19ubuntu1
  Version table:
 *** 4.8.2-19ubuntu1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thank you. I see now that the info page display things correctly.

I simply ran `info gcc` first, which at a closer glance seem to simply load the manpage so that would exaplain why I saw it in #2.

Changed in gcc-defaults (Ubuntu):
importance: Undecided → Medium
Matthias Klose (doko)
affects: gcc-defaults (Ubuntu) → gcc-11 (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gcc-11 - 11-20210310-1ubuntu1

---------------
gcc-11 (11-20210310-1ubuntu1) hirsute; urgency=medium

  * Merge with Debian; remaining changes:
    - Build from upstream sources.

gcc-11 (11-20210310-1) experimental; urgency=medium

  * GCC snapshot, taken from the trunk (20210310)
  * Work around dwz issue on mips64el stripping go1.
  * Replace @tie{} string with a space in the man pages. LP: #1405685.
  * Don't run the memory usage stats on m68k.

 -- Matthias Klose <email address hidden> Wed, 10 Mar 2021 12:06:48 +0100

Changed in gcc-11 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Vladimir, or anyone else affected,

Accepted gcc-10 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-10/10.3.0-1ubuntu1~20.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-groovy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Vladimir, or anyone else affected,

Accepted gcc-10 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-10/10.3.0-1ubuntu1~20.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed-focal
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.