public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: robert rottermann <robert@redcor.ch>
To: development@lists.ipfire.org
Subject: Re: compiling an actual version of python
Date: Sun, 08 Feb 2015 09:42:26 +0100	[thread overview]
Message-ID: <54D72172.5040005@redcor.ch> (raw)
In-Reply-To: <1423335404.17371.181.camel@rice-oxley.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 4031 bytes --]

next problem:

i did copy the python source archve as instructed:
cp python/Python-2.7.9.tar.xz ipfire-2.x/cache/

and changed
vim ~/ipfire/ipfire-2.x/lfs/python
   on line 27 change
     VER        = 2.7.3
   to
     VER        = 2.7.9

but running
./make.sh toolchain

produces the following error

scripts/basic/fixdep.c:141: warning: empty declaration
scripts/basic/fixdep.c:149: error: storage class specified for parameter 'hashtab'
scripts/basic/fixdep.c:152: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:165: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:180: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:198: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:215: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:237: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:271: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:282: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:318: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:400: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:436: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
scripts/basic/fixdep.c:448: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '{' token
/usr/include/unistd.h:756: error: old-style parameter declarations in prototyped 
function definition
scripts/basic/fixdep.c:462: error: expected '{' at end of input
make[2]: *** [scripts/basic/fixdep] Error 1
make[1]: *** [scripts_basic] Error 2
make[1]: Leaving directory 
`/home/robert/ipfire/ipfire-2.x/build/usr/src/linux-3.14.31'
make: *** 
[/home/robert/ipfire/ipfire-2.x/log/linux-3.14.31-ipfire-headers-tools] Error 2

more advice needed ..
thanks
robert


On 07.02.2015 19:56, Michael Tremer wrote:
> Hi,
>
> no, the build system does not replace your system, but requires root
> permissions. Those could damage your system in case anything unexpected
> happens, so creating a virtual machine which you can just delete and
> reinstall is a good option.
>
> -Michael
>
> On Sat, 2015-02-07 at 19:54 +0100, robert rottermann wrote:
>> new problem/question ..
>>
>> now I get the following message:
>> *** Packaged toolchain compilation
>> version   options    time (sec)   status
>> Resetting our nice level to 10
>> [ DONE ]
>> Checking if we're running as root user
>> [ FAIL ]
>>
>> ERROR: Not building as root
>>         Check /home/robert/ipfire/ipfire-2.x/log/_build.preparation.log
>> for errors if applicable
>> robert(a)chrissy:~/ipfire/ipfire-2.x$
>>
>>
>> why should I do that as root?
>>
>> is the build process replacing my system?
>>
>> this is not what I want actually ..
>>
>> I think I restart everything in a virtual machine ..
>>
>> robert
>>
>>
>> On 07.02.2015 19:47, robert rottermann wrote:
>>
>>> On 07.02.2015 13:23, Michael Tremer wrote:
>>>
>>>> Ignore the IPFire 3 stuff. After that, you will need to do what is
>>>> described in the build howto:
>>> aha, thats ignoring IPFire 3 stuff is the key here..
>>> However, this is what is NOT, what is explained in the wiki
>>>
>>> git clone ssh://<user>@git.ipfire.org/pub/git/ipfire-3.x.git # Could also be checked out via the git proto
>>>   c
>>> ol
>>> cd ipfire-3.x/
>>> git remote add <user> ssh://<user>@git.ipfire.org/pub/git/people/<user>/ipfire-3.x.git
>>> thanks,
>>> robert
>>>
>>>
>>> _______________________________________________
>>> Development mailing list
>>> Development(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/development


  reply	other threads:[~2015-02-08  8:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54D65F7A.7050700@redcor.ch>
2015-02-07 18:56 ` Michael Tremer
2015-02-08  8:42   ` robert rottermann [this message]
2015-02-09 11:26     ` Arne Fitzenreiter
2015-02-05 10:03 robert rottermann
2015-02-05 13:23 ` Michael Tremer
2015-02-05 13:35   ` robert rottermann
2015-02-05 23:37     ` Michael Tremer
2015-02-07 11:37       ` robert rottermann
2015-02-07 12:23         ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54D72172.5040005@redcor.ch \
    --to=robert@redcor.ch \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox