@All

Also note that you can now ask questions, report bugs or others writing to the email address you can find in the PDF file...

Don't ever say there is no support !

_________________
Philippe 'Elwood' Ferrucci
Sam460 1.10 Ghz
AmigaOS 4 betatester
Amiga Translator Organisation

@Hyperion brothers

Any chance of seeing updates to newer GCC versions before the next SDK release?

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

Quote:

Quote: Why not get broadband? Is it hard where you live or what? I thought it would be cheaper for almost any type of user these days. It is in Sweden anyway. You can get ADSL broadband for less than 20¤/month.

Quote:

At least here in Italy, dial-ups flat contracts are cheaper than broadband ones. I'm using a semi-flat ISDN 128k connection which costs me 15 euro per month. There's also a full flat 56k contract for 12 euro/month.

Uh, that's expensive.. 1Mbit/1Mbit ADSL 24.5¤ / month here..

Last edited by miksuh on 14-Apr-2006 at 04:36 PM.
Last edited by miksuh on 14-Apr-2006 at 04:34 PM.

Quote:

Any chance of seeing updates to newer GCC versions before the next SDK release?

Not from us... there will be a new SDK for sure, including the then current gcc, but no intermediate updates... if you need those, adtools will provide the source code...

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

@EntilZha

Ok. Thanks for the answer.

No I don't need it. I just wanted to ask the question as some user on this
thread "complained" about using an older version of GCC than was available
in the SDK.

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

@Samwel

money. or rather - being married with 3 kids, and having someone watching the outgoings !
I'd love to, but I dont Trust Telewest to not put the prices up, like they have done with
the cableTV and phone.

...so its not so much where I live, as with whom !

-edit-
I think the best deal I can use (theoretically !!) is about £15 - or roughly ¤20.

Last edited by Agafaster on 15-Apr-2006 at 09:52 PM.

_________________
XH558 - the worlds last flying Vulcan.
ok, its actually XL426 in the picture but you know what I mean.

Quote:

Oh? Then there's an error somewhere, I can't compile YAM since this change.

I get errors everywhere in everything. I'm getting tired of rewriting code and makefiles every time there is an SDK update. Why can't we just fix and improve the way things work instead of constantly changing the way they work?? Being stuck with the same version of GCC and the Amiga SDK for years on OS3 is beginning to look like an advantage None of the programs I compile with new GCC versions seem to work any better than the OS3 versions I compile with GCC 2.95.3.

_________________
X1000 with 2GB memory & OS4.1FE

When you asked for bug reports in a previous comment you probably didn't intend for them to be reported here but I'm gonna do it anyway. Now that we have an Amiga version and a GNU version of make, maybe I won't have to rewite Amiga make files so often.

In an early version of make this worked:
echo 'compiling ...'
In a later version that didn't work but this worked:
echo "compiling ..."
In yet a later version it had to be changed to this:
echo '"compiling ..."'
And now the echo command that works is:
echo "compiling ..."

Whew. I hope we can settle on the current method.

The above isn't really a bug; it's just a pain in the but

I do have a problem with the new Amiga "make".
This line no longer works if there are no files to delete:
@delete #?.o quiet *>NIL:

It worked in the previous "make" I'm using. Now the "make clean"
operation stops with Error[5]. A return value of "5" is a warning
in AmigaDOS and shouldn't break a script or the make command.
Is there a way to set the break level in make??

Will this be fixed or am I stuck with a kludge like:
@echo >NIL: `delete #?.o quiet *>NIL:`
???

_________________
X1000 with 2GB memory & OS4.1FE

If you read the documentation of make, you will notice that there are two of them: make and gmake. The normal make uses an AmigaOS shell to compile, hence, the commands it uses are AmigaOS commands. Echo will expect double quotes.

Gmake, OTOH, uses sh... which means it uses the sh or coreutils commands, which means single quotes.

Regarding delete: Any error or warning WILL break a makefile. This has been the case since the first SDK. If you want to have the return value ignored, prepend the line with a dash, like in

-delete #?.o

This is also stated in the make documentation

Last edited by EntilZha on 16-Apr-2006 at 09:38 AM.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

Quote:

I get errors everywhere in everything.

If your code is correct, it should compile. If not, there's a good chance that there are problems in your code that older compilers just glossed over.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

Quote:

I get errors everywhere in everything. I'm getting tired of rewriting code and makefiles every time there is an SDK update.

Sorry, but gcc is getting stricter with every release. There have been heavy modifications necessary between SAS/C and gcc already, and this will continue. You should compile your code with "-Wall" all the time, and fix all warnings you see. For AmigaOS we mostly even add "-Werror" to make the compilation break on errors.


Quote:

Being stuck with the same version of GCC and the Amiga SDK for years on OS3 is beginning to look like an advantage. None of the programs I compile with new GCC versions seem to work any better than the OS3 versions I compile with GCC 2.95.3.

Can it get any more fuzzy than this? Please go ahead and make a few benchmarks before slagging off other people's work.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

Quote:

Regarding delete: Any error or warning WILL break a makefile. This has been the case since the first SDK. If you want to have the return value ignored, prepend the line with a dash, like in -delete #?.o This is also stated in the make documentation

At some point "-delete #?" stopped working and I changed it. Thanks for the reminder because it now works. I realize that there are bound to be problems in the course of developing the OS4 programming tools. It's just a little frustrating when I have to keep changing code and makefiles that previously worked. Sometimes my bug reporting has produced positive changes and other times it has just been a display of my own ignorance. I'll let you decide which is the case here

With regard to any error breaking a makefile: If "make" is now an Amiga Shell command (with gmake being the sh command) then it should follow the same rules as standard Amiga commands. A return code of 5 is a warning, not an error. Now that we have 2 make commands, lets have the Amiga make work like an Amiga command. For example, the U*nix command "rm" has a -f option will cause it to ignore nonexistant files. The Amiga "delete" command will ignore nonexistant files by default but will issue a verbal warning and set a warning level return code. The only way that using "delete" can work the the same in an Amiga make command as the "rm" does in a U*nix make (gmake) command is if the Amiga make command plays by the AmigaDOS rules i.e. don't stop execution for a warning code. This is probably a trivial complaint and can safely be ignored

_________________
X1000 with 2GB memory & OS4.1FE

Quote:

Sorry, but gcc is getting stricter with every release. There have been heavy modifications necessary between SAS/C and gcc already, and this will continue. You should compile your code with "-Wall" all the time, and fix all warnings you see. For AmigaOS we mostly even add "-Werror" to make the compilation break on errors.

To me, most of the warnings are just academic. I would rather get a single warning about a problem that will cause a program to fail than a thousand warnings that will not lead to a single failure. I have yet to see GCC tell me that I forgot to check a returned pointer for a NULL value before I use it, but it will tell me:

UBYTE *vers = "$VER: filereq 37.0";
warning: pointer targets in initialization differ in signedness

while:

(char)UBYTE *ver = "$VER filereq 37.0";

will yield no warning but is a stupid fix.

The increased strictness is a real pain when you work on an open-source program that is supposed to compile for multiple platforms (OS4, OS3, MOS) that are all using a different version of GCC. A change to eliminate a warning with one version of GCC will produce a new warning on another version. The simplest solution seems to be type casting everything, everywhere to eliminate the warnings for everyone. However, that's not your problem; it's mine.

Quote:

Can it get any more fuzzy than this? Please go ahead and make a few benchmarks before slagging off other people's work.

I don't think the additional warnings (strictness) are responsible for any speed increases and I was referring more to how the programs work; not how fast. However, my Amiga has punished me for offending you. When I posted my last message concerning the "make" command, IBrowse returned to the first page of this thread but the links at the bottom indicated I was still at the last page (which was where I initiated my message). When I clicked the link to move back to the last page my system froze and would not respond to a warm or cold reboot from the keyboard. The reset button rebooted me with reports of an invalidated disk because of a trashed IBrowse cache. I didn't know you had that kind of control over my OS and will be more careful in the future

_________________
X1000 with 2GB memory & OS4.1FE

@xenic
Quote:

I didn't know you had that kind of control over my OS and will be more careful in the future

Ahh, beware the Freiden Jedi Powers you must!

_________________
Are we not done with the same silly arguments and flames yet??!