Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python fails to build with Subversion 1.7 #50344

Closed
Arfrever mannequin opened this issue May 23, 2009 · 8 comments
Closed

Python fails to build with Subversion 1.7 #50344

Arfrever mannequin opened this issue May 23, 2009 · 8 comments
Labels
build The build process and cross-build

Comments

@Arfrever
Copy link
Mannequin

Arfrever mannequin commented May 23, 2009

BPO 6094
Nosy @benjaminp, @ned-deily
Files
  • python-2.6.2-svnversion.patch: python-2.6.2-svnversion.patch
  • python-2.6.2-svnversion.patch: python-2.6.2-svnversion.patch
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2009-05-23.19:25:11.229>
    created_at = <Date 2009-05-23.18:19:56.411>
    labels = ['build']
    title = 'Python fails to build with Subversion 1.7'
    updated_at = <Date 2014-06-28.23:15:48.955>
    user = 'https://bugs.python.org/Arfrever'

    bugs.python.org fields:

    activity = <Date 2014-06-28.23:15:48.955>
    actor = 'ned.deily'
    assignee = 'none'
    closed = True
    closed_date = <Date 2009-05-23.19:25:11.229>
    closer = 'benjamin.peterson'
    components = ['Build']
    creation = <Date 2009-05-23.18:19:56.411>
    creator = 'Arfrever'
    dependencies = []
    files = ['14045', '14047']
    hgrepos = []
    issue_num = 6094
    keywords = ['patch']
    message_count = 8.0
    messages = ['88246', '88248', '88251', '88586', '88587', '221440', '221817', '221821']
    nosy_count = 6.0
    nosy_names = ['jimjjewett', 'benjamin.peterson', 'ned.deily', 'Arfrever', 'jcon', 'suman_pas']
    pr_nums = []
    priority = 'normal'
    resolution = 'fixed'
    stage = None
    status = 'closed'
    superseder = None
    type = 'compile error'
    url = 'https://bugs.python.org/issue6094'
    versions = ['Python 2.6', 'Python 2.5', 'Python 3.0', 'Python 3.1', 'Python 2.7']

    @Arfrever
    Copy link
    Mannequin Author

    Arfrever mannequin commented May 23, 2009

    svnversion program from Subversion 1.7 (currently trunk), when invoked
    on unversioned directory, prints "Unversioned directory" instead
    "exported". This change in output is intentional and won't be reverted.

    It causes build failure:
    x86_64-pc-linux-gnu-gcc -pthread -c -fno-strict-aliasing -DNDEBUG -
    -DSVNVERSION="LC_ALL=C svnversion ." -o Modules/getbuildinfo.o
    ./Modules/getbuildinfo.c
    x86_64-pc-linux-gnu-gcc: directory": No such file or directory
    : warning: missing terminating " character
    ./Modules/getbuildinfo.c: In function '_Py_svnversion':
    ./Modules/getbuildinfo.c:48: error: missing terminating " character
    ./Modules/getbuildinfo.c:48: error: expected expression before ';'
    token
    make: *** [Modules/getbuildinfo.o] Error 1

    I'm attaching the patch which fixes this problem and also updates
    expected output of svnversion.

    @Arfrever Arfrever mannequin added the build The build process and cross-build label May 23, 2009
    @Arfrever
    Copy link
    Mannequin Author

    Arfrever mannequin commented May 23, 2009

    I'm attaching improved patch.

    @benjaminp
    Copy link
    Contributor

    benjaminp commented May 23, 2009

    Fixed in r72871.

    @Arfrever Arfrever mannequin added the build The build process and cross-build label May 25, 2009
    @jimjjewett
    Copy link
    Mannequin

    jimjjewett mannequin commented May 30, 2009

    Would this patch mean that users of pre-1.7 subversion would get build
    failures? Is it possible to support both forms of wording?

    @benjaminp
    Copy link
    Contributor

    benjaminp commented May 30, 2009

    2009/5/30 Jim Jewett <report@bugs.python.org>:

    Jim Jewett <jimjjewett@users.sourceforge.net> added the comment:

    Would this patch mean that users of pre-1.7 subversion would get build
    failures?  Is it possible to support both forms of wording?

    Yes, and it does.

    @sumanpas
    Copy link
    Mannequin

    sumanpas mannequin commented Jun 24, 2014

    I am trying to install Python 2.7.7 or 2.7.3 in one of my linux machine which has RHEL 6.4.

    I am getting the same error, that is mentioned in this bug. I am pasting it below. Please let me know, what should i do here.

    ser Python-2.7.7]# make
    gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE
    -DSVNVERSION=""LC_ALL=C echo Unversioned directory""
    -DHGVERSION=""LC_ALL=C ""
    -DHGTAG=""LC_ALL=C ""
    -DHGBRANCH=""LC_ALL=C ""
    -o Modules/getbuildinfo.o ./Modules/getbuildinfo.c
    gcc.orig: directory": No such file or directory
    : warning: missing terminating " character
    ./Modules/getbuildinfo.c: In function ?_Py_svnversion?:
    ./Modules/getbuildinfo.c:63: error: missing terminating " character
    ./Modules/getbuildinfo.c:63: error: expected expression before ?;? token
    make: *** [Modules/getbuildinfo.o] Error 1

    @jcon
    Copy link
    Mannequin

    jcon mannequin commented Jun 28, 2014

    I encountered the same problem w/ 2.7.7.

    Temporary workaround:
    SVNVERSION="Unversioned directory" ./configure
    make
    ...

    @ned-deily
    Copy link
    Member

    ned-deily commented Jun 28, 2014

    Suman, Jon: This issue was closed five years ago and the fixes for it have long been out in the field. Comments on closed issues are likely to be overlooked and not acted on. If you are having a current problem, you should open a new issue, documenting in particular what OS versions and shell you are using, the pertinent values (SVNVERSION, HGVERSION) from the generated Makefile, and the output from:

    echo LC_ALL=C echo Unversioned directory

    FWIW, I was unable to reproduce the failure on a different Unix platform.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    build The build process and cross-build
    Projects
    None yet
    Development

    No branches or pull requests

    2 participants