mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Andrew M. <andrew48217@yahoo.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] gcc versions supported by PTXDist.
Date: Wed, 5 Oct 2011 09:48:51 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111005T113127-867@post.gmane.org> (raw)

Hello,

I hope this is the correct mailing list to ask this question, it's just I 
couldn't find the answer anywhere else. If not, please direct me to the correct 
one.

I was wondering what versions of gcc are supported by the 2011-08.0 version of 
PTXDist. The reason I ask is because I tried compiling nano (with the given 
nano.make rule given with ptxdist, without modifications), and I got a 
compilation error, regarding line 1600 in the file `files.c`:
fnctl.h:51: error: call to '__open_missing_mode' declared with attribute error: 
open with O_CREAT in second argument needs 3 arguments.

My compiler is gcc 4.4.3 for arm crotex a8. Also, compiling the same package 
(nano 1.3.12) using my host's compiler (gcc 4.4.3, supplied with Ubunutu 10.4) 
gave the same error.

Compiling a newer version of nano (2.2.3) on the host works fine.

I also noticed that the 'out-of-the-box' configuration enforces the 4.3.2 
version of gcc for the toolchain configuration. (Under platforms/toolchain.in, 
line 22)

My questions are:
1. Does ptxdist supposed to work _only_ with version 4.3.2 of gcc? (Or is it a 
bug in the nano configuration?)
2. If so, is there a planned upgrade sometime?

I know I can update the nano receipe and make the newer version of nano 
compile, I'm just wondering if there is a reason that the 4.3.2 version of gcc 
is enforced. (Maybe because other packages rely on the 4.3.2 version of gcc?)

Thank you,

Andrew M.


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2011-10-05  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  9:48 Andrew M. [this message]
2011-10-05 10:50 ` Michael Olbrich

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=loom.20111005T113127-867@post.gmane.org \
    --to=andrew48217@yahoo.com \
    --cc=ptxdist@pengutronix.de \
    /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